When you build an app with Rork, it often drafts a store description for you alongside the app itself. It's a handy feature—but pasting that text into App Store Connect without touching a word usually sells your app short. Generated descriptions are good at listing features accurately, yet they pay almost no attention to where people actually read on a store page.
Here's the thing: most people never see your full description. On an iPhone, they see the handful of lines above the "more" link, and that's it. If you have 30 minutes this weekend, I'd start exactly there. Rewriting the opening is faster than redoing screenshots, and the payoff shows up sooner too.
Half the Decision Happens Above "More"
Open an app's page on an iPhone and the description is collapsed. You get roughly the first three lines; reading the rest means tapping "more." And far fewer people tap it than you'd hope. They swipe through a couple of screenshots, glance at the opening lines, and decide right there whether to download. That's how most browsing actually goes.
So no matter how carefully you describe a feature in the fourth paragraph, that text barely reaches the first decision. Rork's generated descriptions tend to open with something comprehensive—"This app lets you do X, supports Y, and includes Z"—but listing feature names above the fold rarely moves anyone.
Across the apps I've run, the lesson has been consistent: change the opening lines from a declaration of features into a nod to the reader's situation, and the same app gets installed differently. And it really is just a few lines of work.
The Opening Means Something Different on iOS vs. Google Play
There's an easily missed distinction here. Even for the "start of the description," the App Store and Google Play play by different rules.
On the App Store, the description has almost no effect on search ranking. Apple's search leans on the app name, subtitle, and keyword field. That frees the iOS opening to be pure persuasion rather than SEO—you don't need to stuff keywords in.
Google Play, by contrast, has a separate 80-character "short description" field, and that one is indexed for search. It also appears on the listing, headline-style, ahead of the full description. So the Google Play opening has to do double duty in 80 characters: words that help search and words that move the reader. It's the tighter constraint of the two.
Reuse your iOS opening verbatim on Google Play and you throw away search visibility. If you ship to both stores, write the openings separately—that's my default. If you want to tighten the search side further, pair this with Squeezing Every Pixel of Value Out of Your App Store Keyword Field.
A Simple Template for the First Three Lines
You don't need fancy copywriting. Here's the three-sentence template I actually use.
Line one names the reader's situation. Not the app, not a feature—the small worry or wish they have right now. For a water-tracking app: "By evening, do you ever forget how many glasses you've had?"
Line two says what the app does for them, framed as a result rather than a feature name: "Log it in one tap and see what's left for today at a glance." Show the after-state.
Line three removes one hesitation. Free to start, no sign-up, ads kept light—whatever quiets the doubt right before a download. "No account needed; open it and go."
Once those three lines are in place, let Rork's detailed feature rundown follow below them. The collapsed section becomes the careful explanation for people curious enough to tap "more." Hook them up top, reassure them further down—a clean division of labor.
After Rewriting, Always Check on a Real Device
Don't call it done on paper. Preview the actual listing and see how the opening renders. Use the App Store Connect preview, or your live listing on a real device, and count how many lines sit above "more." Languages with wider characters collapse sooner than you'd expect, so make sure your most important words in line one haven't been pushed below the fold.
Line counts shift with device and text-size settings. The safe move is to put your single most important phrase in the first half of line one. Tuck it at the end and some screens will cut it off.
When you're ready to polish the whole listing—screenshots, featuring, and all—A Practical Guide to App Store Custom Product Pages (CPP) for Rork Apps is a good next read.
For now, open your current listing and rewrite just the first three lines. Keep the generated text as your foundation, but make the part that gets read first sound like you. That small bit of effort is what supports the final nudge toward a download. Thanks for reading.