In the last few days, some of you have noticed that Android is gaining some of the same kinds of features and concepts we’ve discovered are coming in Fuchsia. Let’s take a few minutes to dig into each of them and what they mean as a whole for the two OSes.
With all the developer excitement following Google I/O this week, we’re keeping in theme with a developer-oriented Fuchsia Friday.
Earlier this month, Fuchsia gained its first official screenshot tool! No more looking ridiculous by taking a photo of a screen. With this change, I figure now is the perfect time to give a closer look at some first impressions of Fuchsia’s user experience.
This week on Fuchsia Friday, we look at one of the most requested features of Fuchsia and how it might be possible.
This week on Fuchsia Friday, we take count of Fuchsia’s development team and highlight some of its members. The backgrounds of Fuchsia’s contributors are widely varied, including those from RedHat, FreeBSD, Danger, BeOS, iOS and more. Let’s take a look at some of these, and have fun speculating what it might mean for the behind-the-scenes OS that is Fuchsia…
Fuchsia Friday is back with your fix of Fuchsia information. This week, we’re looking at how Fuchsia handles graphics differently and what that might mean for gaming and VR.
This week on Fuchsia Friday, we get to take a look at our most requested topic: Maxwell, the smarts behind Fuchsia.
When describing the organization of Fuchsia code, Google uses a “layer cake” metaphor. Fuchsia is the name of the project as a whole and of the finished product (we presume), but under the hood there are 4 distinct layers that it’s divided into. This week’s Fuchsia Friday details each layer and what we know about them.
If something isn’t growing, it’s dying. With the slew of neglected devices not receiving Android Oreo, it could be argued that the update system is one of Android’s fatal flaws. Fuchsia is trying to be different. This week in Fuchsia Friday we look at Fuchsia’s ambitious update system.
Earlier this week, Google’s new cross-platform mobile app framework Flutter hit Beta. To celebrate that, let’s take a closer look at what Flutter is doing for app development today, and how it’s preparing developers and users alike for Fuchsia.
This week in Fuchsia Friday we look at the bigger picture. Google is making Fuchsia fundamentally different from systems of the past, especially learning from the challenges the company has encountered with Android. But now that we’ve taken a few weeks to describe some of its more important elements in detail, let’s take a step back and look at the big picture. Let’s check out the building blocks and terminology that Google uses to describe Fuchsia’s “modular” design.
With Fuchsia, Google’s upcoming OS for phones and computers, comes a chance to revamp and rebuild existing Android experiences and build them deeper into the operating system. In this week’s Fuchsia Friday, we’re looking closer at how Fuchsia has replaced the app drawer, and what seems to be an exciting reimagining of Instant Apps-like functionality.
Two weeks ago, we learned about Fuchsia’s Stories and Modules, and how they will help us better organize our time, tasks, and ideas. This week, we’re looking at the idea of ‘entities’, Fuchsia’s attempt to catalog the digital world to be read by Assistant. Entities are also part of the glue that holds disparate “modules” together into one coherent Story.
Last Friday, we took a look at how ‘modules’ in Google’s forthcoming Fuchsia OS come together to make ‘stories’. As we learned last week, a story is one or more apps working together to help you complete a single task. Fuchsia, for the uninitiated, is also designed to allow for quick switching between devices by saving your Stories to your personal ledger.
This week, we’re learning more about Ledger and how it helps Fuchsia tell your story.