I own a Pinephone with the latest revision board which was bought in the July 31st batch this year (and got shipped in September/November within the EU).<p>I have to say that hardware-wise, the Pinephone got very _very_ far already. It's an amazing hacker's device, especially with the USB-C host.<p>The only issue that persists is software. Phosh is pretty much useless because not a single app will work as a real mobile app, let alone act in a responsive manner with their underlying design philosophies. It all feels like Android 1.x, which was barely useable outside the context of shitty car navigation handhelds.<p>The available cross-compiled versions of Browsers (e.g. Firefox or Chromium) are totally broken, as they are made for Desktop and do not even downscale their user interface, and are neither responsive anyhow. So for now, I am using my own (prototypical) Browser Stealth [1] due to lack for alternatives because there at least the UI doesn't crash every few seconds when being used within a WebKit2GTK webview.<p>I don't have many requirements for my phone, to be honest. I don't use social apps, and only communicate via telegram. But currently the amount of software that's available for phosh is still the one reminding me of a developer environment or say, an Android emulator image.<p>I seriously thought about taking ownership in creating a few apps for it, like one for openstreetmaps, notes, text editor, which are the more important ones for me.<p>But to be bluntly honest, I don't even know where to start with the whole GTK shitshow. It's absolutely impossible to develop an app without any working examples. There's no non-auto-transpiled-bindings-documentation, there's no libhandy examples that actually work, and there's certainly not any responsive GTK app examples that would show how to make a "real mobile" app. How do people develop apps for mobile GTK?<p>Seriously, I cannot understand it. I want to, but there's no way anyone can keep the mood up digging through a _mobile phone's gdb output while the on screen keyboard crashed_ to figure out how the API works.<p>I think what GTK really needs is something like Electron, but maybe based on WebKit2GTK and (maybe?) gjs. Something that allows bundling your assets to build an app that is offline-ready, and is easy to build with common methodologies of UI frameworks.<p>Because currently I don't see the reason why libhandy exists. It tries to fix a problem, and doesn't fix the underlying cause. GTK boxes and their layouting (and reflow?) concept just isn't made for an adaptive/responsive UI, so you'll always end up with a totally broken UX by modern standards. (You're welcome to challenge me on this, but as long as "make a sidebar that can fade-in/fade-out with a swipe" takes more than a week to build, I think you're wrong.)<p>[1] <a href="https://github.com/tholian-network/stealth" rel="nofollow">https://github.com/tholian-network/stealth</a>