3 ms·
I think a hard fork of Android might have been a better approach. The AOSP has a lot of good, it's just controlled by Google and is more of a source dumping gr
by cptskippy 8y ago
I think a hard fork of Android might have been a better approach. The AOSP has a lot of good, it's just controlled by Google and is more of a source dumping ground and less of an open source project.
They might have even been able to work with Amazon, who has a vested interest in Android a la FireOS, and possibly forced Google to make AOSP a truly open project.
- ocdtrekkie 8y agoI don't think Android is a good starting point for an operating system. And the big elephant in the room doesn't go away. If most Androids are Google Androids, and developers don't want to write their app three times, they're going to write it for iOS and Google Android, and not actually-open-Android. So either you aggressively do not maintain compatibility, to which developers still develop for Google's platform instead of yours, or you're stuck trying to maintain compatibility so devs release apps on your platform, which means you're still beholden to do whatever Google wants. You might as well start clean with an OS designed for the modern era, Android's over a decade old now, and it shows. You're stuck with the app gap either way.
- ReverseCold 8y agoAnd it's getting better too, port Flutter and React """Native""" to your platform and there will already be developers who can make apps.