Module 2 of 12
Lesson 2: Positioning and Audience Clarity
Define who the app is for, what problem it solves, and how that promise should appear in metadata and creatives.
Why this module exists
Positioning decides what the metadata is allowed to promise.
A keyword bank built before positioning is settled is a keyword bank that will be rewritten twice. The work in this module — defining the core user and the job to be done, writing a one-line value proposition, and mapping search intent to user intent — is the bottleneck the rest of the curriculum waits on. Skip it, and Module 3 collects the wrong words; do it well, and Modules 3 through 5 almost write themselves.
Pay specific attention to category and competitive framing. Category and competitive choices are the cheapest decisions to make at this stage and the most expensive to undo six months later. The teams that quietly outperform competitors usually made one slightly braver positioning call here than the rest of the category was willing to make.
Lessons
Lesson 2.1
Define the Core User and Job-to-Be-Done
Clarify who the app serves, what trigger makes the user search, and what competing behavior already exists.
Lesson 2.2
Build a One-Line Value Proposition
Compress the product promise into one line that can later guide app name, subtitle, screenshots, and ad messaging.
Lesson 2.3
Map Search Intent to User Intent
Connect what users type into the App Store with the deeper problem or outcome they actually want solved.
Lesson 2.4
Category and Competitive Framing
Decide whether the app should be framed as utility, education, productivity, AI assistant, tracker, editor, or another market identity.
Key insights
Most App Store pages fail before keyword work; they fail at message clarity.
The first screenshot should answer what the app is, who it is for, and why the user should care.
Apply this module
The lessons above are written to be useful in order, but the work compounds when each one ends with a small concrete output: a written decision, a renamed field, a new entry in the keyword bank. Use the prompts below as the bare minimum the team should leave this module with.
Define the core user and job-to-be-done.
Write a one-line value proposition.
Map user intent to likely search intent.
Choose the right category and competitive frame.