29 September 2026
What an App Store rejection actually looks like
Little Wins is a daily play planner for parents of young children. It went live on the App Store on 16 September 2026. Before that, Apple sent it back twice. The second rejection was about two short lines of text, the app's name and its subtitle.
This post covers what the reviewer objected to, what we changed, and why the rules are stricter than most people expect.
What the listing said
The app is called Little Wins. That name was already taken on the App Store by two live apps, so the store listing needed something longer. Apple caps the name at 30 characters. Our first choice, "Little Wins: Toddler Play & Learn", ran to 33.
So it was split in two:
- Name: Little Wins: Toddler Play
- Subtitle: Daily play & learn, ages 1-3
Apple indexes the name and subtitle for search, so splitting them lost nothing there. The name on the home screen stayed "Little Wins". Only the store listing carried the longer version.
The first bounce
The first rejection came on 8 September 2026 and had nothing to do with wording. Little Wins offers a subscription, and Guideline 3.1.2 requires a working link to the Terms of Use in the App Store description. Ours was on the paywall inside the app but not in the listing text.
The rejection arrived at 15:56. We added the Terms and Privacy links to the description and resubmitted at about 16:10. Every app we ship with a subscription now has both links in the description from the first submission.
The second bounce
The second rejection came on 10 September under Guideline 2.3.8, Accurate Metadata. The reviewer had tested the app on an iPad Air.
The objection was specific. The name "Little Wins: Toddler Play" and the subtitle "Daily play & learn, ages 1-3" suggested that the main audience was children. The app was not in the Kids category. To Apple, those two things contradicted each other.
The reviewer gave two ways out. Remove the child-audience wording from the name, subtitle, icon and screenshots, or move the app into the Kids category.
Why we did not move to Kids
Moving to Kids would have been the quicker fix. It would also have been wrong.
Little Wins is used by the parent. The parent opens it, reads the day's plan and sets up the activities. The child never touches the phone. The honest category is Education, which is where it was.
The Kids category also carries its own obligations. Under Guidelines 1.3 and 5.1.4, apps in it cannot use third-party analytics without verifiable parental consent. Those rules exist for good reasons, and they are designed for apps that children use directly. Taking them on to get past a naming objection would have made the listing less accurate, not more.
So we kept the category and changed the words.
What changed
- Name: Little Wins: Parent Planner
- Subtitle: Daily play ideas for parents
That was the whole fix. The icon is a plain seedling and the six screenshot captions already spoke to the parent, so neither needed touching. The description mentions an age range of 12 months to 3 years. The reviewer did not flag it, so it stayed.
"Toddler" did not disappear from search. It moved into the keyword field, which Apple uses for search but does not show on the listing. For that submission we kept it out of the name and subtitle entirely. A third rejection would have lost several more days, and the safest wording was the one with no room for a second reading.
The reply to App Review was short. Little Wins is a planning tool for parents and carers. Children do not interact with it, which is why it is not in the Kids category. The name and subtitle now make the audience clear. The icon and screenshots already showed the parent-facing planner.
It was approved and went live on 16 September. A later update changed the subtitle to "Toddler activities, planned" and passed review without comment. With "Parent Planner" in the name, the audience was no longer in doubt, and the word on its own was not the problem.
Why the rules are stricter than most people expect
Most people treat an app's name as marketing. Apple treats it as metadata, and 2.3.8 requires metadata to be accurate.
The reviewer is not judging intent. They read the listing literally. "Toddler Play" describes a child playing. Read that way, the child is the user. And a child user brings a whole set of rules about privacy, advertising, analytics and parental gates. The words in the title decide which rulebook the app is held to.
The 30-character limit makes this harder. Compression pushes you towards short, vivid phrases, and short phrases are the ones most open to a second reading. "Toddler Play" is three syllables of perfectly good copy. It is also, on a literal reading, a claim about who the app is for.
The same applies beyond the name. Screenshots, the icon, the subtitle and the category all get read together. A listing that says one thing in its title and something else in its category will be asked to pick one.
It is worth saying that the process itself was fair. Each rejection named the guideline, the device and the exact text at issue. Each offered a clear way forward. Neither was a dispute. They were corrections, and once the listing described the app accurately it went through.
What this means if you are planning an app
The store listing is part of the build. The name, subtitle, category, screenshots and privacy answers all go through review alongside the code, and any one of them can hold up a release. We write them with the same care as the app itself, and we decide the category early, because that choice shapes what the app is allowed to collect and how it has to behave.
Little Wins is one of the apps we have live on the App Store and Google Play. More about how we approach this work is on the app development page. We work with clients in Sutton Coldfield, Great Barr and well beyond. If you have an app in mind and would like to talk it through, we would be glad to hear about it.