Skip to content

FITC 2013 – Day 3

The science of effective software design
Demo regularly feature sets
Just enough software
Don’t make all your decisions upfront
Observe the actions if your users through logs and activities
Build > measure > learn cycle
People are horrible at describing what they need
We don’t need to get it right the first time… Is easy to iterate on the web
Make hypotheses not assumptions
Feature validation with small placeholder feedback buttons before actually building
Statistically significant
Validate assumptions
A/B testing and ramp ups
Online products or plugins for a/b testing
Google content experiments
Exposing features to a small group of users
Multi phase roll outs
Changes aren’t truly validated until they’re in production
Developers need to think differently about how to evolve a system in production
Quality needs to be baked in
“We can’t release because we are not done”
Product design process just change to accommodate experimentation

Experimenting at the edge of digital: robots technology and natural interactions
Show latency creatively. Used bubbles that stretch and then bounce into when loaded
Fight for your values
Invest in what you believe
Identified a pain point


Media convergence

Responsive design techniques, tools, and design strategies
Flexible fluid grids
Flexible images and media
Media queries
Percentages can be very precise, browser will calculate the pixels
Responsive inspector for chrome
Takes full page height screenshots
Desktop down vs mobile first
Design first vs common breakpoints
320 mobile
1920 desktop
Pixel medias queries vs em media queries
Horizontal and vertical media queries
Adobe edge reflow
Not a developer tool, design only
Limited CSS export

Understanding the nature of reality

Post a Comment

Your email is never published nor shared. Required fields are marked *