Phones are terrible anti-user devices, so I can’t do the things I’d like to do with it that I can’t also accomplish on a website. Wasn’t that kinda the problem that was initially stated in the OP?
Maybe I phrased it poorly. I meant, what things do you do on your phone that wouldn’t be possible on a website if you were on another platform?
Actually, I’ve been actively trying to use Firefox Mobile for everything I reasonably can on my phone, and it’s way more possible than you might think.
I actually think a browser model limits a lot of what you say here,
I think you misunderstand me here. I’m not asking for a browser model to increase the number of things that app developers can do, I want to increase the number of things that end-users can safely do, and running web apps in a browser are currently the easiest way to do that.
and browsers definitely have ecosystem lock-in problems: what Google says essentially goes these days. The browser isn’t the great liberator of phones imo.
That’s absolutely a huge problem, yes; but it’s a different one. And in the faintest praise possible, Google does at least maintain fairly solid web standards.
I do however think it’s a weird way to try to fix the phone ecosystem by replacing a restrictive sandbox with a restrictive sandbox that also ties you to a really terrible development ecosystem.
It would be a replacing a sandbox that’s restrictive for the user and developer with one that’s only restrictive for the developer. And I don’t think it’s a particularly terrible development ecosystem; in a lot of ways, the front-end dev ecosystem is the most mature ecosystem. We’re absolutely spoiled for choice in IDEs, in linting tools, in packages…I mean, I used to work in email development years ago. THAT is a terrible development ecosystem, let me tell you.
I think I’d rather my phone be a little “dumber” than my laptop or desktop, though. Or I want it to be powerful enough to be the brains of both, but that would make it expensive enough that I would worry about losing it. Making it just a browser gives it enough utility to be broadly useful, but also enough friction that I won’t get sucked into it.
Also, I think a low-cost, low-power, mass-market B2G-type phone (a la the Chromebook) is way more likely than a mass-market Linux phone. Maybe that’s just me being cynical, though.
As for Google, yeah. I agree that they don’t have the users’ best interest in mind. But there’s currently enough of a pull from mobile Safari that they’re willing to play by the rules for now. My understanding is that the Web Attestation API was basically dead in the water—though maybe that’s me being too optimistic, ha.
Same to you! Good conversation. I appreciate it.