Android on the desktop: Not really “good,” but better than you’d think
arstechnica.com
arstechnica.com
[1] http://www.amazon.co.uk/Mele-A1000g-Quad-Android-Black/dp/B0...
For the most part though, I found it reasonably decent for just a "monkeying around on the internet" desktop, but when I needed to actually do work, it quickly became useless. Google Docs on Android is a fucking travesty of a thing, and MS Office was not yet available at the time.
A grand vision held back by the hardware.
I have never tried to use Android as a 'laptop OS' (even though the Pixel C is so very tempting) but from what I can gather, the interface has been rethought profoundly for 4.0 and focused on the mobile use case.
According to the rumors, Google is supposed to deliver a more polyvalent version of the OS (and more importantly of its own apps)... Let's see what happens (or not) at Google I/O.
So I bought an ultra-cheap Windows 7" tablet. While it's much better from an application point of view (you can run Word on it, Visual Studio, and so on) it's really hard to use the traditional desktop without a mouse - everything is too small to be a touch target.
Then Google decided to merge the two, and since then it's been back to the "tablet is giant phone" interface.
Ars Technica has done several articles on Google's failure to follow its own design examples when reviewing tablets: http://arstechnica.com/gadgets/2014/11/the-nexus-10-lollipop...
Why can't Android run the full Chrome browser? Why can't Android's Chrome run Google Docs and Sheets? https://news.ycombinator.com/item?id=10716287
1. The Android kernel is essentially a fork of the Linux kernel with a bunch of non-upstream features and non-upstreamable crapware drivers written by the phone/tablet vendors. By and large mainstream Linux distros are only happy to ship upstream kernels. This means you'd need to run a hybrid distro userspace + Android kernel, which sucks because of missing kernel features, lack of integration with distro packaging, and lack of security updates for the kernel (unless you apply them by hand each time yourself).
2. Mainstream Linux desktops suck without a mouse and don't have any multitouch features -- despite groups like GNOME fetishizing iOS, they haven't "got" what makes it good nor provided a competent replacement. Also the form-factor of a phone or tablet is quite different from a laptop or desktop and so requires somewhat special GUI software - single app at a time, on screen keyboard, larger text, page-sized forms without decorations and so on.
Anyway, you can look at Ubuntu Phone as a good place to start.
It just works, so people don't talk about it anymore.
I'd really just like my dash screen to show the contents of my phone... or better yet ... have the phone adapt to the dimensions of the screen, and change the layout/interaction style, etc.
Well, I will wait for Google to merge/combine ChromeOS and Android somehow to offer the best of both worlds then. An Android smartphone/tablets that offers ChromeOS capabilities (or an mouse+keyboard centric) window manager when connected to a monitor/projector would be awesome. I think this will be the future.
The OS itself shouldn't really matter as long as it can stay out of the way in the background, one thing Android does offer is a large ecosystem of apps.
Users of other operating systems are often not doing much more in their daily activities, and recent OS updates tend to support that more and more (OS X's notifications, Windows start screen and metro apps etc.)
Apart from that, what does centering on messaging/browsing take away from e.g. word processing or other office uses? Or how is multiplexing browser views inherently different from multiplexing terminal windows?
I'm not saying that I'm particularly fond of the way Android does things, but I don't think its focus is to blame for that.