DEV Community

ReviewFold
ReviewFold

Posted on

Why Pooling iOS and Android App Store Reviews Hides Half Your Engineering Bugs

When mobile engineering and product teams look at user feedback, one habit causes more misdiagnosis than any bad prompt: exporting App Store and Google Play reviews into the same spreadsheet and averaging the complaints together.

It looks tidy on a slide. In practice, it buries half your real engineering signal.

On November 18, 2026, we collected 200 most-recent US public reviews per storefront across Goodnotes (Apple US + Google Play US), MyFitnessPal (Apple US + Google Play US), and Cronometer (Google Play US)—1,000 reviews total—to compare what iOS and Android reviewers actually report. Two storefronts under the exact same company were rarely complaining about the same thing.

Disclosure: I build ReviewFold, a research tool that analyzes public App Store (US/CA) and Google Play (US) reviews one storefront at a time and lets teams compare completed reports side by side. I used deterministic keyword checks and AI editing assistance on top of our saved November 18 review snapshots.

First, check the sample calendar windows before comparing counts

Because both storefronts are bounded snapshots of the latest 200 written reviews rather than date-locked exports, the calendar spans differ sharply by app and platform:

App & Storefront Sample Size Date Window (UTC) 1–2★ Count
Goodnotes · Apple App Store US 200 2026-10-06 – 2026-11-16 (42 days) 97 (48.5%)
Goodnotes · Google Play US 200 2026-09-03 – 2026-11-17 (76 days) 102 (51.0%)
MyFitnessPal · Apple App Store US 200 2026-10-28 – 2026-11-17 (21 days) 100 (50.0%)
MyFitnessPal · Google Play US 200 2026-10-29 – 2026-11-17 (20 days) 84 (42.0%)
Cronometer · Google Play US 200 2026-10-21 – 2026-11-17 (28 days) 50 (25.0%)

These numbers reflect those 200-review snapshots at collection time, never total active users. Even keeping those distinct date spans in mind, the architectural divergence between stores is stark.

Divergence 1: Goodnotes (iPad ergonomic bugs vs. Android web-wrapper latency)

In Goodnotes’ Apple US snapshot, 18 of 200 reviews mention AI features and complaints cluster heavily around Goodnotes 6 Special Edition upgrades, mandatory Goodnotes accounts, and iPad editor regressions:

"Just upgraded to the new app and there are so many bugs. 1) if you color in a shape it just un-colors it and leaves the outline only 2) when you leave the app it doesn’t take you back to all your open notebooks, it takes you to the browsing screen and you have to find and click what you were working on 3) moving the undo bottom to the top left means as a right handed writer I have to travel to the opposite side of the iPad and cover the page" (Apple US · 2★ · Nov 15, 2026)

Switch to the Android snapshot (us-goodnotes-google.json) and AI disappears completely: 0 / 200 mentions of AI. Instead, 48 / 200 focus on Android/cross-platform friction and 68 / 200 cite lag, crashes, or export bloat—complete with build version 2.0.12 (v330419):

"goodnotes for ipad was wonderful, but totally worthless in Android.its a struggle to even import a file from drive, requires internet connection even to open asystem file. takes forever to even load a file. on top of all, I had to pay 999 rupees for this poor user interface." (Google Play US · 1★ · Nov 10, 2026 · v2.0.12 (v330419))

"export size become more larger and time taking..I used to take same page atmost 9mb now taking 90 mb and export time is increased from 30 sec to 5 min" (Google Play US · 1★ · Nov 12, 2026 · v2.0.12 (v330419))

Yet the Android store isn't universally failing either—niche PDF markup workflows still score cleanly:

"Brilliant program for keeping track of full coverage, complicated cross stitch designs. Thank you." (Google Play US · 5★ · Nov 10, 2026)

If an engineering PM mixed Apple and Android CSVs together, the iOS account-flow fire would dilute Android’s 9MB -> 90MB PDF export regression—or worse, leadership might prioritize AI polish over offline Android parity. For a full side-by-side framework on splitting stores, see our App Store vs. Google Play review analysis guide.

Divergence 2: MyFitnessPal & Cronometer (broken iOS UI controls vs. Android OS sync loops)

Even in overlapping fall windows (MyFitnessPal Apple 21 days from Oct 28 vs. Google Play 20 days from Oct 29), native Android and iOS bugs hit completely different layers of the stack.

On Apple US, MyFitnessPal reviewers flag dead bottom-bar interactive buttons after redesign updates:

"The app UI has been changed so much that it’s hard to navigate. It’s hard to navigate to your recipes, and a lot of the simple features don’t work anymore. For example, now when I go into a meal I have saved and click the “Edit” button, the button doesn’t do anything. I also can’t create a new meal because when I try to click the button there is no response." (Apple US · 2★ · Nov 16, 2026)

Not everyone dislikes the update—counter-evidence matters too:

"I’ve been using MyFitnessPal since 2006 and it’s always been a lifesaver. The new updates make the app easier to use and I tell everyone I know about it. It will help them too!" (Apple US · 5★ · Nov 17, 2026)

Meanwhile on Google Play US, MyFitnessPal feedback isolates exact release build 26.45.0 issues—third-party app syncing and removed breakdown views:

"sync with mapmyrun never works constantly having to deinstall reinstall boths apps, disconnect then reconnect and update them both and it still only works intermittently" (Google Play US · 2★ · Nov 16, 2026 · v26.45.0)

"Meal macro breakdown screen is gone, it's the main reason I pay for this... please bring it back!!" (Google Play US · 1★ · Nov 15, 2026 · v26.45.0)

And Cronometer on Google Play highlights Android-only system integrations like Google Health Connect (v4.58.0) and signup wizard state (v4.60.4)—alongside a separate ad-timing conversation we unpacked in our Cronometer vs. MyFitnessPal US review comparison:

"sync with health connect is unreliable. both energy expenditure in from health connect and energy intake out to health connect. days where cronometer says random 11,000 calorie expenditure days, and where health connect sync is missing tracked days." (Google Play US · 1★ · Nov 15, 2026 · v4.58.0)

"i can't get to the 2nd page of sign up. the 'next', button won't highlight or work. tried twice." (Google Play US · 1★ · Nov 16, 2026 · v4.60.4)

Three practical rules for developer review triage

  1. Preserve storefront and appVersion before clustering. Public Google Play records include build tags (v2.0.12, v26.45.0, v4.58.0), while public Apple RSS feeds omit them. Mixing both hides which release introduced a regression.
  2. Sort raw store quotes before filing Jira tickets. A 5-star review may carry a crisp feature request, while a 1-star "can't log in" complaint belongs in a Needs more info hold row rather than an engineer's sprint queue. You can grab our blank 12-column feature request vs. bug report triage template to keep raw quotes separate from engineering hypotheses.
  3. Compare completed per-store reports side by side. Analyze Apple App Store and Google Play independently on the same competitor before making roadmap bets.

If you want to pull 200 recent public reviews for either Apple App Store (US/CA) or Google Play (US) and compare completed store reports side by side with exact quotes attached, try a free preview on ReviewFold.

Top comments (0)