It would be easy to blow off Google’s “Project Ara” modular smartphone concept as just another one of those Google science fair projects that will never come to anything. Remember “Google Wave” anyone? Yeah, we were all “waving” bye-bye to that one before it ever got off the ground. As engineers, we all know that only one out of every dozen or more cool technology ideas ever comes to anything interesting. But, Google’s propensity for over-funding lots of blue-sky projects just to see if anything sticks is well known, and it is a fertile breeding ground for highly-public failures.
The marketing for Ara doesn’t help much either. Billed as the “smartphone for the next five billion people,” the marketing concept just doesn’t hold water. The implication is that all those people out there who currently don’t have a smartphone (you know the ones) have been just waiting around patiently until somebody gave them a phone they could customize with various application processors, wireless modules, memories, screens, cameras, and accelerometers. Hmmm… Just take a quick poll of the folks you know who don’t yet have a smartphone. Think it’s because they really really want the quad-core? Yeah, me neither.
Forgetting the five billion fantasy for a minute, just who would want a smartphone that you can customize with a wide variety of plug in modules? Probably folks like engineers, that’s who. So, while Google’s marketing seems to indicate they’re aiming at the long tail of the smartphone adoption curve, they’re much more likely to find their customers in the early-adopter crowd.
That’s all OK, actually. Ara doesn’t have to fulfill the promises of its marketing hype in order to accomplish something truly revolutionary. But, before we dive into our analysis, let’s take a step back and look at what Ara really is.
The idea behind Ara is to build an open hardware architecture for smartphones. The core of the device is an aluminum endoskeleton – a frame that can accept plug-in modules of varying sizes. Initally, three different sizes of endoskeletons are planned – small, medium, and large. In theory, you could own multiple endoskeletons and move modules around between them constantly, depending on your needs. Want something tiny to slip into your pocket? Populate the small frame. Need to do some serious work? Grab the big one and slip on a large screen – and you get something like a “phablet.”
The modules are held into their slots in the endoskeleton by a clever electropermanent magnet scheme. The magnets hold fast with no power applied, and they can be electrically released on command. In order to avoid electrical connectors, close-proximity capacitive connectors are used – with SerDes links that support up to 10Gbps to the backplane. The connections are accomplished via a (new) MIPI standard called MIPI UniPro (which, when combined with MIPI M-Phy creates MIPI UniPort-M). While some of the details of the connectors and the magnet scheme have yet to be completely worked out, the idea is to provide for interchangeable modules that can be completely smooth with no connector pins or sockets.
Modules can be designed by any third party (yep, this means YOU, so go ahead and grab yourself a dev kit and get crackin’). What would such a dev kit look like (we hear you ask)? Well, imagine an FPGA development board with a Lattice FPGA on it – in smartphone module form-factor – and you’re pretty close. Lattice also supplies the tiny tiny FPGAs that connect each module to the backplane, so – counting up modules and backplane connections – there could potentially be a 2-digit number of Lattice FPGAs in a single Ara smartphone. Nice socket score for Lattice, and also an FPGA application that really no other FPGAs were positioned to capture given the form-factor and power constraints.
Every single component of the phone is modular: applications processor, screen, memory, battery, wireless, accelerometers, camera, GPS, that-thing-you’re-designing – all of it plugs right in. Of course the OS is slated to be Android, and it turns out that making Android work in an Ara-friendly way is no small chore. It seems that Android has historically been custom built for each unique hardware configuration – which is easy when your customers are companies like… Samsung, and there are a small number of phone configurations to support, and end-users aren’t CHANGING those configurations DAILY in the field.
So – Android needs a tweak or two under the hood (where “tweak” may be defined as near-total-re-write, but we digress). The team is working on a new, more module-friendly Android as we speak. At the recent Ara Module Developers’ Conference, we got to see the world’s first public demo of an Ara prototype actually booting Android. So – it can be done.
Now, I know you all want to run out and start designing amazing whatsits for Ara phones, and it makes sense. After all, you probably haven’t gotten the call from Apple or Samsung telling you they just had to have your [insert cool thing here] in the next iPhone or Galaxy, but Ara gives you a chance to do it anyway. It’s the self-publishing model for smartphone hardware – complete with a hardware version of an app store. But, before you order your MDK (module developers’ kit) and start cranking out the Verilog, let’s talk a bit about what Ara is and what it isn’t.
It’s pretty easy to imagine being frustrated by a phone that is really a cluster of modules, when we’re used to the hardened, monolithic chunks of tech wizardry we all currently carry around. Will Ara phones survive the drop test, or explode into a frustrating pile of modules and broken displays? How will you recover a bricked phone that has no power – when it requires power to get the endoskeleton to loosen its death grip on the modules? Will it feel cool in your hand? The questions go on and on.
Yeah, they’re working on all that. It’s a prototype, OK?
However, picture available camera modules from players like Canon, Nikon, and Fuji. Imagine being able to choose from a variety of displays. Picture special medical plug-in modules, or a high-end oscilloscope probe interface that slides right into a module bay. When you start thinking about specialized capabilities that could be put into smartphone modules, the architecture suddenly transcends our vision of “smartphone” into something more – a modular, extensible, connected portable computing platform, which could be the base for just about any kind of mobile application.
There are other nice side-effects of the architecture as well. If you drop your phone and break the screen, just pop in a new one. If they come out with a faster processor, a better battery, a really cool blood chemistry analyzer, fitness monitor, or other “oh, I need to upgrade” kinda’ capability – you don’t need to upgrade. You just pop in the new module. Biennial smartphone obsolescence could potentially become a thing of the past.
We don’t know if Ara will take off, or go the way of the Newton. However, like the Newton, some important concepts Ara introduces will almost certainly survive – and that will be good for all of us.