True innovation in the mobile space has passed.
On June 29, 2007, Apple introduced the iPhone to the world. It wasn’t the first smartphone—not by a long shot—but it was the first to really nail the experience. While the technology that powers mobile computing is improving exponentially, every smartphone (even every tablet) that follows the iPhone is a shade of what Steve Jobs unveiled over six years ago.
I’ve been using iOS7 on an iPhone 5 for several weeks now. With each Beta release there have been modifications to stabilize and improve the operating system. I have concerns about usability issues, especially for users who are new to the iPhone experience, but for the most part—aside from some stylistic choices and visual design inconsistencies—the new operating system is a step in a positive direction.
There’s one thing that’s been bother me though…enough to blog about it. Apple moved the Trash!
iOS7 Beta has a setting enabled by default on iPhones (I’m not seeing the same feature on my iPad) that is automatically tracking and storing users’ movements. Given the recent attention and outcry over NSA tracking and privacy, I’m sure this is going to ruffle quite a few feathers.
After living with the Pebble smart watch on my wrist, designing a Pebble watch app, and immersing myself in smart watch news, rumors, and trends, I wanted to compile a design wish list for upcoming smart watch manufacturers. You hear that Apple, Microsoft, Google, Samsung…even you Pebble (if you’re around long enough for a v.2)? These are the features you’ll need to include in your smart watch in order to make it a must have for everyone—not just gadget geeks.
After over a year of waiting (I backed the Kickstarter on 4/12/2012), my White Pebble Smart Watch finally arrived in my mailbox a couple weeks ago. Here’s my take on life with a smart watch.
At the cusp of an important decision about how to move forward with the architecture and design of our mobile application, the team was deadlocked. Tech was looking for a design solution to mitigate architectural issues that were causing instability. Design, while equally concerned about app performance, wasn’t interested in making a quick fix—potentially adding superfluous UI elements—for the sake of expediency.
