LAS VEGAS â€” Matias Duarte is a man who loves a challenge.
Itâ€™s part of why he took his current job at Google, leading the Android operating system team as head of user experience. In a nutshell, he is the man tasked with making sure Android looks, feels, and performs as smoothly as possible. And it is not an easy job.
â€œDesigning an open mobile operating system â€” and doing it really well â€” thatâ€™s never happened before in human history,â€ Duarte tells me, leaning forward in his chair and sipping from a cup of tea as we spoke in the garish hallway of a hotel on the Vegas strip earlier this week. He is visibly excited, seemingly up to the task when I note how big the challenge is. â€œIâ€™ve done the closed thing before,â€ he says, referring to his days at Palm working on the webOS operating system. â€œAnd Iâ€™d like to think I did it well.â€
Logistically speaking, his new gig is a nightmare. Not only does the Android team have to engineer adroit, adaptable code, but they must serve third-party developers who are trying to create apps for a constantly updated operating system. This second task has been especially difficult in the wake of the most recent Android code overhaul, version 4.0, also known as â€˜Ice Cream Sandwich.â€™
Duarte wants to remedy this. On Thursday, Google launched Android Design, a web site created specifically to help aid developers in the creation of applications for ICS. The site offers a comprehensive visual to third-party application developers, giving suggestions on everything from how to implement different visual elements to overall back-end patterns for the OS itself.
In theory, it will help developers better understand just how the Android team thinks about layout and implementation, while simultaneously giving suggestions to interaction designers on how to maintain visual integrity. Basically, it will help both first-time developers and Android veterans make apps look less crappy.
â€œWe havenâ€™t really had a style guide,â€ Duarte says. â€œWe havenâ€™t really given you a lot of guidance on how to migrate your application from a phone, perhaps, to a tablet. Weâ€™ve done so only by example.â€
Which has been a chief complaint of developers whenever another version of the OS is released. Developers are forced to reverse engineer the code from the new version and translate that to the previous version of Android to figure out how to move their app to the new software environment. Whatâ€™s more, Android averages a new version launch about twice a year. Itâ€™s an incredibly fast pace in the mobile world, not to mention a pain in the ass for mobile developers who just want to keep their apps up to speed.
The guide, then, will be continually updated with a running list of features, suggestions, and development methods, including things as granular as software button placement to as large as dealing with screen sizes.
â€œAndroid has had a lot of terrific developer API level documentation,â€ Duarte tells me, speaking of the code that developers use to understand how Android works, and how to make applications for the platform. â€œBut within our style guide we have things [where] we think, unequivocally, this is the way to make it Android.â€
By last count, over 700,000 new Android devices are being activated every single day. Thatâ€™s spread across dozens of manufacturers and hundreds of different types of devices, each with different hardware specifications and sizes. These device makers are free to choose the open-source Android as the operating system to run on their myriad different devices. And on each one, Android and its hundreds of thousands of apps must function, and function well.
Duarte hopes this can clean up Android apps, whether they look like sloppy ports from one version to another, or a rough app from a first-time Android developer. So in essence, the site could serve as a starting point for Android newcomers, a way to foster the fast-growing app ecosystem.
Itâ€™s the next logical step for the platform. Typically, developers hoping for app store success have launched their programs on Appleâ€™s iOS platform first, with Android eventually coming second in almost an afterthought. Part of this is incentivized by the bottom line. Itâ€™s often said that Android apps canâ€™t make you any money, while iOS is the more lucrative for budding entrepreneurs. The other part is due to the platformâ€™s success across the many manufacturers. Itâ€™s far less work to account for the handful of Appleâ€™s device screen sizes and hardware compared to the sprawling device portfolio Android manufacturers offer.
Ultimately, itâ€™s about finishing what Duarte started with the latest software release. As the biggest Android overhaul to date, itâ€™s Androidâ€™s true coming-out party, what the team considers the first true version of what the Android OS can be.
Iâ€™ve lived with an ICS phone for months, and consider the release the best theyâ€™ve offered yet. But the challenge now is getting app-makers up to speed, and making the software for the platform look and feel just as good as the stock system itself. Android Design is the first step on that path. And Matias canâ€™t wait to watch it flourish.
â€œThis is the second part of our Ice Cream Sandwich launch,â€ he says. As this site goes up, I can feel like itâ€™s finished. Like ICS is truly complete.â€
Revisit Wired.com next week for the full interview with Matias Duarte
Article source: http://www.wired.com/gadgetlab/2012/01/android-design-matias-duarte/