4 ms·

I don’t think you understand what it takes to support “unsupported devices”. I already explained that it does take effort, so without that screen you’d have a b

• ryandrake 2y ago
  It takes zero effort to keep an existing app running that's already installed on a user's old phone. You simply do nothing! Don't issue updates or go out of your way to remotely disable users, and instead focus on shiny new phones. If the app hits a server API, you just make sure that API version doesn't get touched (you are versioning your APIs right?). It's not rocket science. Sorry, everyone has one HN soapbox, and you happen to have run into mine. Software developers need to stop being so hostile to users with devices they deem "old and icky". This includes OS vendors, too by the way, I'm not leaving them out. Supporting only N-1 is a user-hostile policy, and it's driven primarily out of developer laziness rather than business need. Remotely disabling any version is absolutely appalling, and I hope that practice doesn't catch on.
  • sureIy 2y ago
    > I hope that practice doesn't catch on. I got news for you, they invented something called websites and all they do is remotely disable what appears in your browser. Next thing you know, they place them in webviews and show "Your browser is not supported because it's running on a 8-year-old device." I don't know how else to tell you that they did not break something that works, but simply stopped serving an old web view because supporting it DOES NOT come for free. Do you still ship IE6 views for the lone monthly viewer too?