Skip to main content
Hook layoutWith device mockup

Screen Hero Layout

Top-clipped device, centered headline, one hero stat. A frame-1 hook for when the app screen itself is the strongest first impression.

Try this layout
Screen Hero Layout example: an App Store screenshot built with the screen hero layout
Example generated in AppScreenshotStudio

What is the screen hero layout?

The screen hero layout clips a device at the top of the frame so the app screen bleeds off the upper edge, with a centered headline and a single hero stat (a rating, a count, a one-line outcome) below it. It reads as a hook because the partial device pulls the eye straight into the product, then the headline names the promise. The App Store shows up to three screenshots in search results, so frame 1 has to communicate the product almost instantly, and a large top-anchored screen does that faster than a small centered mockup. Use screen hero when the interface is visually strong on its own (a clean dashboard, a striking visual, a distinctive layout) and you want the screen rather than a caption to carry the first impression. Pair it with an educate frame next that explains what the screen actually does, so the hook does not stand alone.

Layout spec

Narrative job
Hook
Device mockup
Yes
Works in frames (of 5)
12345
Renders
Laurel statStat rowStar rating

Read from the builder engine: the narrative job, device, valid frame positions, and trust signals this layout actually renders.

When to use this layout

Reach for screen hero on frame 1 when the screen sells itself and you would rather show than tell. If the UI is plain or needs a caption to make sense, device-hero or a text-top educate layout lands better. Keep the hero stat to one signal, and only use a number you can stand behind.

Best for

  • Frame 1 when the app screen is strong enough to lead
  • Apps with a distinctive or visually rich interface (dashboards, editors, media)
  • Hooks where you want the product visible instantly, not described first
  • Sets that open on the UI and explain features in later frames

Common pitfalls

  • Clipping so much of the screen that the key UI element is cut off
  • Stacking multiple stats under the headline, which dilutes the single hook
  • Using a weak or fabricated stat, which reads worse than no stat at all

Generate a screen hero screenshot

Describe your app, and the builder generates a frame in this layout. No design decisions, just finished output.

Get screenshots