Ask Hackaday: Why Make Modular Hardware?

In the movies, everything is modular. Some big gun fell off the spaceship when it crashed? Good thing you can just pick it up and fire it as-is (looking at you, Guardians of the Galaxy 2). Hyperdrive dead? No problem, because in the Star Wars universe you can just drop a new one in and be on your way.

Of course, things just aren’t that simple in the real world. Most systems, be they spaceships or cell phones, are enormously complicated and contain hundreds or thousands of interconnected parts. If the camera in my Samsung phone breaks, I can’t exactly steal the one from my girlfriend’s iPhone. They’re simply not interchangeable because the systems were designed differently. Even if we had the same phone and the cameras were interchangeable, they wouldn’t be easy to swap. We’d have to crack open the phones and carefully perform the switch. Speaking of switches, the Nintendo Switch is a good counterexample here. Joycon break? Just buy a new one and pop it on.

What if more products were like the Nintendo Switch? Is its modularity just the tip of the iceberg?

Continue reading “Ask Hackaday: Why Make Modular Hardware?”

The Key To Modular Smartphones

Cellphone startup Fairphone is now taking pre-orders for their modular smartphone, which is expected to start shipping in December of this year. Although I’m much more familiar with Google’s project Ara, this is the first modular concept to make it to market. It does lead me to a few questions though: is this actually a modular smartphone, and how widely will modular concepts be adopted?

Continue reading “The Key To Modular Smartphones”

Google Releases Project Ara MDK

Ara Modules

 

It’s been a little while since we’ve heard about modular smartphones, but Google has just released the Module Developers Kit (MDK) for Project Ara. The development kit gives an overview of the inner workings of the project, and provides templates for building your own modules.

Once you’ve agreed to the license agreement and downloaded the MDK, you’ll find a large specification document. It explains how a phone will comprise of many modules loaded into an endoskeleton, giving mechanical support and electrical connections. An interface block provides each module with power and data over LVDS. Modules are held in place by an electro-permanent magnet which can be toggled by software.

When you’re finished with the specification document, you can dive into the reference designs. These include templates and actual modules for WiFi, thermal imaging, a battery pack, and more. Mechanical CAD is provided as STEP files and drawings, and electrical design files are provided as Altium projects and PDF schematics.

We discussed both Project Ara and Phonebloks on Hackaday in the past, but now we’re starting to see real details. Google’s Project Ara Developer Conference takes place on April 15th and 16th, and you can register to take part remotely for free. Is this the start of an open, modular phone? Let us know what you think.

[Thanks to Adam for the tip]

Ask Hackaday: Does Project Ara Solve The Phonebloks’ Problems?

Our tips line is blowing up again, this time directing us to Motorola’s Project Ara: a phone with modular components that plug into a base “endoskeleton.” If you missed the news coverage strewn across the web and you are doing a double-take, that’s because Project Ara is frighteningly similar to the (presumed vaporware) Phonebloks concept from a few weeks ago. Phonebloks was the subject of our last “Ask Hackaday” article, generating hundreds of comments ranging from those defending the concept to those furiously opposed to it.

There’s a conspiracy theory circulating that suggests Motorola released the Phonebloks concept as a viral marketing scheme to generate hype before revealing the official product line. We suspect it’s a bit less conniving. As [jorde] explained on Hacker News, an Israeli startup, Modu, had developed a similar modular cell phone several years ago, and Google bought the patents in May of 2011. A few months later, Google bought something else: Motorola. It seems likely that Project Ara is merely a resurrected and revised Modu, and Motorola conveniently announced it in the wake of Phonebloks’ popularity. Regardless, Motorola has announced that they have partnered with Phonebloks’ creator Dave Hakkens .

So what’s different? Phonebloks was met with cries of “vaporware!” and fervent arguments raising concerns about unavoidable hardware limitations. Motorola claims their goal is:

to do for hardware what the Android platform has done for software: create a vibrant third-party developer ecosystem, lower the barriers to entry, increase the pace of innovation, and substantially compress development timelines.

Unlike Project Ara, Phonebloks didn’t consider open-source hardware (Wayback Machine link), and Motorola makes an interesting argument here: that advances in 3D printing indicate an evolving “open hardware ecosystem,” and the next era of phone development may rest in the hands of your average hacker or a small startup company. Some speculate that the Ara will be similar to the relationship between a PC and its peripherals: Motorola provides the essential guts while giving you some slots for attaching additional components. Let us know in the comments what you think about Project Ara: is it just more vaporware, or a watered-down but plausible alternative to Phonebloks?  And, perhaps most important: do you, as a hacker, want a phone that supports open hardware and lets you plug in “peripherals?” The Phonebloks website has since changed to reflect the partnership with Motorola, and includes a new video that you can watch below.

Continue reading “Ask Hackaday: Does Project Ara Solve The Phonebloks’ Problems?”