Mobile QA beyond “run it on BrowserStack”
Device farms are useful. They are not a strategy. What I actually check on native, mobile web, and wearables.
BrowserStack and physical devices answer different questions. Farms give breadth and regression speed. A phone in your hand catches install friction, permission prompts, keyboard behaviour, and the awkward paths users hit between buildings and lifts.
My mobile thread has been consistent for years: native iOS and Android, mobile web, and — when the product needs it — wearables. The point is not collecting devices. It is mapping journeys that cross app, API, and hardware.
A useful mobile plan usually covers: critical install and upgrade paths, offline or poor-network behaviour where relevant, push and deep links, compatibility across a small real matrix, and release readiness notes Product can actually read.
I also raise functional improvements as stories or low-priority defects when something works but still fights the user. That is not scope creep. It is cheaper than discovering the same friction in UAT or production.
If your “mobile QA” is only a BrowserStack checklist, you are testing screenshots of confidence. Pair farm coverage with a few deliberate physical-device sessions and you get decisions, not just green ticks.
Marius Ene
Senior Functional QA · user & business focus