iOS and iPadOS are really the same OS under a different marketing label. If you look only at APIs, the overlap even with macOS is very large and getting larger every year.
Chrome OS and Android are much farther apart, both in terms of API (web apps and Android are very different; iOS apps can run unmodified on newer Macs, for example) and OS implementation.
I have a feeling this is less about the design of OSs or APIs and more about how they respond to regulatory pressure to spin off Chrome into a separate business. They may be rebranding parts of the Chrome ecosystem so they aren’t forced to get rid of it.
I would love Google developing an Android desktop enviroment meant to be used as an OS alternative to Windows and MacOS. Probably they can have a native compatibility with Linux software, and maybe bring some good UI, UX. Midrange Phone hardware can handle your average productivity needs.
Desktop Mode in Android 15 looks like a move into a desktop set up.
And since OpenMoko, never really made a dent in the market, continuous reboots of the same idea, without grasping why normies don't get them, as means to a sustainable business.
You can't just create a well-polished, iPhone-like device with a company of 100000 times smaller size than Apple. You inevitably start with a niche audience.
Sounds more to me like Google taking convergence seriously which is a clever way to attack Apple in the tablet market since Google has no real laptop line to actually cannibalise.
With side loading, nothing really prevents you from doing development on Android apart from the poor UX. Technically, I’m fairly sure Google could probably easily give you access to a full sandboxed Linux environment if they think it’s a good idea.
I wonder how this will affect the EDU market here in the US. ChromeBooks are heavily used in K-12 education and are nearly ubiquitous. If they keep the same manageability as is currently available for Chromebooks, it should be fine. IF not, it could be big trouble for schools.
23 comments
[ 2.9 ms ] story [ 64.6 ms ] thread1) iOS for phones 2) iPadOS for tablets 3) MacOS for computers
Google attempt to use one OS (Android) for both phones and tablets will result an unwieldy API for developers and confusing experience for users.
Rather than trying to build 'one size fits' solution they should aim for 'right tool for the job' strategy
Chrome OS and Android are much farther apart, both in terms of API (web apps and Android are very different; iOS apps can run unmodified on newer Macs, for example) and OS implementation.
And it no longer runs like the original chrome os did way before (simple and lightweight). It needs to be in the $600 price category to be decent.
Desktop Mode in Android 15 looks like a move into a desktop set up.
With side loading, nothing really prevents you from doing development on Android apart from the poor UX. Technically, I’m fairly sure Google could probably easily give you access to a full sandboxed Linux environment if they think it’s a good idea.
In a nutshell schools benefit from a a simple, restrictive, laptop device that runs the web well.