As we've seen through previous software clues, the OS would represent Google's chance to start from scratch and eliminate the baggage that comes with existing software. Both Android and Chrome OS are based on Linux, for example, which carries technology that Google might no longer need. Android in particular still has some elements of Java (currently through OpenJDK) that Google might want to jettison in light of its ongoing legal battles with Oracle. Fuchsia is also expected to scale more consistently across device types, include better hooks for voice commands and provide faster security updates than on Android.

It's far from certain that Google would make that timetable. It's a daunting feat to ask Samsung and other hardware brands to throw out legacy app compatibility, rewrite custom software and otherwise pour massive amounts of time and money into supporting an untested platform. Just ask Microsoft how well things went when Windows Phone 7 rendered existing Windows Mobile know-how obsolete. Google would have to both ensure a rich catalog of Fuchsia-native apps and convince manufacturers that the OS is worth using on mainstream devices that would attract wide audiences. It wouldn't be shocking if Fuchsia took much longer than five years to completely supplant Android, if just because the existing platform is so deeply entrenched.

Update, 2:15PM ET: Google has told CNET that there isn't a five-year plan for Fuchsia. In a statement the company described the OS as "one of many experimental open-source projects" happening at Google, with no timeline for it to appear in future products. Of course, that doesn't mean it won't appear in five-ish years, but right now there's no roadmap.