I expect unification isn't the main driver. Rather it is to have a closed source system. They bought Android already open source licensed, but have been moving towards having everything important into one closed app, Google Services. Fuscia will allow the final control step.
Don't get the premise of this article at all. Attempts to meld mobile and desktop OSes (Windows 10) have been disastrous. No need for desktop and mobile to run same code base.http://www.wired.co.uk/article/google-fuchsia-chrome-os-android-demo …
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Relying on the same code base doesn’t have to mean unifying other aspects of the system, though, does it? If it means developers can more easily put out versions of an app for a family of devices – macOS and iOS, say – ideas like Fuchsia and Marzipan make quite a lot of sense.
-
Say I buy a Mac and apps I need, then later buy an iPhone or iPad for mobile use. It’d be great to know that I’m more likely (in a few years) to get the same apps there if devs’ lives have been made easier by not having to double up (roughly speaking) on learning frameworks/APIs.
-
Perhaps. And things are improving, but IMHO apps that are coded for both mobile and desktop are worse than those that are coded for specific platform.
-
That’s very broad. Are you able to go into pros and cons of either approach when it comes to architecture/maintenance? There’s a lot of stuff out there, purely in the context of Apple, on how having to deal with two different frameworks (AppKit and UIKit) is uncomfortable.
-
Many of the apps I use on both macOS and iOS are great on both, but there’s a lot of expense of the developer building three versions across iPhone, iPad and Mac, and for the really good apps it’s expensive buying versions for multiple devices, too.
-
Lightroom Classic on desktop infinitely better than Lightroom CC coded to span mobile/desktop. Normally find limitations of mobile hamper the desktop version.
-
That’s one example. H about others from devs other than Adobe? I gather it takes shortcuts by using Java for much crossplatform code; there are (or were in consecutive versions I’ve used) signs of its development choices through poor integration with small aspects of macOS.
-
For every hampered app like that, I can point out some pretty impressive mobile adaptations. Starting with
@OmniGroup’s iPad versions of apps that it has made for many years on the Mac. - 3 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.