Company / division: Android
Moto X4 Brings Android One to the US and Google’s Project Fi (Sep 20, 2017)
Google’s Android One project for emerging markets was launched in 2014, and focused on countries in the Indian subcontinent and other parts of Asia. But it’s appeared to be struggling, with little recent positive news from vendors supporting it in those countries. In addition, at its I/O developer conference this year Google announced a project internally called Android Go, which is focused on optimizing Android for low-cost devices and therefore seemed to be in somewhat the same vein. But the funny thing about Android One is that’s it’s been morphing somewhat from a project for the low end of the Android market to one more targeted at the mid market. There have been several Android One phones through Sharp in Japan since mid-2016, and now Xiaomi is announcing a device. which seems at least in part targeted at India.
The most interesting thing about Xiaomi as a partner is the fact that it’s always majored on its proprietary UI – MIUI – as a differentiator for its devices, and it’s arguably that the fairly locked-down Android One was intended at least in part as a response to Android OEMs’ customizations, so this is certainly a departure for Xiaomi. As with the Japanese phones, though, this one is also targeted at the mid-market, selling for a little over $200, with 80% of handsets sold in India below $200. So it’s a poor fit for the original focus of the Android One project, which is arguably now being taken over by the Android Go initiative, but indicative of what Android One is evolving into. The big question is whether the device will actually sell, given that a Xiaomi phone without MIUI is a tougher sell and there are plenty of other cheaper Android phones in the countries the companies are targeting with this one. There’s certainly no guarantee Android One does any better in India at $200 plus than it did at $100.
Google today announced ARCore, an equivalent to Apple’s ARKit tools for developers to create AR experiences on Android phones. Importantly, it’s not tied to the latest version of the Android operating system but rather is being implemented on a device-by-device basis, with Google’s own Pixel and Samsung’s Galaxy S8 the first devices to support it, with the latter running Nougat rather than Oreo. There are two ways to look at this announcement, given the timing: on the one hand, it looks like a response to ARKit and the massive positive buzz that’s received since it was announced in June; on the other, it’s a natural outgrowth of the work Google’s done with its much higher end Tango AR framework in the last few years, and that’s certainly how Google’s pitching it. I think the reality given the speed with which this has been released is that this was something Google was working on pre-ARKit but has accelerated in light of the ARKit launch.
Its blog post headline is “Augmented reality at Android scale” and you can read that one of two ways: on the one hand, as a counterpoint to ARKit, which runs at the somewhat smaller iOS scale, but on the other as an acknowledgement that – interesting though Tango is as a platform – it was never going to achieve true Android scale. The rollout plans here are a little vague – Google hopes its “preview” of ARCore will hit 100 million devices sometime this winter, which is likely a fraction of the iOS devices that will support ARKit by that time, but there’s potential for broad rollout of this platform to most recent premium Android devices over the next couple of years. That’s likely short of true Android scale (2 billion plus phones) but would likely hit the devices where it’s most relevant, which are those that compete more directly with the iPhone, though Apple will enjoy a year or two of significantly greater adoption before Android starts to catch up.
At this point, it’s hard to see Tango as anything other than a time-consuming and expensive failure in its own right, but it’s clearly allowed Google to learn a lot which can now be applied to ARCore and therefore be much more useful and widely available. Between Apple and Google’s launches, it’s clearer than ever that smartphone AR will be by far the largest chunk of the overall AR/VR spectrum, and we should see some really interesting implementations over the next few months.
Android Police has a review of the Asus ZenFone AR, the second phone to carry Google’s Tango augmented reality technology. It sounds like it’s a big improvement over the clunky first phone from Lenovo, but it certainly doesn’t sound like it’ll be a big seller, while Tango itself doesn’t sound like it’s moved on much either. The review is worth noting because Google has been in AR for far longer than Apple, and yet Tango seems to have stalled at the experimental phase, with lots of effort from Google and yet very little to show for it. Two phones, neither of which will end up selling in large numbers, very few apps and essentially no meaningful position in AR just at a time when the space is about to take off thanks to Apple’s entry through ARKit in iOS. That’s something of an indictment of Google’s failure in this area, with its Daydream VR effort faring a little better but also not yet finding a sizable market niche to call its own. One other thing to note from the review here: it sounds like Tango absolutely hammers battery life on this device, and that’s something that will be well worth watching when ARKit-based apps launch on the iPhone in September. Pokemon Go has already taught us that apps featuring AR (and location-based elements) can be hard on batteries and still be popular, but it will detract from AR’s popularity on the iPhone if ARKit apps show a comparable tradeoff in battery life.
via Android Police
The Verge seems to have secured the first of two exclusive looks at Android founder Andy Rubin’s new phone, from his company Essential (Recode’s Code Conference will have an interview with Rubin tonight where I’d expect him to share more). So far, there’s nothing about the software, beyond the assumption that it’ll run Android. So the focus is entirely on the hardware design, including the materials, connectors, and a theoretical ecosystem of modular add-ons (for now, there’s just one: a 360° camera). The reporting on this is all a little breathless – Andy Rubin has quite a reputation and anything he launches will be accorded a fair measure of respect. But the pitch here feels so much like almost every other new entrant in the market, a mix of straw man arguments about the current state of the market, grandiose claims about how all that will change, ambitions to build an ecosystem without any evidence that any other player is interested, and nothing at all about distribution, which continues to be the key question in the US smartphone market. We’ll hopefully know a little more by tonight, but I’m extremely skeptical that this phone will do any better than any other recent attempt to change the smartphone market. In the meantime, that won’t stop this project from getting tons of positive media attention in the run-up to an actual launch sometime later this year. It’s worth noting that beyond the phone there are some other bits and pieces too, including a smart home OS and speaker with a screen, but again the details are so short and claims so grand that I’m inclined to ignore them until we actually know something specific about them.
via The Verge
PayPal Partners with Google around Android Pay (Apr 18, 2017)
Google Forced to Unbundle Services from Android and Open to Search Competitors in Russia (Apr 17, 2017)
The EU is currently taking action against Google over what it sees as anticompetitive practices including bundling of its own services and blocking competing ones from being pre-installed in Android. As such, this Russian case takes on more importance than it might otherwise have, because it presents one possible outcome of the EU case, which is forcing Google to unbundle its own services from Android and allow competing search engines like Yandex to be pre-installed. That’s certainly a possibility in the EU case too, and would mirror the action taken years ago against Microsoft over browsers in Windows. If that were to happen, I’m skeptical many people (or OEMs) would choose alternative search engines on an Android phone, but it would potentially threaten Google’s Android business model, which is entirely about the apps and services it runs on the device (and the advertising they enable). For what it’s worth, as I wrote in this piece at the time the EU action was announced, I still think it’s misguided.
Google has today announced a patent licensing alliance which is intended to provide cover to member companies using each other’s patents. The idea is that any member can use any other member’s patents without fear of being sued, something that’s actually been quite common between members of the broader ecosystem over the last few years. The alliance has only nine members to start with, about half of which are smaller smartphone brands, but the members do include Samsung, LG, and of course Google itself, as well as Foxconn. Those members alone apparently have 230,000 patents between them which will now be freely available to other members within the context of Android devices. This is a fascinating move, and it’s impressive that Google was able to get Samsung and LG in particular on board without also having some of the other big Android vendors. Of course, none of this will stop these companies from suing those outside the Android ecosystem (or this alliance), but it might help temper some of the animosity that has sometimes characterized competition between Android OEMs.