[fauigerzigerk]

I think there's a lot more going on than they are publicly letting on.

If the general public starts to believe that there is an Android successor in the works, many people will stop buying Android devices until further notice. This could be absolutely catastrophic for the Android device market.

If I were Google, I would bury the name Fuchsia, call the thing Android 10, and let it be known that it's years out.

[greenhouse_gas]

>If the general public starts to believe that there is an Android successor in the works, many people will stop buying Android devices until further notice.

The bigger danger is the response by android developers. Will you invest in a soon-to-be-deprecated Android Native app written in a soon-to-be-deprecated API (because, at least according to the Internet rumors, Fuchsia will be using Dart instead of Java and will have a totally different API), rather than just write it in Xamarin, Cordova or React Native?

And once your apps aren't written in Android API, how hard is it to port to, say, Windows Phone?

This damages their moat.

[sebe]

>Fuchsia will be using Dart instead of Java

The current sysui is flutter/dart based, Flutter is google's newish mobile app sdk, the guys who started it have work on the chrome team, it's in alpha and has support android and ios.

https://github.com/fuchsia-mirror/sysui "Armadillo is currently the default system UI for Fuchsia. Armadillo is written in Flutter"

Here is an example of a rust programme, Xi editor, using flutter for the ui. https://github.com/fuchsia-mirror/xi

[jayd16]

This is silly. No way they would launch such a thing without ART support. Even ChromeOS is running Android apps now.

[remir]

From what I understand, with Dart/Flutter you can write apps for Fuchsia, iOS and Android with the same codebase. I think this could be interesting for devs. If making Fuchsia apps is easier and more pleasant than making Android apps, developers will respond positively.