Fuchsia Is Not An Experiment, Its coming IN 2020!

Some self-important asshats at some startups are claiming that java on Android is not going bye-bye and that Fuchsia is an experiment, ie taking the Google VP literally by his IO comments.

I am going to show via simple Engineering logic why that is not the case and show that Fuchsia is coming in 2020.

Point One: Oracle vs Google Java APIs are copyrightable decision is not really going away. Sure you cn hope it might go away on appeal. But, even Google knows that javs is going bybe bye as its one of the reasons why Fuchsia was started in the first place as its the only mobile OS once the virtualization of legacy Android via a container is deleted via systems update as viable for complaining with the Oracle vs Google decision.

Point Two: java on Android performance ceiling of UI rendering speeds. Last improvement in UI rendering speed was 2014 from 35 FPS to 60 FPS for java apps and its now 2019 and iOS apps have 90 FPS in speed of UI rendering.

And its a ceiling folks, the Android team did an exceptional job of squeezing out all the improved performance in using a java VM based on registers rather than stack. But, the bottleneck is also from the lower OS layer in the form of a Macro kernel-OS and IO implementation.

Point Three: The Google VP comments refer not to the OS itself! Its the different builds for different hardware device forms such as Chromebook and TV, phone and iOT. There are two device form UIs in the Fuchsia current form. So the experiment is having a build for each form factor grouping.

That differs from legacy Android where are device form facgtor groupings had the exact same build with the same large global UI form factor.

Point Four: The biggest app to be ported to Fuchsia before its actual real product releae to OEMs was just recently finished. Yes, you guessed it the Chrome browser.

Point Five: Their are already other non mobile OEMs that are beyond prototype stages with Fuchsia products and testing the RC releases. Jetway, for one. Folks its real as it gets before the final release to OEMS!

Point Six: In the Oracle-vs-Google java APIs are copyrightable in which the US Supreme court will not hear to reverse the Federal Appeals ruling against Google if the appeals ends tomorrow which of these things are infringing; legacy java-Android SDK, legacy java Android OS, Emulator legacy system OS images, and or the java Android apps in Google Play Store?

Before you answer, remember that Oracle, Google, the Courts, and Android OEMs already know the answer AND are in fact acting upon that answer. Give up? Out of that list only the java Android apps do not infringing as they do not include the java.* package structures. Not the openJDK code class files as those are open source, I refer to the structure of packages as evidence by the subfolders.

That means since Google would than have non functioning stuff in form of legacy Android OS, legacy Android SDK, and legacy system OS images for the emulator that in fact java app dev stops on the Android OS platform. Ouch!

Also, note that the legacy Android OS in fuchsia is a separate virtualized container that in fact acts as INDEPENDENT driver. What does that mean? That means that the Fuchsia OS system image updates independently from that driver or in short words if the Fuchsia-legacy Android OS VM combo is on the user device BEFORE appeals run out than Google can still comply with the court decision and update the Fuchsia OS because it will not include the legacy Android java VM container AND thus the device user will still get to use their java apps for as long as its required until the firm that produced them updates to Flutter.

What’s Left?

1. OEMs finishing their porting their apps to Flutter and the SOC device drivers.

2. Whatever other apps Google wants to port to Flutter to showcase the Fuchsia OS.

My estimation is that Fuchsia devices will be out before December 2020 given that the legacy Android-java-VM combination has Android PIE system classes.

How does this affect Flutter?

Just imagine not just 2.5 billion devices overr 4 years flipping to Fuchsia and Flutter apps; but also Facebook being forced to use Flutter to port their apps to Fuchsia and iOS.

SIDE NOTE About Cross Platform: iOS-native, Android-legacy-java, and Fuchsia Flutter do not match in form of app model view-controller models as legacy android uses activity as a controller so does apple(AND, the apple and android-legacy models do not match either as android uses a context and fragments and Facebook used Apple’s activity definition with React Native which is the main reason why you have to write two UIs with the React Native framework ) while Fuchsia does not. The only way to make things match is via a new app widget framework such as Flutter. The only way forward for startups like facebook is flutter whether facebook likes it or not. Same challenges facebook faces is challenges Twitter faces etc.

Oh the irony of Google being able to list in showcases on the Flutter site the Facebook app!

I am just a former android developer riding the new Flutter cross platform front end wave. I have a somewhat raw flutter stuff repo as I am writing some flutter dev books and that is at:

flutterpatterns url

I can be followed ay:

Angel List



My small portfolio site is at:


Flutter Cross Platform Mobile App Design https://keybase.io/fredgrott