“I'm thinking based on your last post, there's a great talk in there, but rather than throw you to the mob with "Your framework sucks", I was thinking a talk entitled (something like) "Data Driven Decisions” would be awesome. Remy Sharp, email, Jul 2015
ERGONOMICS USER NEEDS • Fun to use. • Quick to build. • Works around bugs. • Gets me paid, yo. • Loads quickly. • Has smooth interactions. • Doesn’t slow down my phone. • Doesn’t crash. • Has features I want.
ERGONOMICS USER NEEDS • Fun to use. • Quick to build. • Works around bugs. • Gets me paid, yo. • Loads quickly. • Has smooth interactions. • Doesn’t slow down my phone. • Doesn’t crash. • Has features I want.
Model data requested Model data arrives JS requested JS arrives Page interactive Evaluation, load & execution BOOTSTRAPPING / “TIME-TO-INTERACTIVE” Load
Model data requested Model data arrives JS requested JS arrives Page interactive Evaluation, load & execution Load BOOTSTRAPPING / “TIME-TO-INTERACTIVE”
POSSIBLE OBJECTIONS • TodoMVC isn’t idiomatic. • TodoMVC isn’t my use-case. • A Nexus 5 / iPhone 5S isn’t what our users use. • It’ll be better in the next version of [insert framework here].
COSTS • Time. • Bandwidth. • CPU usage. • Frame rate. ERGONOMICS • Fun to use. • Quick to build. • Works around bugs. • Gets me paid, yo. • Memory usage. • Learning it. • Re-learning it. • Debugging it.