# LinkedIn year in review

> A colorful year-in-review system turns LinkedIn statistics into patterned mobile cards. BUCK built the modular, multilingual experience in Rive and shows its design and logic in this case-study film.

- Kind: Video
- Page: https://meetreference.com/v/ref-buck-linkedin-year-in-review/
- Ready-to-use agent handoff: https://meetreference.com/v/ref-buck-linkedin-year-in-review/agent.txt
- Authorship: Not stated
- Made with: Not stated
- Model: not stated
- Built with: Rive
- Style: Product launches; geometric, color blocking, flat graphics, bold typography, modular, mobile, playful
- Length and format: 45 sec, 16:9 (1280x720 source)
- Playback: a muted visual reference. The original soundtrack is available only at the source.
- Shared by BUCK in Website: https://buck.co/work/linkedin-year-in-review
- Prompt fidelity: Unavailable in this entry. The recreation brief is written by Reference.

## Before you start

Guidance from Reference, separate from the creator's instructions.

1. Read the reference and inspect the project, installed libraries, and available agent skills before writing code. Reuse suitable tools already present.
2. Prefer the creator-reported libraries and skills when they fit the task. Explain what useful additions help with, and install missing project dependencies or relevant skills from official sources when the environment and the user's existing permissions allow it. Respect the project's package manager and setup rules; do not ask again for routine setup already authorized.
3. Distinguish tools used by the creator from your own recommendations. A listed tool is not automatically required, and an empty tools or requirements list means the setup is unknown, not that nothing is needed.
4. Ask concise questions when missing inputs or choices materially affect the result: paid services, credentials, the user's assets, or a different production approach. Use existing answers and permissions; continue independent work while waiting.
5. If a useful library, skill, or service cannot be installed or used, explain an available alternative and its expected effect on quality, features, or effort. Get the user's choice before a material compromise; otherwise state the fallback and continue. Never silently simplify the result or claim to have used a tool you did not use.

## Recreating this video

This is a visual reference. No original creator prompt is available. The following brief was written by Reference after inspecting the work.

Build a small vocabulary of circles, semicircles, wedges, and rounded bars, then reuse it across full-frame graphics and narrow mobile cards. Use contrasting solid backgrounds and reserve a pale, uninterrupted area for the main statistic while patterned geometry occupies the edges. Adapt the visible side-by-side presentation to compare variants, replacing the branding, metrics, copy, and language examples with those of the new subject.

1. Open the live work or source and inspect the frame images below.
2. Adapt its layout, hierarchy, palette, and interaction patterns to the user's own content and brand.
3. Compare the result against the reference. Use your own assets and credit the original creator.

## What it looks like

Written by Reference from the video frames, not by the creator.

Polished, minimalist motion-graphics style using bold typography, flat vector shapes, and simplified interface elements.

- Color: Navy and dark blue, bright blue, coral red, mint and light green, pale blue, cream, and white.
- Type: Heavy navy sans-serif headings accompany smaller labels on the mobile cards; a spreadsheet and node diagram appear in the process views.
- Framing: Centered titles and logo marks alternate with full-frame panels and tightly arranged dashboard or card layouts; large areas of solid color create clear contrast.
- Structure: A Rive title card, a node diagram, a circular motif, a data table, three themed mobile cards, paired device views, a three-language heading, patterned cards in different languages, and a minimal studio mark.

Storyboard, nine frames spread across the video: https://meetreference.com/media/ref-buck-linkedin-year-in-review/storyboard.webp

- Frame 1 at 2.5s: https://meetreference.com/media/ref-buck-linkedin-year-in-review/f1.webp
- Frame 2 at 7.5s: https://meetreference.com/media/ref-buck-linkedin-year-in-review/f2.webp
- Frame 3 at 12.5s: https://meetreference.com/media/ref-buck-linkedin-year-in-review/f3.webp
- Frame 4 at 17.5s: https://meetreference.com/media/ref-buck-linkedin-year-in-review/f4.webp
- Frame 5 at 22.6s: https://meetreference.com/media/ref-buck-linkedin-year-in-review/f5.webp
- Frame 6 at 27.6s: https://meetreference.com/media/ref-buck-linkedin-year-in-review/f6.webp
- Frame 7 at 32.6s: https://meetreference.com/media/ref-buck-linkedin-year-in-review/f7.webp
- Frame 8 at 37.6s: https://meetreference.com/media/ref-buck-linkedin-year-in-review/f8.webp
- Frame 9 at 42.6s: https://meetreference.com/media/ref-buck-linkedin-year-in-review/f9.webp

## Links

- Watch: https://buck.co/work/linkedin-year-in-review
- Original post: https://buck.co/work/linkedin-year-in-review