The subtitle is the second most valuable field in an App Store listing and the one most often wasted. It gets indexed, it sits directly under the name, and Apple counts a word once whether it appears in the title, the subtitle or the keyword field.
Repeating words you have already used eats up thirty characters on nothing. A writer sees the three fields as one budget and makes a deliberate decision on how to allocate them.
Subtitles are read in a second while a thumb scrolls. The image and icon are already processing and competing before the subtitle is read. What gets processed is a promise in a sentence; a subject and a verb. No more. Fragments of nouns strung together to form a sentence are read as fillers. They are no better without a subject and verb even if each word is a keyword.
A model, when queried for a subtitle, responds with a title, two adjectives, and a placeholder for a field it knows nothing about. As is to be expected, it happily repeats words Apple has counted, and it has no problem going beyond thirty characters, since character count is a task it is not good at doing.
You need to provide your current title, keyword field and category so I can draft anything, since a subtitle only makes sense as the third part of a set. After that, they ‘play’ with the app until they find something worth the thirty characters that they would showcase as part of the single benefit. It is rare that this is the feature that a company takes the most pride in.
When a user first opens your app, they are measuring it against whatever the subtitle of your app promises. If your subtitle says scan a receipt in five seconds, then your first onboarding screen shouldn’t have a fifteen-field account form. We pit your subtitle alongside your onboarding and simply say the two don’t match when they describe different products.
One rate, whatever the format: $10 per 100 words. You are paying for the writer’s time and judgement, so the price scales with the words rather than with a package tier.
| Typical app subtitle | Words | Writing | Fee (1%) | You pay |
|---|---|---|---|---|
| Single option | 10 | $1 | $0.01 | $1.01 |
| Five variations | 30 | $3 | $0.03 | $3.03 |
| Full name set | 60 | $6 | $0.06 | $6.06 |
An app subtitle is shorter than our 100-word minimum order, so a single one is charged as 100 words ($10.10). Most clients commission these in batches, which uses the minimum properly — ask for however many options you want and we will quote the set.
The writer receives 100% of the writing price. Our 1% fee is added on top of it, and 0.5% is donated to tree planting. Full pricing breakdown.
Ask on the contact page and a person will answer, usually the same working day. For a live order, reply to your confirmation email and it reaches whoever is handling it.
Ask on the contact page and a person will answer, usually the same working day. For a live order, reply to your confirmation email and it reaches whoever is handling it.
It needs to be included in a new app version along with the rest of the build. That’s why the promotional text field is available for text that changes on a weekly basis. Normally, we put subtitles that will last for a release cycle along with some promotional text for more temporary messages.
We will suggest one, and we will always inform you about the words that the subtitle has covered already to avoid duplication in purchasing. Keyword research tooling is your call. What we bring in is the opinion about which term deserves the limited number of visible characters.
Completely. Copyright transfers to you on delivery, with no attribution requirement and no licence back to us. Nothing written for you is resold, repurposed or republished.
Reviews from completed, paid orders in this category.
Mostly excellent. Your improvements to the auth section are better than what our engineers wrote. Your pagination endpoints, however, were explained in the spec according to how they behave rather than how they are, which required two revisions. Our spec is incorrect in that area as well.
Our release notes went unread, but they serve the purpose of listing what breaks and what doesn’t when considering whether to upgrade. Two customers actually took the time to send thank yous in the same week, something that had never happened before.
Our releases happen every fortnight, and our notes have evolved into change logs. To keep things organized, the writer has noted what changed within a card or view and what changed underneath. Each note is a brief summary of the change. The biggest metric I’m interested in post release is the volume of support tickets. It always dips.
We do not ask you to take the no-AI promise on trust. Each draft is run through these platforms and the reports are attached to your delivery email.
Originality.aiAI detection + plagiarism
GPTZeroAI detection
TurnitinAI detection + similarity
CopyleaksAI detection + plagiarism
Winston AIAI detection
ZeroGPTAI detection
SaplingAI detection
Content at ScaleAI detection
Send the brief, get a human draft back within 3 days. No account, no subscription, no AI.
$10 per 100 words · all of it to the writer · 0.5% to trees