nexa
ExploreServicesAboutTeamFAQBlogContact
GitHubStart a project
Blog · Design

What we changed in our store screenshots on the second pass

Our first Tarot Destiny screenshots described features. The second set shows what it feels like to use the app.

Tina

Team Lead · Mobile & Web

May 30, 20262 min read

On this page

  1. What was wrong with the first set
  2. The new set, frame by frame
  3. Rules we now follow
  4. Timing changed most

Store screenshots are the only part of an app most people will ever see. They decide whether someone installs, often in the few seconds it takes to scroll past. Our first set for Tarot Destiny was accurate and completely forgettable. Here is a frame-by-frame look at the redesign.

What was wrong with the first set

Each screenshot answered "what does this app have": daily card, spreads, journal, history. That is the question people ask last, if at all. The questions they ask first are "what will this feel like" and "is this for me".

PROBLEM 01

Separate ads, not a set

Every frame had a different background, so the row looked like five unrelated images.

PROBLEM 02

Captions named features

"Journal" tells you a screen exists. It does not tell you why you would open it.

PROBLEM 03

Frame one needed the others

In search results only one or two frames show. Ours made no sense alone.

PROBLEM 04

Placeholder content

A few screens showed sample text that made the app look unfinished.

The new set, frame by frame

  1. Card revealSays what the app is
  2. ShuffleStart of a reading
  3. DrawChoose a card
  4. MeaningThe interpretation
  5. JournalSave it for later
One reading told in order. Search results only show the first frame or two, so frame 01 carries the pitch.
FrameJobCaption style
01 · RevealSell the whole app on its ownWhat the app is, in plain words
02 · ShuffleInvite the viewer inSecond person, present tense
03 · DrawShow interactionOne short action line
04 · MeaningShow the payoffWhat you get from a reading
05 · JournalGive a reason to come backHabit, not feature name
A feature list tells people what they could do. A story shows them doing it.

Rules we now follow

Do

  • Make frame one work alone
  • One idea and one short line per frame
  • Use real content in every screen
  • Keep one background family across the set

Don't

  • Label frames with feature names
  • Use lorem ipsum or empty states
  • Write captions too small for a thumbnail
  • Treat screenshots as the last task
The thumbnail test

Shrink the whole set to the size it appears on a phone search page. If a caption cannot be read at that size, it gets shorter, not smaller.

Timing changed most

We used to make screenshots at the end, as a packaging task. Now we sketch the screenshot story early. If we cannot describe an app in five frames, the product itself usually is not focused enough yet.

Mentioned in this post

Tarot Destiny

Case study

Work with us

Need an app like Tarot Destiny built?

Our services

Keep reading

All posts
  • AI can design an app now. Are designers redundant?
    Read post

    Design

    AI can design an app now. Are designers redundant?

    AI makes the first draft of a screen cheap. That shifts design work to what matters most: understanding users and choosing what is right for them.

    Tina· Oct 10, 20266 min read
  • AI in software development: turn change into an advantage
    Read post

    Engineering

    AI in software development: turn change into an advantage

    AI does not replace technical thinking. With the right process, it frees teams to focus on the decisions that make products better.

    Ethan· Oct 9, 20264 min read
  • Adding AI to an app without a surprise bill
    Read post

    Engineering

    Adding AI to an app without a surprise bill

    Most of the cost of an AI feature is decided before the first request. Model routing, caching, context size and hard limits, in order of impact.

    Ethan· Oct 7, 20267 min read
nexa
ExploreServicesAboutTeamFAQBlogContact

© 2026 Nexa Tech. All rights reserved.

Web · Mobile · Open source