Languages and scripts
Every app review from India can be in a different language: users often mix English with Hindi or regional languages, in Roman or native scripts. Analysis that reads only English misses part of your users.
Play Store reviews in other languages.
Play store reviews in other languagesDevices and networks
- A wide range of phones, including low-memory devices.
- Older Android versions still in use.
- Patchy connectivity outside major cities.
- Data-usage and app-size concerns.
Topics that come up often
- UPI and payment failures.
- OTP delays.
- App size and data use.
- Performance on budget phones.
- Language support in the app itself.
Analysing them well
- Classify every language with a multilingual model.
- Tag device and OS mentions.
- Compare complaint shares by version and, where available, by device.
- Check accuracy by language monthly.
Free review snapshot
Want this done for your own reviews?
No commitment. We use your details only to send your snapshot and follow up. Privacy policy
An example
A grocery app's reviews from smaller cities complained about slow loading and data use, mostly in Hindi. A lighter image mode for slow connections, announced in Hindi and English replies, reduced those complaints over two releases.
Common mistakes
- English-only analysis.
- Testing only on flagship phones.
- Ignoring data-use complaints.
- Machine-translated replies without checks.
Common questions
Which languages are most common?
It depends on your audience; count your own reviews.
Are Indian users harsher reviewers?
Avoid generalising; compare your app with itself over time.
Should the app support more languages?
Review complaints about language are a useful signal.
Do reviews mention device brands?
Often; tag them.
Checklist
- All languages analysed.
- Device and OS tagged.
- Payments and OTP watched.
- Accuracy checked by language.
In short
Expect many languages, varied devices and networks, and frequent payment and OTP topics; analyse every language and compare by device and version.
Testing for real conditions
Use review mentions to shape testing: if users mention slow loading on budget phones or failures on older Android versions, add those devices and network conditions to release testing. Reviews from Indian users are often a precise guide to the conditions your app actually runs in.
Replying to Indian users
Reply in the user's language where your team writes it well, keep replies short, and give a support route for payment or OTP problems. Suggested replies in Play Console cover recent English reviews only, so plan for people to handle other languages.
Comparing regions
If your app serves several regions, compare complaint shares by language as a rough proxy for region. Differences often point to network conditions, language support or payment methods that vary by area.
Support expectations
Many users expect support in their language and through chat or phone, not just email. Reviews that mention unreachable support often follow a payment or delivery problem; the support complaint makes it worse. Track support mentions alongside the problems that trigger them.
Payment methods
UPI, wallets, cards and cash on delivery each produce their own complaints. Tag the payment method when users name it; a failure that affects one wallet is a very different fix from one that affects all.
City tiers
Users in smaller cities often write about network and device limits more than metro users; compare complaint shares by language or region to see it.
Doing this with Falcon
Falcon classifies every Google Play review of your app into feature areas and specific issues with the sentiment of each mention, on the same taxonomy as your store reviews but kept separate. Negative share by area and month shows what is new or growing, and every issue opens the reviews behind it.