The Pixel C inscription has had a tough life. Under a formula name of “Ryu,” a Pixel C started life in a Chrome OS open source repository, clearly indicating that during one prove it was meant to run Chrome OS. Google was experimenting with a touchscreen interface for Chrome OS to a prove that an on-screen keyboard (which is mostly invalid on a laptop) shipped in a fast version. A finished chronicle of an “all-touch” Chrome OS never materialized, though, and we finished adult with a Pixel C using unchanging Android 6.0 Marshmallow.
The outcome was a “productivity” device that couldn’t multitask. You could form like a champ with a Pixel C’s keyboard, yet a one-app-at-a-time inlet of Android done things like referencing information while typing flattering many impossible. The Pixel C was all a some-more unsatisfactory since we knew a separate shade mode was coming—a “highly experimental” chronicle of a underline debuted in Marshmallow’s developer preview.
Split shade wasn’t prepared for a Pixel C’s launch, though, that usually fueled a feeling that a C was a half-baked device with program that wasn’t prepared for a hardware it was using on. There were other bad signs, too—the inscription had a whopping 4 microphones on top, that seemed to prove it was built for some kind of torpedo voice approval system, yet it didn’t even support always-on Google voice commands during launch.
In a Reddit AMA hosted shortly after a launch of a Pixel C, a growth team’s response to questions was something along a lines of “just wait until Android N!” With a consumer chronicle of Android N—Android 7.0 Nougat—finally out, let’s take another demeanour during a Pixel C. A full 8 months after a release, can Nougat save a Pixel C? What’s a standing of Android tablets now that separate shade has arrived? Is Android unequivocally prepared for a device with a hardware keyboard?
We’re still not certain about hardware issues
This is my third Pixel C. The initial inscription had large tie problems between a keyboard and tablet, and shortly after a review, we perceived a deputy section that achieved many better. After a few months of ownership, section #2 started incidentally rebooting after a confidence update. Some long threads in a central Google forums get into this, so cave wasn’t an removed case.
Numerous OTAs arrived and even a N developer preview, yet a pointless reboot problem never went away. It was after detected that a usually approach to repair a pointless reboot problem is to have a hardware replaced. we abandoned this and manually updated a Pixel C to a final chronicle of Android 7.0 Nougat, and it soon died, refusing to foot past a liberation screen.
Time for deputy #3! So far, things have been fine.
Do Android inscription apps still suck? (Spoiler alert: Yes)
The determined knowledge is that a app conditions on Android inscription is awful, yet we hatred repeating a determined knowledge year after year though during slightest checking in on things once in a while. So let’s investigate.
In a year 2016, do Android inscription apps still suck? To answer this, we commissioned a tip 200 apps on a Pixel C and gave them all a discerning exam drive. we looked during apps only—not games—using this “Top Apps only” Play Store list. The thought is that games scale usually excellent on tablets; it’s apps that are a challenge.
Of a tip 200 apps:
- Nineteen were not concordant with a Pixel C
- Sixty-nine did not support landscape during all
- Eighty-four were stretched-out phone apps
- Twenty-eight were, by my judgment, tangible “tablet” apps
That there aren’t many inscription apps isn’t a warn to many people. What was a startle was a miss of landscape support in so many apps. More than 33 percent of a tip 200 were all landscape, all a time, and many some-more (even some Google apps) had interstitials and other singular screens that didn’t support landscape.
Android apps are essentially used on phones, that are essentially used in mural mode. The Pixel C essentially lives in landscape mode, though—the cameras, earthy buttons, microphones, and speakers are oriented with a expectancy of landscape, and a device contingency be in landscape in sequence to use a earthy keyboard. When compared to a phone market, this is a really singular pattern that creates a problem in apps that many people won’t notice.
Most of a “phone” apps tumble into 3 categories on a tablet: there’s a dreaded stretched-out app, that creates no blueprint considerations for a tablet. Then there are a “Card” apps that hope to scale good on tablets by adhering all into a label container, that afterwards usually gets slotted into a grid that fits your screen. There’s also a “pillar box” app, that puts large margins on a left and right side of a phone app, relieving a bit of a “stretched out phone app” problems. But nothing of these apps is more powerful on a inscription a approach a multi-pane, tablet-native app is.
One of a best inscription app makers in a tip 200 is Microsoft. Seeing because is easy. Google’s pattern methodology is to perspective tablets as large phones, yet Microsoft views them as little desktop computers. As a result, we get torpedo versions of Word, Excel, Outlook, and Skype, with information-dense, multi-pane layouts.