4 ms·
> after all, porting your apps from standard Android to an AOSP fork is easier than than porting it to Windows Phone So is this REALLY Android if you need to p
by Mister_Snuggles 13y ago
> after all, porting your apps from standard Android to an AOSP fork is easier than than porting it to Windows Phone
So is this REALLY Android if you need to port your applications to run on it? How much of what makes an Android phone Android is AOSP and how much is the Google services that sit on top of it?
- mdwrigh2 13y agoThis isn't necessarily Google services vs. AOSP. Since they aren't going through certification there's no guarantee they've gone through CTS tests (so they APIs may differ from stock Android, either in signature or functionality).
- Mister_Snuggles 13y agoSo it sounds like we have two Androids on the market now: Certified Android and not-quite-Android-but-still-mostly-Android.
- mdwrigh2 13y agoNo, there's one Android: the one certified by CTS and conforming to the CDD. You aren't allowed to use the name Android to describe your device without being certified as "Android-compatible". From the FAQ on source.android.com: "Is compatibility mandatory? No. The Android Compatibility Program is optional. Since the Android source code is open, anyone can use it to build any kind of device. However, if manufacturers wish to use the Android name with their products, or want access to Google Play, they must first demonstrate their devices are compatible."