Both Facebook and Amazon are rumored to be preparing to launch their own smartphones, both running their own takes on Android, and both placing their HTML5-based services at the heart of the mobile experience. Of course, neither is confirming the move, but that just follows in a long tradition of web players turned handset vendors, such as Google and Microsoft. The question is, why do software houses and retailers suddenly feel the need to turn into device vendors, taking on the very different economics of that business, and making themselves reliant on a mobile manufacturing partner while alienating other platforms for their services?
Google, Facebook and Amazon all have the reach to make their offerings ubiquitous on every mobile device around, without having to own the hardware itself. And they might have learned some lessons from Google’s Nexus experience. If they try to be too disruptive, bypassing traditional channels or angering other mobile partners, they can actually reduce the reach of their key services. Yet if they do not do something radically different, there is no point having their own phones at all.
There is an element of Apple envy, but none of these web firms can emulate the integrated hardware/software experience of iOS because they are working with open source platforms and web services, not a closed environment. Their huge reach and influence depends on that, yet they hanker for at least a little of the iPhone maker’s control. So Amazon and, reportedly, Facebook will use their own tweaks of Android, creating their own user interfaces and developer platforms. The plus side ‘ a user experience optimized for their particular offerings; the downside ‘ fragmentation of Android.
So, we may argue that these companies are excellent at delivering services across multiple platforms, with a strong and consistent user interface ‘ and moving into hardware will only compromise those strengths. The proof seems to lie in Nexus, now largely a showcase developer product rather than a mass consumer device; and even more in the conflicts, internally and within the Android community, which Google will face once it completes the takeover of Motorola Mobility. And yet, we have to acknowledge that Amazon is already achieving what Google failed to do, launching its own-branded devices (first ereaders, now the Fire tablet) to deliver the best experience for its content and commerce, yet without any apparent dilution of its presence on third party products.
It has done this by creating gadgets which were directly relevant to its services, particularly its digital content stores and cloud offerings, and which had limited existing competition, enabling it to be disruptive in price and to amass large market share quickly. So the Fire, if it lives up to the high expectations for its sales, will do that by being affordable and coming with a different proposition to that of the iPad, and one which will only reinforce the Amazon experience.
It is doubtful whether Amazon could do the same in the overcrowded handset space. Here, there will be little room to differentiate. The content experience will inevitably be weaker on a small screen and it is questionable how far Amazon could differentiate its own version from its native and HMTL5 apps for other Android or iOS devices, with the exception of its innovative Silk browser.
And being price disruptive in order to get its services into more hands would be a marginal tactic ‘ with low cost smartphone vendors and carrier subsidies, most users are accustomed to getting their handsets virtually for free anyway. However, it might be able to shift the price/functionality ratio somewhat – CEO Jeff Bezos has stressed that the firm is ‘the only hi-tech company that operates on low margins’ because of its roots as a retailer, and it may also use those economics to price its handset very cheaply, as it has done with the Fire. It could deliver greater functionality than most low cost Android phones, to appeal to the prepaid base, reducing reliance on carrier subsidies, and even support its own MVNO, or embedded data connectivity (as in the Kindle ereaders).
According to Citigroup, citing supply chain checks, Amazon will launch a smartphone next year which will cost between $150 and $170 to manufacture, and the firm thinks Amazon would sell it for very little profit in order to boost uptake and stimulate its content and app sales. “For a normal brand like HTC, they need to price the product at $243 to make 30% gross margin,” says the research note. “If Amazon is actually willing to lose some money on the device, the price gap could be even bigger.”
The phone would presumably be tightly integrated with Amazon’s Android Appstore and its other shopfronts and support Silk, which made its debut on the Kindle Fire and promises more efficient use of mobile resources by doing most of the processing in the cloud. But Amazon is already gaining ground on Google’s Android Market via its existing apps for third party Android handsets, so there will only be a point to launching its own smartphone if it can significantly improve on the usual user experience for the Google OS, in order to drive greater content consumption.
Citigroup does not think the retailer will take the plunge until the last quarter of next year, based on its channel checks in Taiwan. Analyst Mark Mahaney thinks the Foxconn/Hon Hai group will co-develop the device as well as manufacturing it (it does the same for the Kindle ereaders and tablet), and that Amazon will stick with the same chip families as the Kindles ‘ TI OMAP 4 and Qualcomm basebands.
Even less proven as a hardware player is Facebook, which is said to be commissioning an own-branded smartphone from HTC. Since HTC, along with various other vendors such as INQ, already makes ‘Facebook phones’, with their user interfaces centered entirely on the social network, it is questionable how much difference this would make in the consumers’ eyes. The power of the Facebook brand, and the promise of a super-efficient social experience, is undoubted ‘ 3 Group and more recently Orange have traded on offering this, with handsets co-branded between their own logo and Facebook itself.
Going one step further and commissioning its own handset, rather than partnering with an existing brand, would only deliver additional value if the resulting phone furthers Facebook’s agenda in other ways, otherwise it will just split the existing market and potentially anger key partners, like 3, in the important web-phone midmarket ‘ where the social net’s much-vaunted mobile usage growth is concentrated, and where operator alliances are most important for effective distribution.
In this latest round of chat about the long rumored ‘Facebook phone’, there are hints that the device would be more than a branded, but otherwise, conventional design. Like Amazon, Facebook is thought to be creating its own twist on Android, encouraging a separate (though not incompatible) apps base to boost its goal of turning its social net into a complete apps platform. This would combine the developer appeal of Android with the ability to incorporate Facebook’s APIs in the programs, bringing thousands of new third party capabilities to the overall experience.
Also like Amazon, Facebook would create its own user interface overlay centered on its services, something it may feel is more necessary now that Google will be pushing its rival Google+ to the heart of the standardized Android look and feel. All a Facebook spokesperson would say was: “We think every mobile device is better if it is deeply social.” But some analysts think it has to work harder to ensure that ‘deep social’ experience continues to revolve around its own product and not Google+.
Like other web players turned phone suppliers before it ‘ Google, Apple et al ‘ it is keeping very quiet about any plans. The new report comes from the Wall Street Journal’s All Things D blog, and claims: “The phone is being planned to run on a modified version of Android that Facebook, tweaked heavily to deeply integrate its services and support HTML5 as a platform for applications.”
This would see Facebook moving well beyond a mere handset optimized for its social network to an Amazon-style attempt to hijack the Android experience for its own offerings. The company has already put HTML5 at the heart of its strategy to expand its social net seamlessly across different device types, and to turn it into a complete platform and communications hub to rival those of Google and Microsoft.
It is clearly in the interests of both Facebook and Amazon to dilute Google’s control over the Android experience, which it has aimed at making its own applications universal. Some ask why they would work with Android at all, and both have been linked to possible interest in buying Hewlett-Packard’s webOS in order to control their own platform. This would bring either firm an OS more inherently suited to the emerging mobile usage trend, to rely on web apps, streamed content and cloud storage rather than native apps and files ‘ a cloud-oriented world where both firms aim to steal influence from Apple and Microsoft, which are less naturally attuned to that environment.
However, as HP itself found, attracting developer and user support for a new OS is an uphill battle. But the answer to that problem, and the seemingly untouchable influence of iOS and Android and their app stores, is HTML5, delivering web apps uniformly to any OS and with functionality close to that of a native program. Facebook’s reinvention of its platform and its multi-device strategy around HTML5, and Amazon’s use of the technology to bypass Apple’s storefront, are early symptoms of the wave to come. We are not convinced either needs the distraction of its own handset to make their cloud strategies a success, but if they usher in a fully blown and appealing HTML5 experience to the handset mainstream, rather than the still niche tablet or cloudbook segments, their brand power could help move the mobile market ahead again, as Google did when it (controversially at the time) turned it hand to operating systems.
Google’s fight nowadays is almost as much with those trying to usurp its role as the defining face of Android, as with Apple. Its Google+ is chasing Facebook, while it needs to defend the supremacy of Android Market against Amazon, while expanding its own digital content offerings, which have been overshadowed by those of Apple and Amazon. The past week has seen the search giant hitting back with two new elements in its quest to deliver the perfectly integrated connected lifestyle to its customers’ various devices. It has announced the full US availability of its iTunes-style music service, and is streamlining its payments processes by merging Google Checkout and Wallet.
The long anticipated Google Music may be far too late to damage iTunes seriously, coming eight years after that service made its debut, but it does fill an important gap for those who want to do most of their content consumption on Android, and outside the Apple closed environment. The new offering allows customers to buy songs through Android Market, and to store and stream up to 20,000 tracks in the cloud.
Google tends to be weaker than Apple or Amazon in creating slick purchasing experiences (as seen in its bookstore and, indeed, Android Market itself). But it does have the market weight to get device, apps and content support behind its platforms. It has signed deals with 1,000 record labels, including most of the big ones ‘ UMG, Sony and EMI Group ‘ giving it a total base of about 13m tracks. However, it has not yet signed Warner Music, which is reported still to have concerns about piracy and pricing. As with rival services, some songs are free, while others cost between 69 cents and $1.29.
Like Apple with its latest iTunes enhancements, Google is harnessing social networking, integrating the music store with its Google+ system to support sharing and discussion of songs.
‘Music is more important to Google than ever before,’ Jamie Rosenberg, director of digital content for Android, said at the launch event, promising value added content to surround the songs themselves, including reviews, band information and exclusive tracks from artists such as Coldplay. Users will get 90-second previews of songs before they buy. Artists can pay a one-off $25 fee to create their own pages to display videos and information, in a way reminiscent of MySpace, and to sell self-published music for a 70% share of the revenue generated.
The importance of carrier billing in stimulating purchases has been seen clearly in other parts of Android Market, so it is no surprise that Google has formed an alliance with T-Mobile USA to allow its subscribers to buy tracks and put them on their mobile bill.
In another aspect of creating a smooth digital payments process, Google is to merge its Checkout online payment processing system ‘ which has struggled to make inroads on eBay’s PayPal ‘ with its fledgling m-commerce offering, Google Wallet. This will integrate the payments chain across Android Market, YouTube and Google+ Games in a stab at the unified purchasing worlds of Amazon and Apple. Consumers who shop with merchants who accept either Wallet or Checkout will be able to supply their Wallet username and password to complete a transaction. “There’s no need to pull out your credit card or enter your shipping address with every transaction,” wrote Wallet product manager Ben Lee on a company blog.
The NFC-based Google Wallet enables consumers to make purchases and collect or redeem offers by tapping their Android handset at US retail outlets supporting MasterCard PayPass terminals.