Design, then Code

Design, Then Code is a nice place to begin thinking about making an app for iOS devices. The name is certainly good, in that it stresses thinking about the user experience in advance of building the code that creates the functionality, but the idea that one can do all the design work ahead of the construction is something that I thought we were long past. I understand that they are responding in some fashion to the sort of user experience nightmares that folks often point out as being the great weakness of Google’s application offerings, where there is a lot of functionality, you just can’t figure out how to get to it.

Why does it have to be one or the other? I thought we were beginning to figure out that it has to be both?

Leave a Reply