The real job of a Play Store page
An app store listing isn't a landing page — it's a three-second verdict. The user arrives from a search result or a share link with exactly one question: is this the thing that solves my problem, yes or no. Everything else — social proof, feature tables, the changelog — is for the 5% who stay. The first three seconds have to close the other 95%.
That framing governed every decision below. Positioning, icon, short description, first three screenshots, keyword surface — each had to carry load independently, because most users only ever saw a subset.
The positioning line — six words, written nineteen times
Handwritten to print-ready in seconds.
We wrote and discarded around nineteen versions before this one locked. Every earlier draft either (a) named the technology ("Gemini-powered exam scanner") — which was true but meaningless to a teacher; or (b) named the feature ("Turn photos into printable exams") — which sounded like every other OCR app in the category. The final line earns its place by naming only the transformation: what the user has before ("handwritten"), what they have after ("print-ready"), and the perceived cost ("in seconds"). Nothing about the app itself.
That line got promoted into every surface: the Play Store short description, the WhatsApp share preview, the landing page H1, the launch tweet, the onboarding splash. Consistency was more important than cleverness. If a teacher saw the app three times in three different places, the sentence was the same sentence each time — that repetition is what brand memory is actually made of, at this scale.
The screenshot ladder — optimized for "swipe twice and bounce"
Play Store telemetry is blunt, but one thing it does measure well is how many screenshots users look at before they either install or leave. For us, the median was 2.3. That number dictated the entire screenshot strategy:
- Screen 1 — the promise. A split-frame showing a handwritten exam page on the left and a clean, formatted PDF on the right, with a single caption: Handwritten to print-ready. No UI. No chrome. Just proof.
- Screen 2 — the action. An in-app screenshot of Gemini extracting structure from a scan, with annotations showing it identifying MCQ blocks, section headers, and marks. This is where the skeptical teacher decides we're not another OCR wrapper.
- Screen 3 — the result. The exported PDF rendered at A4 with a school logo, multi-column layout, and correctly placed chemistry notation (H₂SO₄, integrals, Devanagari). This is what they actually need to print Monday morning.
Screens 4–6 cover features — fairness pricing, offline mode, rescan-append. They exist for the conscientious 30% who read everything, but we accepted they would have close to zero impact on the install-decision curve.
Screens 1–3 were tested against a B variant (screens 1–3 showed features instead of transformation) with roughly 200 impressions per arm before we called it. Install rate on the transformation-led ladder was a meaningful delta — not publishable-level significant at this sample size, but directionally clear enough, and the qualitative signal ("it's the only one that showed a before and after") was unambiguous.
Keywords — writing for humans, labeled for the algorithm
The standard ASO advice is to stuff the long description with every keyword variant you can justify. We didn't. The long description reads as prose a teacher could show a colleague without embarrassment. The keywords are instead planted where they actually earn ranking weight: in the app title (PaperLoop — Exam Scanner for Teachers), the short description (120 chars, every word load-bearing), and the first 160 characters of the long description (which is all that shows before the "more" fold).
Keyword bets were explicit:
- "Exam scanner" / "question paper" — the high-intent head terms. Competitive, but the positioning line is literal to both.
- "Handwriting to PDF" — mid-intent, lower competition. This is the search a teacher runs at 11pm when they give up on Word.
- "School printable" / "teacher tools" — category framing. Lower immediate conversion, but defines the neighbourhood we want to live in for future related-app surfacing.
We consciously did not bid for "OCR" or "scanner" standalone. The volume was tempting, but the intent mismatch was fatal — those users want CamScanner, and our uninstall-reason code would spike the moment they realised we were a different thing entirely.
Launch day — no paid, two Reddit posts, one WhatsApp forward
Zero paid acquisition. The launch plan was three things: a post in r/IndianTeachers framed as a tool I built for my aunt (true), a parallel post in r/Teachers as a wider-audience variant, and a three-message WhatsApp announcement seeded to the same fourteen teachers I had originally interviewed, with explicit permission to forward.
Within seven days we had 200 installs. The geographic spread was the real signal — teachers in Jaipur, Coimbatore, and Siliguri who had never heard of me meant the Play Store listing was closing the install on its own, without requiring a trusted messenger. That's the only ASO metric I actually trust: can the page do the job when I'm not in the room.
What I'd watch next
The weakness in the current listing is the rating bar — at 4.6 with 14 reviews, it reads as "new." The next cycle's work is a non-invasive in-app review prompt, triggered only after two successful scans and one successful export, never after a failed scan. A prompt after failure is what kills apps in this category, not a prompt after success.
The keyword work is also not finished. Once we cross a thousand installs, the Play Console starts surfacing which search queries are converting — at which point the short description rewrites itself from evidence instead of intuition, and the current positioning line either proves itself or needs the twentieth draft.