Take the 2-minute tour ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.

A few weeks ago I saw a story about a master app designer showing how he worked with good old pen and paper to do effective prototyping before writing code. I'm unable to dig up that story (and I think it was a video) but if you could recommend any other useful resources I'd appreciate them. I know roughly what I want to build, but want a useful framework for thinking about how the screens should flow together. The app I want to build is for the iOS platform, but I think the video might have been about creating a web app. Thanks!


migration rejected from stackoverflow.com Jul 2 '13 at 17:37

This question came from our site for professional and enthusiast programmers. Votes, comments, and answers are locked due to the question being closed here, but it may be eligible for editing and reopening on the site where it originated.

closed as too broad by MichaelT, Dan Pichelman, Kilian Foth, maple_shaft Jul 2 '13 at 17:37

There are either too many possible answers, or good answers would be too long for this format. Please add details to narrow the answer set or to isolate an issue that can be answered in a few paragraphs. If this question can be reworded to fit the rules in the help center, please edit the question.

3 Answers 3

Well that is a pretty broad question. But I think that you looking for storyboarding ( wire framing for the web). Using xcode's storyboard is a great way to lay out your application. There are a number of resources. I recommend you looking up Stanford's cs193p ios programming course.


This is a free lib for iOS apps prototyping: http://www.alterplay.com/ios-dev-tips/2012/04/prototyping-ios-applications.html It's based on Axure framework.


I believe the video you are looking for is http://www.infoq.com/presentations/Fast-Easy-Usability-Tricks-for-Big-Product-Improvements.

He argues to not use coded prototypes because the testers can't change them. And that changes the whole thing, if people can't change things they behave differently.