Method & Empirical Study · Cross-Storefront Research
App Store vs. Google Play reviews: Do iOS and Android users complain about the same things?
Product teams routinely combine Apple App Store and Google Play reviews into one sentiment average. Across 800 US reviews pulled the same day for Goodnotes and MyFitnessPal (200 per storefront), pooling stores erases the exact platform architecture and version bugs your roadmap needs.
- Apps studied
- Goodnotes + MyFitnessPal (+ Cronometer Health Connect note)
- US snapshots
- 200 reviews × 4 primary snapshots = 800 rows
- Goodnotes 1–2★
- Apple 97 (48.5%) · Google 102 (51.0%)
- MyFitnessPal 1–2★
- Apple 100 (50.0%) · Google 84 (42.0%)
- Product workflow
- 1 store per report; compare completed reports side by side
On this page
- Four US snapshots compared
- Case 1: Goodnotes iOS vs. Android
- Case 2: MyFitnessPal overlapping fall windows
- Four cross-store rules
- Questions
ReviewFold deliberately analyzes one storefront at a time (Apple US/CA or Google Play US) and lets you compare completed reports side by side—so store regressions never blur together.
01 · Four US snapshots compared
Same company, different product failures
Even when collected on the same day, fixed 200-review snapshots span different calendars across stores—yet two storefronts under the same brand still surface very different product failures.
| App & Storefront | Window & 1–2★ Share | Dominant Complaint Signal | Metadata Difference |
|---|---|---|---|
| Goodnotes · Apple App Store US | Oct 6–Nov 16, 2026 (42 days) 97 / 200 (48.5%) |
Account prompts before upgrading to Special Edition, update UI shifts, AI mentions: 18/200 | App version omitted in Apple public RSS feed |
| Goodnotes · Google Play US | Sep 3–Nov 17, 2026 (76 days) 102 / 200 (51.0%) |
AI mentions: 0/200; cross-platform/Android complaints hit 48/200 & crash/lag hits 68/200 | Exposes exact build string (e.g., 2.0.12 (v330419)) |
| MyFitnessPal · Apple App Store US | Oct 28–Nov 17, 2026 (21 days) 100 / 200 (50.0%) |
Unresponsive bottom-bar Edit and create-meal buttons, screen-filling ads, barcode gating |
Overlaps Android’s span (starts 1 day earlier: Oct 28 vs. Oct 29), no build string |
| MyFitnessPal · Google Play US | Oct 29–Nov 17, 2026 (20 days) 84 / 200 (42.0%) |
MapMyRun sync uninstall/reinstall cycles, missing Meal macro breakdown screen, forced streak popups |
Pinpoints build 26.45.0 cleanly |
Goodnotes · App Store US
97 1–2★- Window
- Oct 6–Nov 16, 2026
- Top signal
- Account/upgrade friction, 18 AI mentions
Goodnotes · Google Play US
102 1–2★- Window
- Sep 3–Nov 17, 2026
- Top signal
- 0 AI mentions · 48 cross-platform · 68 crash/lag
MyFitnessPal · App Store US
100 1–2★- Window
- Oct 28–Nov 17, 2026
- Top signal
- Broken bottom Edit/Create buttons + ads
MyFitnessPal · Google Play US
84 1–2★- Window
- Oct 29–Nov 17, 2026
- Top signal
- v26.45.0 MapMyRun sync, macro screen gone
02 · Case 1: Goodnotes
On Apple, users debate licenses and AI; on Android, they fight a slow web wrapper
If a researcher only checked iOS App Store reviews for Goodnotes, they would completely miss that Android users never mention AI—and instead protest internet dependency and 10× PDF bloat.
-
“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.”
Platform divergence: the reviewer compares Android directly against iPad—not against Notability.
-
“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”
Concrete performance metric tied to Android v2.0.12—absent in the Apple US snapshot.
-
“Brilliant program for keeping track of full coverage, complicated cross stitch designs. Thank you.”
Counter-evidence: even on Android, lightweight PDF annotation niches rate the app 5 stars cleanly.
03 · Case 2: MyFitnessPal (Overlapping fall US windows)
Two native codebases breaking two separate daily habits
Across closely overlapping late-October to mid-November windows (Apple 21 days from Oct 28 vs. Google Play 20 days from Oct 29), Apple users report unresponsive food editing controls, while Android v26.45.0 reviewers isolate MapMyRun integration and missing meal macro screens—just as Android Cronometer isolates Health Connect failures.
-
“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.”
iOS UI regression hitting core bottom-bar food creation flow.
-
“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”
Android ecosystem permission & cross-app sync friction pinpointed to v26.45.0.
-
“Meal macro breakdown screen is gone, it's the main reason I pay for this... please bring it back!!”
Subscriber feature disappearance specific to this Android rollout.
-
“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!”
Counter-evidence: redesign complaints are never unanimous—20-year fans still praise the updated navigation.
-
“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.”
Cross-store bonus: on Android, Cronometer catches Google Health Connect data corruption bugs (
v4.58.0) that never exist on iOS Apple HealthKit.
04 · Cross-store methodology
Four rules before comparing Apple and Google reviews
- Keep stores separate until coding finishes Generate one report for Apple App Store US and a separate report for Google Play US, then compare the completed reports side by side without pooling counts.
- Check whether date windows align Review velocity differs wildly by platform; read how many days 200 reviews cover before quoting shares.
- Harvest version tags from Google Play Public Google Play payloads carry
appVersionstrings (26.45.0,2.0.12,4.58.0) that isolate exact release regressions faster than Apple RSS. - Separate platform architecture from pricing strategy An Android web-wrapper delay requires engineering investment; an iOS hidden one-time license flow is a billing UX change.
05 · Questions
Cross-store research questions
Does ReviewFold combine Apple App Store and Google Play into one single report?
No. ReviewFold analyzes one app and one storefront per report (Apple US/CA or Google Play US, up to 200 recent reviews), and lets you run completed reports side by side across 2–3 entries so Apple and Android signals never bleed together silently.
Why not always start with Google Play if it includes app version strings?
Some categories monetize or break very differently on Apple hardware—as Goodnotes proved, where Apple users discuss Apple Pencil ergonomics, Special Edition licenses, and AI features that barely appear in Android snapshots.
Compare stores cleanly
Test both storefronts side by side on your top competitor.
Run Apple US/CA and Google Play US separately (1 free preview every 24h; $9.99/mo for 5 full reports + side-by-side comparison at zero extra credit).