Recent access to a training video website introduces me to Bill Scott, UX Engineering Process. Experience from Netflix & Paypal allows for industry related stories during the 5 hour lecture. My notes below, with bold my favorites:
“The bits the customer touches, we [front end engineers] own.” –Bill Scott
Typical product life cycle: product over the wall to design, over the wall to engineer, delivery to customer.
Rapid Experimentation.
Netflix: over 90% or more of the UI code thrown away every year.
Design for throwability.
BUILD. TEST. LEARN.
design for volatility.
Get up & running so everyone can see what it is that we’re trying to build.
RITE <- google it.
Define the cadence of the group.
Azure mockup? … but it is on the laptop, just look at it here.
Kristine Profetti: How to do usability testing.
(What does GitHub internal mean?)
RAPID PROTOTYPING: use node.js. Javascript templates allow for run on server AND client. “Dust” is practical & works. Moustache, Ember, Handlbars, Underscore?
Twitter bower
“Resist desire to beautify the design.” Focus on learning.
UI Architecture: Native vs. Web: Hybrid approach: phonegap or use cordova. Avoid mimic native controls. Webkit? SDK? SCK? GPU?
RESS Responsive Server Side, also Luke W.
(Mobile first rocks, I got that covered.)
Don’t let the engineers drive the design.
I think I finally may have a grasp on “rapid prototyping”. So instead of directing the project from paper wireframes, quickly HTML in the skeleton of the pages, and on the pages that need special functionalities (like a custom calendar), you code-pretend that the functionality exists, making it look the same as if it were really there with quick HTML. Once every feature and functionality required by the project is clearly outlined in the HTML prototype, every member of the team can look at the prototype to “understand what it is that we are trying to build.”
