Earlier quoted context omitted.
Good point. Still, any AOSP fork needs to track Google's version only if they want to run applications built for Google's version of Android. The first iteration of Firefox's mobile OS didn't run any Android apps so it would be no loss if their fork of AOSP also didn't run Android apps. That's why I would suggest renaming so that people don't think they can install Android apps.
The question then is... why would you build on Android? It's not exactly the zippiest platform around these days. The primary pain point for alternative platforms like Windows Phone or any other "third OS" is the lack of apps. Which is the case for keeping compatibility. If you're going to drop it, why not at least focus on a more performant core to your platform? Also, currently Android has been ruled as copyright i…
It's zippy enough, especially when you look at all the different platforms it works on. It's pretty far behind iOS, but then iOS has only a few platforms to worry about. Android is probably good enough especially when you factor in power consumption.
In the end though, it's all about trade-offs. Going with an Android fork gives you a pretty solid base to build off of. It's a nice option for app developers because the tools for Android development are excellent and the OS is well understood.