This site may earn chapter commissions from the links on this page. Terms of employ.

Google has taken Android from a small startup to the largest mobile computing platform in the world. You can't exercise that solely on luck, but that doesn't mean Google hasn't fabricated some mistakes. Some have pointed to one issue or some other every bit show of Android's inadequacy. Still, things have worked out, even with a few big errors on Google's part. And so, allow's talk about all those times Google facepalmed with Android, and what information technology did to fix it.

Google Now on Tap

Google announced a new element to search on Android called On Tap in the lead upward to Android 6.0 Marshmallow. The idea was that you'd long printing the abode push while using the telephone, and On Tap would be able to offer information most what was on the screen, as well every bit offer contextual search results. It was a nice idea, but On Tap ended up being a mess.

nowtap2.0

The primary issue with On Tap was that you could never tell if the feature would actually do anything useful until you opened it. Too often it would simply say there was nothing useful on the screen. After a few attempts, nearly users wouldn't bother with On Tap once more. Google began throwing everything at On Tap to run across what stuck; at that place were screenshots, map search shortcuts, and news items. None of this helped, and Google Now on Tap was quietly retired early this year.

Google launched the Pixel with Assistant, which took over the long-press functionality of the home button. Several months subsequently, Assistant came to all Android phones running Marshmallow or higher, supplanting Now on Tap. It's a smarter employ of Google'south car learning power than On Tap, and it plugs into a ton of third-political party services.

The Nexus Q

The Nexus Q was announced at Google I/O in 2012, and were handed out to attendees before the full general public has a chance to buy ane. This $300 media streamer ran a modified version of Android that connected to the user's Google account to play music, movies, and YouTube videos. However, information technology didn't connect to any non-Google services like Netflix. That effectively doomed the device.

nexus q

This was the first Android device Google developed entirely in-firm, and information technology wasn't actually bad from a hardware standpoint. Information technology was a pocket-sized metal sphere with a 25-watt amp and HDMI output for HD video. Still, the software was so express that Google had to filibuster the July 2012 launch while information technology revamped the production. Google did allow everyone who pre-ordered the device have it for free, but no further features were added. Google killed the Nexus Q in early 2013 without e'er selling a single unit.

This was not Google's last effort at gaining a foothold in the living room, and it seemed to learn from its mistake. In 2013 it unveiled the Chromecast, a $35 device that permit users stream content to their Telly. It wasn't much more capable than the Nexus Q at launch, but it was cheap. The Chromecast has go one of Google'south most successful media products.

Android 3.0 Honeycomb

Android circa 2010 did not back up tablets, and this is when the iPad was selling like hotcakes. Several Android OEMs like Samsung were hacking Android 2.three onto tablets with little success, but Google's beginning stab at making Android tablet-friendly wasn't much better. Android 3.0 Honeycomb was appear in early on 2011 alongside the Motorola Xoom tablet, but it was extremely express.

honeycomb

Honeycomb was clunky, unattractive, and wasn't even open up source. Information technology just ran on tablets, so developers had to operate two dissimilar versions of their apps if they wanted to be on tablets. Honeycomb was as well limited to Tegra 2 ARM chips at get-go, which restricted hardware selection. Information technology was the verbal opposite of what Android had been doing thus far. Google treated this version of Android like a beta test, and that made for an unattractive consumer product.

After slogging on for eight months, Google finally launched Android 4.0, which again unified the phone and tablet versions. It was merely then that Google released Honeycomb's source code. While it was non well-liked, Honeycomb included a few features that would get standard on afterward versions of Android like tabbed browsing and screenshots in the recent apps screen.

The "App Ops" Permission Manager

Android 4.3 Jelly Edible bean was a small update to the Os later two previous Jelly Bean builds. In fact, its nearly notable feature wasn't even supposed to be included—an advanced permissions manager. See, Google accidentally left a bill of fare called App Ops attainable in the Os. So, Google blocked access to App Ops in an update sparking a moving ridge of bad press.

Android-4-3-Permissions

App Ops gave users access to manual permission control for apps, which sounded great. Still, apps at the time did not support that natively. Thus, deactivating permissions could cause crashes and other unexpected behavior. This should not have been accessible, but it was. All you had to do was find and launch the activeness for the subconscious bill of fare with any number of apps in the Play Store.

Naturally, Google ripped App Ops out in a future Os update, and people were upset. Privacy advocates lambasted Google for removing the option, declining to understand this was a developer characteristic that was non ready for prime time. Google took its licks, though, and got to work on offer a existent permissions manager. When Android 6.0 Marshmallow rolled out, it had proper support for turning app permissions on and off.

Android Wear 2.0

Smartwatches have nevertheless to accept off similar many in the industry had hoped. Even Apple'southward sales haven't lived up to expectations, as evidenced past its quiet refusal to offering sales numbers for its Watch. Android Wear was due for a large update last year, only information technology took longer than expected. Google was supposed to launch Android Habiliment in the fall of 2016, just the programmer preview release got extremely negative feedback. So, Google reworked information technology. Unfortunately, it'south even so non very good.

wear2.0

Even when the update rolled out months late, users haven't been overly pleased. Android Habiliment 2.0 makes a number of bizarre changes like unbundling notifications and disconnecting do-not-disturb mode on the watch from practise-not-disturb on the phone.

Google needed to brand the case for smartwatches with Vesture 2.0, and it really didn't. We don't know withal how (or if) Google will make this one right. In that location should be a new version of Wear based on Android 8.0 later this year. Well, unless it'due south delayed too.

At present read: 25 Best Android Tips to Brand Your Telephone More than Useful