COLONEL MANIC // who gets it right
Criteria for inclusion: A confirmed graceful incompatibility handling on an EOL rugged device. The app identified the device as incompatible and declined installation cleanly, with no device impact. Evidence-based.

This page exists to demonstrate that the bar is achievable. Not high — achievable. The apps listed here are not remarkable for their engineering. They are remarkable for the fact that they bothered.

The lesson is in who appears here. When a regulated industry with no particular software expertise routinely does better than a consumer technology company, the problem is not technical. It is cultural.

State Farm Confirmed

State Farm is an insurance company. Their core business is actuarial tables, policy management, and claims processing — not software engineering. Their Android app is a customer-facing tool, not a product in its own right.

And yet: when installed on a CAT S61 running Android 9, their app correctly identified the device as incompatible and declined to install. Cleanly. Without ceremony. The user saw a clear dialog, was offered a direct path to uninstall, and lost nothing but thirty seconds.

What they did right
  • Device compatibility checked before any initialisation
  • Clear, plain-language incompatibility dialog
  • No device state modified prior to the check
  • Direct uninstall path offered in the dialog
  • No network request required to display the message

Why this probably happened

State Farm almost certainly achieved this not through technical brilliance but through compliance culture. Regulated industries that handle financial data are accustomed to QA checklists, audit trails, and not shipping things that break in unpredictable ways.

That conservatism — often mocked as bureaucratic slowness — produced a better outcome on rugged device compatibility than a consumer electronics company whose entire identity is building hardware and software that work together.

State Farm, founded 1922. Still doing the Right Thing.

Additional entries require confirmed evidence of graceful incompatibility handling on a named rugged device. If you have an example, submit it.