David Ruddock of Android Police thinks the Pixel C is a bad idea. While I think I agree with the basic premise of this article, I am not on board with most of the points being made. #

The writer basically says the Pixel C will fail because Android is not optimized for productivity, but that depends on one's requirements and everyone's is slightly different. For example, I am the type of person who uses desktop Windows applications full screen, or maximized. I think that the Microsoft Office mobile apps work very well on Android and I can be pretty productive with them.#

Further, the writer claims that Android is simply not good for tablets. I don't think Android's UI is any worse on tablets than iOS. While my opinion is that Microsoft's Surface may be the best for productivity on 10.1" and larger tablets, that has more to do with app support and screen orientation than the UI. #

Where I do think Google has a problem that may affect the Pixel C is with Android's performance on the Nvidia processor. If my personal experience with the Nexus 9 is any indication, Android has some real problems with the Nvidia. My Nexus 9 seems to need to be rebooted every day to clear up whatever memory jankyness is going on. Spontaneous freezes, reboots, and general weirdness remain despite Android 5.1.1 that Google claims fixes these problems. #

One of the fundamental differences between tablet and smartphone operating systems and desktop operating systems is reliability. We expect the OS on our smart devices to just run non-stop for days if not weeks with no problems, while we accept having to reboot desktop OSes daily. #

Android's quality seems to be increasingly worse with each new release, and nobody seems to be writing much about the issue. Does Android's UI impede productivity and therefore doom the Pixel C to failure? Perhaps. Does a buggy Android that locks up unexpectedly, slows down or spontaneously reboots doom the Pixel C? Definitely. #