Demo #1 Task
You've built your first app slice. Time to show it off with a demo!
You have at most 3 minutes to demo. To make the most of it,
- Show your team slide.
- Show your product box slide. Don't spend more than 15 seconds on this. People can read faster than you can talk.
- Demo with a story. Act it out. Show, don't tell.
- Take notes. Have at least one team member designated to write down notes on things that didn't work, and comments from the class.
A product box should quickly convey what your app is supposed to do, in a familiar format, namely the description you would expect to see if this were a package on a shelf, or an entry on an app store.
The key components of a product box are:
- A screenshot, showing the value of your app.
- This will often be the same as your payoff screenshot in Panel 3 of your four-panel storyboard.
Two to four value propositions.
- These should be payoffs not actions, e.g., "Find new places to eat!" not "A user can search for places to eat."
Do NOT give a feature tour. Feature tours are the worst possible way to demo an app, and terrible at guiding app design. Microsoft Word has thousands of features. Most of them are never used.
The right way to demo is with a story. A story has realistic people in a realistic situation. They have a problem. Your app comes to the rescue and solves the problem. That's what a demo needs to tell. That's all a demo needs to tell.
A good demo story tells you what you need to implement first. For more on designing with stories, see Storytelling by Design by Kim Goodwin.
Questions? Ask your team mates. Still unclear? Post questions to Piazza.