Why this lesson matters
If the audience and job are blurry, the metadata and product page will also be blurry.
Core idea
Positioning begins with the user’s job, not the app’s features.
Real-world example
An invoicing app wins after narrowing the audience
An invoicing app says it is for every business. After narrowing the page to freelancers and solo consultants, the messaging becomes much easier to write and much easier to understand.
Why the example matters
The clearer the user, the clearer the App Store page.
Let's make it clearer
Start with the trigger moment, not a marketing persona
A useful App Store audience definition starts with the moment that creates demand. The team should ask what happened just before the user searched, browsed, or clicked through to this kind of app. That moment usually produces clearer language than a broad persona document ever will.
This method matters because App Store messaging has very little space. If the audience is defined too broadly, the subtitle becomes vague, the screenshots become generic, and the keyword plan drifts away from real demand. A sharp trigger moment keeps every later field more focused.
Define who the user is in one line of plain language.
Define what happened that made the app feel necessary now.
Define what the user would do if this app did not exist.
Map the real competitors, including non-app behavior
Many teams only compare themselves to direct App Store competitors. That is incomplete. The real competition often includes spreadsheets, notes apps, browser tabs, manual habits, or not solving the problem at all. Those alternatives shape what the user expects to see on the product page.
Students should write down both app competitors and substitute behaviors. This usually reveals better screenshot headlines and more honest metadata because the listing starts speaking to the actual job instead of only to category peers.
Step-by-step framework
Name the core user in plain language.
Describe the problem moment that creates demand.
List existing alternatives, including offline or manual behavior.
Write a one-sentence job-to-be-done statement.
Practical exercise
Write one job-to-be-done statement and one “what the user was doing before the app” statement.