5. AND IF THERE ARE MORE...
Thursday, November 14, 13
6. TIME AND UNKNOWNS
• Do
we create compositions for all different permutations just
to get a sign off? (a lot of time needed)
• Will
it work on the device? (unknowns)
Thursday, November 14, 13
7. DESIGN APPROACH
• Just
in time Design
• Done
• Layered
just before the development team needs it
Design
• Skeleton
• Muscle
• Skin
- Initial design work, think Layout
- Content to fit in Layout
- Visual Design
Thursday, November 14, 13
22. PROBLEM
• The
sketches were good to allow us to make a decision on a
proposal of an idea, but we were missing:
• The
interaction of the idea on the actual device (ie. what
happens when the keyboard appears on landscape)
• The
actual spacing of the elements on page (ie. when
padding, margins and actual graphics were used the space
issue comes up immediately)
Thursday, November 14, 13
24. REFINING THE DESIGN PHASE
Prototype
Analysis
Sketches
Build
Visual Design
Thursday, November 14, 13
25. A COUPLE OF NOTES
• Prototype
is useful when:
• there
is user interactions (input field, youtube video, etc)
• there
is uncertainty around page layout/reflows
• Visual
designs is obviously a must for the build.
Thursday, November 14, 13
32. OUTCOME
• Test
page will exercise all breakpoints to ensure coverage
• iframe
to trigger mediaquery breakpoint
• screenshot
• Makes
Thursday, November 14, 13
capture to ensure no regressions
HTML/CSS refactorable
34. LEGO BLOCKS
• Made
use of OOCSS techniques to build a library of
components
• Made
these components intrinsically responsive
• Building
pages will just be a matter of composing these
elements
Thursday, November 14, 13
45. WINS
• Less
sign offs and more collaborations & showcases
• Software
• UI
was designed to better suit the device
test coverage enabled weekly/fortnightly releases
• UI
library of components enabled quick development of new
features.
Thursday, November 14, 13