We've recently seen plenty of rumors related to Google's future plans for its Search app, from automatically remembering where you parked to reminding you of things when you're with another person, to reminding you to pay bills, down to something as simple as setting a proper timer. Clearly, Google's got plenty of plans for what will happen inside Search. But today, we've got something a little different - this time, it relates to how Google's voice assistant will break out of Search, entering other Google apps to help you do more with your voice and perform more actions with Search in general.
There have been a lot of leaks lately, and they don't show any sign of slowing down - Yoel Kaseb (via Google+) has shared screenshots of what he claims to be a test build of a redesigned Google+ app. According to his post, the build is unstable and probably unfinished, and he has since been locked out from accessing or using the APK. But what we can see from the screenshots Kaseb managed to capture is both compelling and in line with some of the other leaks we've seen recently.
An Amazon phone has been rumored almost as long as an Amazon tablet, but now we might have actually caught our first glimpse of this unicorn device. Photos acquired by BGR show a phone clad in protective armor to hide the design. It appears to have a number of unusual sensors on the front, but the accompanying information points to a use for them – Amazon's Kindle phone will allegedly have a 3D interface.
Several weeks ago, we caught wind of Android 4.4.3 and some of the changes it could bring, consisting mostly of bug fixes, both big and small. At this point, according to several sources familiar with the matter, Android 4.4.3 has entered internal testing outside of the core Android team - a process otherwise known as dogfooding. The final release isn't expected to hit public devices for a number of weeks, so those of you expecting it any day now will have to wait just a bit longer.
We've reported on several Google Now-related rumors recently. If our information is accurate, Google Now will soon be able to help you remember and pay for bills, automatically infer events from your communications, and serve you reminders depending on who is near you. Today, we've got another one. This time, Google wants to help you remember where you left your car.
Occasionally, an OS update will bring around features that really change things. Android 3.0 brought the Android experience to tablets. 4.0 completely revamped the UI and added guidelines that made Android look cohesive for the first time. 4.4 added Svelte, which promised to seat Android comfortably on an even broader range of devices. We have reason to believe another one of those changes is right around the corner, and it's known internally as Hera.
In a bit of unexpected news, the Verge has just posted images and descriptions of Android TV, based on information provided to them by an unnamed source.
Android TV, according to the Verge, is Google's renewed bid for the living room, looking to put Google TV in the rear view mirror, and deliver content in a cohesive experience that users will actually want to do. It does this by focusing on being an entertainment platform, rather than making your TV function like a large tablet with a remote.
According to a report from The Information, Google held a series of talks with Verizon Wireless in January covering a range of issues. A source familiar with the talks says one item on the agenda was Google's interest in becoming a mobile virtual network operator (MVNO) in markets where it offers Google Fiber. This isn't the first time a Google phone carrier has been rumored, but this might be the first time Android is strong enough to withstand the inevitable blowback from established carriers.
If there's one thing we hear time and again about Android, it's the F word: fragmentation. While it's largely just an annoying word used to get under the skin of Android fans, I think in at least one respect, it's been a valid criticism: the wildly varying experiences Android users have with the post-purchase support and software on their handsets. Now, it's equally correct to say that's not really Google's fault, nor its responsibility - OEMs are the ones dropping the ball in a lot of respects here, and I totally agree with that!