Supporting product work · Later

Content Workflows

Connected two distinct Later product surfaces across the content lifecycle: discovering and approving useful media, then organizing and reusing it from the Media Library.

60-second summary

Problem

Brands needed to find authentic content, assess whether it was useful, and move approved assets into an increasingly large library without losing context or momentum.

Role

Product Design · UI Implementation · Web app

Pivotal decision

Treat discovery, review, approval, library organization, and reuse as connected stages while keeping each product surface focused on its primary task.

Connected product evidence

A visible path from hashtag, profile, stock, and contributor sources into a content-management workspace for filtering, reviewing, and scheduling assets.

Later hashtag content discovery with search history and a media result grid — 01Product interface
Hashtag discovery connects a repeatable search history with a content-first result grid and engagement context.

Decisions and system thinking

Two product surfaces connected by one content lifecycle

UGC and Content Library remain clearly identified as separate projects. Their functional handoff reveals the wider system: approved media becomes reusable product content.

01 / Discover

Support different ways of finding useful media.

Hashtag search, profile search, stock photography, and contributor submissions use source-specific context while sharing familiar result grids, filtering, selection, and action patterns.

02 / Review and approve

Make state and next action visible.

Contributor views separate all, pending, added, and discarded submissions. Search, filters, and sorting help users locate a specific asset, while approval actions keep the content itself as the visual priority.

03 / Organize and reuse

Carry approved content into the Media Library.

The library brings browsing, filtering, asset review, and scheduling into one working surface so teams can move from acquisition to reuse without rebuilding context.

02Profile discovery preserves creator context while helping teams assess reusable content.

Later stock photo search with multi-selection and an Add to Library action — 03Stock-photo selection uses the same clear path from discovery to the Media Library.

Later contributor workflow showing pending, added, and discarded approval states — 04Contributor states, filtering, and an explicit empty state support review and approval.

Later Content Library showing filters, assets, and content-management controls — 05The Media Library continues the workflow with browsing, filtering, and asset management.

Detailed Later Content Library controls — 06Focused controls move teams from asset discovery into a specific action.

Later Content Library selection and scheduling workflow — 07Selection and scheduling stay connected to the asset being reviewed.

Content lifecycle

From discovery to a reusable asset

01Find content by hashtag, profile, contributor, or stock source
02Review content and its available context
03Filter, sort, approve, or discard
04Add approved media to the library
05Organize, select, and schedule the asset

Shipped-product walkthrough

User-generated content walkthrough

Later’s public tutorial demonstrates how customers find and collect user-generated content. It documents a shipped product surface rather than providing an adoption or efficiency metric.

A public walkthrough of finding and collecting authentic content for a social strategy.Watch on YouTube

Technical constraint

Design around the context the API can actually provide

Content type, likes, and comments could appear on result cards, but the source notes that content-owner data was unavailable in a key collection flow. Avatars were therefore omitted rather than filled with misleading identity information.

Design contribution

What I contributed across the product workflow

Project-scope definition with product
Competitor and user research and testing
Impact–effort prioritization
Information architecture and workflow design
User flows, prototypes, and high-fidelity UI
Figma component-library creation
HTML/CSS implementation quality

View original UGC source case