What screens are in the LinkedIn Compose a post (with attach) flow?

This Atlas flow includes Home Feed, Post Composer, Composer Attachment Grid.

What can teams learn from this LinkedIn flow?

The flow helps teams inspect real mobile app navigation, compare product patterns, plan QA coverage, and give AI agents reliable app context.

Revyl Atlas flow

LinkedIn Compose a post (with attach) flow

LinkedIn's compose a post (with attach) flow moves users from Home Feed to Composer Attachment Grid across 3 mapped iOS app screens. Use this path for mobile UX teardown work, QA coverage planning, and AI agent navigation context.

View full report Open map

3Screens

socialFlow type

iOSPlatform

Home FeedStarts at

Research notes

Why the LinkedIn Compose a post (with attach) flow matters

Navigation pattern This flow shows how LinkedIn carries a user from Home Feed to Composer Attachment Grid across real app states.

Testing coverage The screen path gives QA and product teams concrete screens to verify, including visible UI density, transition order, and repeated mobile states.

Agent grounding Atlas makes this journey usable as navigation context for AI agents that need to understand the app before executing mobile tasks.

Screen path

LinkedIn Compose a post (with attach) screenshots

This page is a crawlable breakdown of one real mobile journey. The screenshots, step labels, and element counts make the LinkedIn Compose a post (with attach) path easier to compare against competing apps, reproduce during QA planning, and reuse as structured navigation context for app automation.

Home Feed

Step 1 in the LinkedIn Compose a post (with attach) flow. Atlas detected 14 UI elements on this screen.

Post Composer

Step 2 in the LinkedIn Compose a post (with attach) flow. Atlas detected 9 UI elements on this screen.

Composer Attachment Grid

Step 3 in the LinkedIn Compose a post (with attach) flow. Atlas detected 8 UI elements on this screen.

How to use it

Apply this flow to product and testing work

For product research Use the ordered path to understand which screens appear before and after key actions, how much interface density the user sees, and where the app introduces extra decisions or interruptions.

For QA planning Turn each screen in the path into a coverage checkpoint. The screenshot sequence helps teams verify expected states, navigation transitions, and UI inventory without manually rediscovering the journey.

Related flows