Series

Mobile QA.

The mobile-specific risks web-first teams miss — lifecycle, network, permissions, and updates. Web testing trains assumptions that quietly break on mobile. This series covers why mobile bugs escape web-first teams, the device-real smoke test before release, and the tool choice for automating it.

Who it's forWeb-first QA teamsMobile testers

// overview

Web testing trains a mental model — a page loads, you interact, you assert — and mobile quietly violates every assumption in it. Apps get backgrounded and killed, networks switch mid-request, permissions get denied, and every version you've ever shipped runs at once. This series is about the bugs that escape teams who test mobile like a smaller website.

It explains why the bugs escape (the invisible assumptions), gives you a device-real smoke test that exercises lifecycle, network, interruptions, permissions and the upgrade path, and covers the tool choice for automating it.

Read it before your next mobile release — especially if your team grew up on web.

// reading order

  1. Opinions·13 June 2026 · 7 min read

    Why mobile bugs escape web-first QA teams

    Web-first teams carry assumptions that quietly break on mobile — permissions, offline state, lifecycle, and updates.

    mobile-testingopinion
  2. Tutorials·13 June 2026 · 7 min read

    My mobile smoke test before every release

    A short, device-real smoke pass: permissions, offline, rotation, interruptions, and the update path.

    mobile-testingchecklistrelease
  3. Tutorials·13 June 2026 · 8 min read

    Push notification testing: what usually goes wrong

    Notifications behave differently foregrounded, backgrounded, and killed — and deep-link to the wrong place when they arrive. The killed-app cold start is where it breaks.

    mobile-testingnotificationsbugs
  4. Tutorials·13 June 2026 · 8 min read

    Offline mode bugs every mobile tester should check

    The interesting offline bugs are in the transitions, not the offline state: double-submits on reconnect, in-flight requests that die, optimistic UI that never rolls back.

    mobile-testingofflinebugs
  5. Comparisons·2 December 2025 · 9 min read

    Mobile testing in 2026: Appium, Detox, or Maestro?

    Mobile test automation is the last frontier where 'just pick the obvious tool' doesn't apply. Three credible options in 2026 — each making a different bet. Here's the comparison.

    mobile-testingappiumdetoxmaestro
  7. Deep dives·13 June 2026 · 9 min read

    Testing app updates without breaking existing users

    QA fresh-installs; real users upgrade in place over old data. Test the upgrade path — schema migrations, stored settings, sessions, multi-version jumps.

    mobile-testingapp-updatesmigrationregression

// RELATED QA.CODES RESOURCES

Tool

Common Bug

Next seriesAccessibility for QA