Linux phones are more important now than ever

I had a Neo Freerunner.

It was a terrible experience. I bought it with the impression that it had calls, texts etc working fine, and they were looking for developers to come along and add apps, games, whatever to round out the experience.

I couldn't have been more wrong. They had about four different distros. There was the 'old' one, the 'new' one which was already scheduled for deprecation because of the new-new one in the pipeline and there was also a debian distro. Each one used an entirely different UI framework (gtk/efl/qt), and the developers seemed focused on these endless interface rewrites when the unit couldn't reliably receive a call or a text under any of them.

After that I had a Nokia N900, which was a great experience. They'd nailed down the basics perfectly (as you'd expect from a much larger company) and the unit was a capable smartphone with linux under the hood and easily accessible. It's just a shame the app ecosystem never took off, and nokia flushed itself down the toilet shortly thereafter. I guess Sailfish is the successor in this space, though I liked that Maemo was debian-ish rather than rpm-ish :)

I guess what I'm saying is that a linux phone doesn't have to be raw, but for god's sake make it able to take calls and send a few messages...

> What government apps do people run?

Public transport ticket app, government ID app, drivers licence app.

I do believe all of these specific examples run fine on rooted Android without too much hassle (unsure about the second one), so they should be emulatable or whatever on a Linux phone, but that assumes that experience holds up decently well, which I would be surprised if it did for apps like this.

> Why do you need to access your bank account on your phone?

Because the app is a whole lot better than the web interfaces my previous banks had. Plus the added convenience. I'd prefer that the web interface was just as good as the app, but I'd still use the app even if that existed, just due to the convenience.

They're rarely completely mandatory (Grandma still needs to be able to access her bank too), but the alternative is usually a whole lot more inconvenient (sometimes for bad reasons, sometimes just because that's how life is).

Total agreement with the article's conclusions. I'm an Android developer who once had about six apps listed in the Play Store. But as time passed, maintenance became more and more baroque, and a simple Android version change required me to rewrite all my apps or lose my listings. Like many developers, I gave up.

Then Google announced a decision to disallow sideloading (not clear when this will take effect) and many tablet/cellphone manufacturers intend to disallow bootloader unlocking. If all this happens, it basically closes the Android platform to anything but "official" software releases.

Consider this from my perspective. My first computer was an Apple II in the late 1970s. I could do anything I wanted with it, and I did. But over the decades I've watched the world of software development -- with the exception of personally owned Linux machines -- gradually turn into a walled garden.

What can I say -- it sucks the joy out of programming.

Working on LineageOS doesn't help you if you can't even install it. Fewer and fewer phones come with unlockable bootloaders these days. The grip is tightening.