Microsoft couldn't do it because everyone new (of the users) that even if they put in their effort to switch and wait for the ecosystem to grow, they will end up with just the same crap: another closed-source monopoly with it's own quirks. We won't have just two overlords, but instead 3 of the same. Wow such a difference...
Now an truly open system might make a difference. Not saying it will, it has it's own problems, but comparing it to Windows Phone is not really apples to apples.
The third party app platform was pretty slow and missing a lot of APIs relative to the others. The first party UI, which got praise from reviewers for being smooth, was written in a different language and framework.
In the first version, the default blank app from Visual Studio's "new project" wizard was slow to load. I think I measured it on the order of 500ms at the time. Not much room for third parties to add more stuff without being slow.
The only question I'd ask is : how many phones should they sell to break even ? Cos if they actually make some profit, that's just fine. Maybe they don't aim to go to mass market. And that's why MSFT may have failed : they tried to fight on Google's ground, head to head. Of course Pine can't do that. So if they just repeat what's been done for Raspberry, that's just great enough to have a living ecosystem.
I personaly just need SMS, voice and a browser. The rest, I can live without it (or program it :-)
You greatly overestimate the number of users who care about how closed or how open an ecosystem is.
If the user can't interact with their bank, whatchu YouTube, talk to their friends and parents over Snapchat or Skype, call Uber, play Spotify, etc etc etc, it doesn't matter in the least if your phone is 100% open source.
Microsoft had sunk billions into trying to get the ecosystem off the ground. What makes you think that "a truly open system" will get that ecosystem?
> If the user can't interact with their bank, whatchu YouTube, talk to their friends and parents over Snapchat or Skype, call Uber, play Spotify, etc etc etc, it doesn't matter in the least if your phone is 100% open source.
Most of this should be available on the PinePhone at launch (albeit not as nicely as on Android).
Bank - should have a website (and if they don't have a website they most likely don't have an app anyway)
YouTube - website again (youtube.com)
Skype - has a web app and a Electron app available for Linux (web.skype.com)
Uber - has a PWA that can be used for booking rides (m.uber.com)
Spotify - has a web app and a Electron app available for Linux (open.spotify.com)
My bank app has significantly better usability than the website because it can mostly cache credentials and support a short login procedure. Or use the fingerprint scanner.
Not really, among "normal" banks. This does seem to be the case with the new "challenger" banks like Monzo and Starling, which are all "mobile first" and are basically impossible to use if you don't have an Android/iPhone. But every regular bank in the UK has a website with online banking, often with more functionality than the apps, but maybe this is different in other countries - online banking in the UK has been commonplace since before mobile apps were really a thing.
Funnily enough, my last bank and two current ones, the app is increasingly a front for a mobile web version. With each new update I see more functionality moving to web.
I have an account with Bank of America and was not aware of this so thanks. That said, you can do pretty much everything else via the website. The opposite is also probably true, that there are some features on the website not available on the app (for example can you open a new CD in the app?).
The target audience isn't people who need to use Skype, Snapchat, or Uber. But I'm sure it will be possible to run some of those android apps through anbox. Spotify has a Linux client, and for YouTube there's the FreeTube client, which actually protects users' integrity.
I love them, thanks to it I have refocused on mobile Web, even though I tend to prefer native apps.
For traditional CRUD apps, PWAs are quite alright, and one avoids having to deal with Android's always changing "best practices", with a stagnant Android Java.
Now an truly open system might make a difference. Not saying it will, it has it's own problems, but comparing it to Windows Phone is not really apples to apples.