What feature do users request most across app categories?

Integrations and sync are the single most-concentrated feature class, with Productivity leading at 20% of requests (1 in 5) mentioning integration, sync, calendar, or API. The single most universal request, though, is editing and bulk-management — 9-17% of requests in every category. Across 40,000+ App Store reviews matched to category, users overwhelmingly ask for the app to talk to their other tools, then to let them clean up what they already entered.

Are feature requests usually from happy or unhappy users?

It depends entirely on the category, and the gap is sharper than founders typically realize. In Finance (60% from 4-5★), Games (58%), Health & Fitness (54%), and Productivity (51%), most requests come from happy users — these are love letters. In Travel (54% from 1-2★), Lifestyle (48%), and Food & Drink (50%), most come from blocked users — these are churn warnings disguised as suggestions. Business sits genuinely split at 42% blocked / 40% happy.

Should I build offline mode or push notifications?

Offline mode is essentially dead as a feature request — 0 to 0.2% of requests across every App Store category mention it. It's table stakes now, not a differentiator. Notifications are sparser (2-6% by category) but not quite as buried; in Productivity (5%) they're still a meaningful share. Neither belongs in a launch headline in 2026.

What is a conditional upgrader review?

A review that says the product would be perfect if it had X. These cluster at 3-4 stars and are the most actionable reviews you have — a user naming the single thing between them and a five-star rating. The pattern is dense in Health & Fitness and Productivity (where users see clear potential they're not getting), thinner in Travel and Food & Drink (where blocked users tend to leave rather than negotiate).

What users ask for, by category

"Users are asking for X" is one of the most-repeated and least-useful sentences in product. Across 40,000+ App Store reviews matched to App Store category (is_spam = false), what people request — and what the request actually means — splits sharply by vertical. The words look the same. The urgency behind them is opposite.

We re-ran every claim below as a direct SQL aggregation against the corpus (Klarion's app_store_reviews × app_store_apps join, June 2026 snapshot) so every number is reproducible.

Every vertical has a signature ask

Filtering to reviews containing an explicit request word (wish, please add, needs to, missing, would love, should add, hope), the dominant feature ask in each category is sharper than the surrounding noise:

Productivity — integrations (449 requests, 20% mention integration/sync/calendar/API/Zapier). The single most concentrated ask in the whole dataset. Followed by edit/undo/bulk (13%) and platform parity (12%). Users don't want a bigger app; they want their app to talk to everything else.
Business — platform parity AND edit/bulk, basically tied (718 requests, 11% platform / 10% edit). Business users live across iPad, desktop, and web — but they spend almost as much energy asking to fix what they already entered.
Health & Fitness — diffuse (1,038 requests). The Apple Watch ask is real (8%) but not dominant — it's tied with integrations (8%) and edit/bulk (9%). The wearable matters; it doesn't define the category.
Finance — get my data out (226 requests, 12% export/CSV/PDF/receipt). The highest data-portability demand of any category, narrowly ahead of integrations (11%). Finance users want sovereignty over their numbers.
Travel — fix what's broken (63 requests, 17% edit/bulk, 10% platform). Travel users barely ask for features; they ask for the app to stop blocking them.

"Great app. I would suggest add support for Apple Watch."

— 4★ review, Health & Fitness app — the classic ask shape

Two patterns cut across everything.

9–17% of feature requests in every category are for edit / undo / bulk / fix-what-I-already-entered. The least glamorous feature class is the most universal. People don't ask for more power; they ask to clean up the mess the app let them make.
Klarion analysis of 40,000+ App Store reviews matched to category (`is_spam = false`), June 2026 snapshot.

0–0.2% of feature requests across every category mention offline mode. Shipping "offline mode" as a headline feature in 2026 wins no one. Notifications are similarly sparse (2–6% across categories), though not quite as buried.
Klarion analysis of 40,000+ App Store reviews matched to category, June 2026 snapshot.

The same request means opposite things

Here is the part that matters. The temperature of a feature request — whether it comes from a happy or an unhappy user — flips entirely by category. Numbers below are direct aggregations from the request corpus, June 2026:

| Category | Happy (4–5★) | Blocked (1–2★) | Reading | |---|---|---|---| | Finance | 60% | 27% | A request is a love letter. | | Games | 58% | 24% | Engaged fans pulling forward. | | Health & Fitness | 54% | 30% | Mostly satisfied users with one missing piece. | | Productivity | 51% | 34% | Balanced, leaning positive. | | Education | 46% | 38% | Genuinely mixed. | | Business | 40% | 42% | Slightly more blocked than happy. | | Food & Drink | 40% | 50% | The request is a churn warning. | | Lifestyle | 33% | 48% | Heavily blocked. | | Travel | 38% | 54% | A request is the last thing standing between the user and abandonment. |

"It could be good to add an export option like ODS, XLS, and PDF."

— 4★ review, Finance app — a satisfied user pulling you forward.

"Stupid app won't let me order, says I need to update the app, but no update is available!! Super frustrating."

— 1★ review, Food & Drink app — not a suggestion, a blocker on the way out.

In Finance, Games, Health, and Productivity, a feature request is roadmap fuel: ship it and you convert an advocate into an evangelist. In Travel, Lifestyle, and Food & Drink, the same request is the last thing standing between the user and abandonment — ignore it and they're gone. Business sits in the middle, the request distribution genuinely split — same words can mean either thing depending on the reviewer.

The conditional upgraders

One request pattern is worth isolating: "this would be perfect if it had X." These conditional upgraders cluster heavily at 3–4 stars and barely exist anywhere else. They are the most actionable reviews on your page — a user telling you the exact, single thing between them and a five-star rating.

"This is a great logger with nice features. It would be perfect if it had a web interface so I could type my workouts on the web and then just log at the gym."

— 5★ review, Health & Fitness app

What to do with this

Never act on "users are asking for X" without the rating distribution behind it. The same words carry opposite urgency depending on who's writing them. A team that treats a Finance request and a Travel request identically will over-invest in polish for happy users while blocked users quietly churn — or the reverse. Read the star rating, not just the words. It tells you whether you're looking at a wish or a warning.

The honest framing: requests from satisfied users (Finance, Games, Health, Productivity) are signals about what your most-engaged users want next. Requests from blocked users (Travel, Lifestyle, Food & Drink) are signals about what's already broken. Same vocabulary. Opposite triage queue.