5 ms·
Wasn't sure what "Apple's 10-3-1 prototyping process" involves; it ends up that the title is pretty self-explanatory: Apple designers come up with 10 entirely
by joelhaus 16y ago
Wasn't sure what "Apple's 10-3-1 prototyping process" involves; it ends up that the title is pretty self-explanatory:
Apple designers come up with 10 entirely different mock ups of any new feature. Not, Lopp said, "seven in order to make three look good", which seems to be a fairly standard practice elsewhere. They'll take ten, and give themselves room to design without restriction. Later they whittle that number to three, spend more months on those three and then finally end up with one strong decision.
[Source: http://www.businessweek.com/the_thread/techbeat/archives/2008/03/apples_design_process.html http://www.businessweek.com/the_thread/techbeat/archives/200...]
- tomlin 16y agoExcept mock-ups != prototype.
- joelhaus 16y agoPicky, picky. Semantics: http://en.wikipedia.org/wiki/Prototype#Semantics http://en.wikipedia.org/wiki/Prototype#Semantics
- tomlin 16y agoI'm picky because, as a coder, I have to personally deal with different variations of what people think "prototype" means. One client thinks prototype means "mock-up", another thinks it means "ready to go" after a round of QA. Surely you can see how this might effect a project overall?
- joelhaus 16y agoNo doubt. That's why specifying project requirements and writing proposals is usually so important for both client and coder. Managing expectations is key.
- tomlin 16y agoManaging is a waste of time. Working smart is better. It's simple. We have a word for mock-up or comp. We have a word for prototype which is...prototype.