DigitalHermosa.com:: A Better Experience with iPad and iPhone Software
iphone ipad custom apps


This content is current as of:

Home > Methodology > Storyboard

Digital Hermosa, noun, originally from Spanish for 'beautiful view.' We're iOS Engineers.

iphone, ipad, software, ios, engineering
iphone, ipad, software, ios, engineeringHome
Marketing Objectives
About Us
User Experiences
Our Brand - Your Brand
Business Models

Our App Store Products

Accent Coach
DR_M
HillaryMail
Investment Dashboard 5
Knitting Queen
Lead Capture
NPMChapters
NPMConvention
Saint Rose of Lima
Say It On Billboard
UIColorBox

Our Methodology

Overview
1 - Analysis
2 - Storyboard
3 - Proposal
4 - Functional Spec
5 - Plan the Work...
Pricing Considerations
Get Started

Legal and other Overhead Stuff

Support
Privacy
Copyright
Site Map
Contact us

STORYBOARDS CREATE FORM AND OWNERSHIP.

Based on the information gathered so far, we can sketch out a storyboard in short order. Storyboards are typically Microsoft PowerPoint or Apple KeyNote documents where a slide might include a screen shot and words describing the function of various buttons, tableView taps and the like. The goal of this step is to give, what may only have been sketched on a napkin or whiteboard, described in words, or compared to an existing app, form and ownership to the User Interface.

We do this early in the project life cycle because it gives all the parties involved something to poke at, something to aim at, and something to reconsider. It also is what the target end user will see and live with every time they pull up the app.

We prefer to present the storyboard to the client in an engaging session, often face-to-face, to capture their ideas, decide what needs changing and otherwise shape the design assumptions to more closely match the client's perspective. It's when the client 'accepts' and therefore 'owns' the storyboard, we know that we've locked down (as best as one can lock these things down), the target of what we are to accomplish for them.