3 ms·
If you want an open source smartphone OS, why not just use Android (AOSP)?
by criddell 11y ago
If you want an open source smartphone OS, why not just use Android (AOSP)?
- rockdoe 11y agoBecause the apps ecosystem is getting more and more locked into Play Services, which are not part of AOSP.
- 5ilv3r 11y agoFdroid apps work well for me. I did not install gapps at all.
- criddell 11y agoAnd how is the app ecosystem on other open source mobile operating systems?
- rockdoe 11y agoThe internet is pretty fine, except for a prevalence of webkit only sites on mobile.
- criddell 11y agoDo you really think so? What are some of the best internet apps? I think a native app will always give a better experience because they can always just contain a browser view (it's basically a superset). Plus native code will always be more efficient and in mobile, that matters.
- rockdoe 11y agoA native app is already lost at the start because it requires the user to install it. Also at least on Android I don't buy the efficiency argument at all, Java and JavaScript are both JITed. You think Java JITs better than asm.js? The integration argument is decent, but it's only really relevant for apps that get a lot of use, not the long tail of stuff that you use once or twice.
- criddell 11y ago> A native app is already lost at the start because it requires the user to install it The billions of installed apps indicates that the friction isn't significant. > I don't buy the efficiency argument at all, Java and JavaScript are both JITed That's how everything worked back in the Gingerbread days. Android's ART system compiles applications to native code when they are installed. You can also install actual native code with Android's NDK. If you like the idea of asm.js, then you should check out Go on Android. It does the same thing - offers a restricted set of the language that runs very fast. There's definitely a subset of apps that work very well in a browser. But you can do more, faster, with lower power consumption with native apps.
- jbiddy 11y agoBecause Google has almost completely stopped pushing things to AOSP and instead keeps all the goodies locked under their proprietary apps. There is no AOSP for their "Okay, Google" stuff for instance. Most Google AOSP functionality is stuck in Android 2.x days.
- criddell 11y agoI don't think that argument makes any sense. The options seem to be write everything from scratch or take AOSP and write only the services. The latter option makes a lot more sense to me.
- ocdtrekkie 11y agoThe biggest problem with forking Android is that all of the apps will be developed for Google's flavor of Android. Which generally means you need to try to remain compatible with it, with ends with "you have to follow Google's development direction". And Google's development direction, of course, is selected by Google's business interests.
- criddell 11y ago> Which generally means you need to try to remain compatible with it, with ends with "you have to follow Google's development direction" You certainly don't need to do any of that. Amazon didn't do that and they have a pretty successful line of tablets. Even their crappy phone was far better than the Firefox OS phone. Firefox could fork AOSP, break compatibility (if they want), rename it, and never look back. If they did this, they would be far ahead of where they are right now with Firefox OS.
- ocdtrekkie 11y agoAmazon DOES have to do that. Each version of their OS is based on a version of Google's version of Android. And they have to follow Google in re-implementing every Google API as an Amazon API as quickly as possible so they don't lose compatibility with apps.