Pages
Archives
- September 2011
- April 2011
- February 2011
- January 2011
- November 2010
- September 2010
- August 2010
- July 2010
- June 2010
- May 2010
- February 2010
- January 2010
- November 2009
- October 2009
- September 2009
- August 2009
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- February 2009
- January 2009
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
- September 2007
- August 2007
- July 2007
- June 2007
- May 2007
- April 2007
- March 2007
- January 2007
- December 2006
- November 2006
- October 2006
- September 2006
- August 2006
- July 2006
- May 2006
- March 2006
- February 2006
- January 2006
- December 2005
- October 2005
- September 2005
- August 2005
- May 2004
- March 2002
- October 2001
Sexy schemas?!
Jeremy Zawodny decided to “annotate” Tom Coates’ recent Future of Web Apps presentation. Not sure the annotations really add much value, in fact, one seems particularly backwards:
Start designing with data, not pages
Figure out what data is important, how it will be stored, represented, and transferred. Think about the generic services that one can build on top of that repository. Only then should you get the wireframe geeks and/or the photshop geeks involved.
This is scary, because you won’t have a mock-up right away. Your PowerPoint presentations will look as if they’re missing something. But that’s okay. This is about doing some engineering style design before product design and interface mocks.
Emphasis mine. Great recipe for creating something no one except an engineer wants to use. It’s a shame really, go grab Tom’s entire PDF presentation (16MB) and page through it. The example sites he references and the imagery, now that’s compelling. There’s a story there, something that grabs everyone. When you get folks passionate about experiences, about making their lives easier, you get customers for life. How can you not do product design first?
For example, using one of the best user experience cliche ever: the iPod. Apple didn’t begin by designing an ID3v1.1 tagged file player. Now they just ask “Which iPod are you?”