My phone detects going on a run as “someone snatching my phone and running off”
A phone's new "theft detection" feature is aggressively misfiring, mistaking a user's run for a phone snatching and locking the device. This post struck a nerve on Hacker News, sparking widespread frustration with overly "smart" software that makes unhelpful assumptions about user behavior. The discussion highlights a common sentiment: tech often designs for an ideal, rather than a real, user experience.
The Lowdown
A Mastodon user, Fabian Giesen (@rygorous), shared a frustrating experience where a recent phone update began detecting his regular runs as a phone theft incident. This 'smart' feature instantly locks his screen and kicks him out of his running app, despite global device protections being turned off. He expressed exasperation with software trying to 'outsmart' users without offering fine-grained control.
The initial post quickly led to others sharing similar anecdotes about overzealous 'smart' features:
- Laptop Left-Behind Alerts: Phones or watches erroneously alerting users that they've forgotten their laptop, even when it's in hand or nearby.
- Vehicles Brick themselves: An example of hire cars in Canada self-bricking when detecting movement with the engine off, leading to issues like being unable to drive off a ferry.
- Inability to Disable: The core complaint revolved around the lack of clear, functional options to disable or customize these 'protections', forcing users into inconvenient workarounds or considering alternative operating systems like LineageOS or GrapheneOS.
The story resonates as a prime example of well-intentioned software features creating significant real-world friction due to poor implementation and a lack of user understanding.
The Gossip
Smart Features' Follies
Many commenters echoed the sentiment of frustrating 'smart' features that misinterpret user actions or make poor assumptions. Examples ranged from Apple Watches auto-pausing hikes while the user is actively working out to Google Maps suggesting convoluted public transport routes to avoid short walks. The core critique is that developers and product managers often design in a 'bubble,' failing to account for diverse real-world use cases or offering insufficient customization to disable these unhelpful 'protections.'
Phone Theft Realities
The discussion branched into the real-world prevalence of phone snatching, particularly in major cities like London, Mexico City, and Brazil. Commenters shared how common this type of crime is, leading some to argue that such anti-theft features, while annoying, are a response to a genuine problem. Existing and emerging counter-measures were mentioned, including physical lanyards, iPhone's activation lock, app-specific biometric locks, and even government apps to report stolen phones, highlighting the ongoing cat-and-mouse game between thieves and device security.
Navigation's Niggles
A significant tangent revolved around the perceived shortcomings of map and navigation apps, especially Google Maps. Users complained about poor public transport routing that tries to minimize walking to an absurd degree, even when short walks would be more efficient. Other issues included maps suggesting ferry routes with unrealistic wait times, an inability to easily customize preferences (e.g., avoiding specific roads or setting toll thresholds), and the overall lack of flexibility in tailoring routes to individual preferences beyond 'fastest' or 'shortest.'