31. 1. Existing team abilities
2. Fast to dev
3. Remote updates
4. A “cheap” test
5. Something > nothing
gearoid.io • @gearoidorourke Mobile Moments 2016
33. gearoid.io • @gearoidorourke Mobile Moments 2016
1. Trigger.io limitations
2. Didn’t “feel” native
3. Needs the web
4. 1-2-1 mapping of features
5. Devs hated the code
47. “Hey Gina, can we
move Tuesday’s
booking to 9am instead
of 10am?”
gearoid.io • @gearoidorourke Mobile Moments 2016
48. “Sure thing.
Just click below to
confirm the change.”
gearoid.io • @gearoidorourke Mobile Moments 2016
“Hey Gina, can we move
Tuesday’s booking to 9am
instead of 10am?”
gearoid.io • @gearoidorourke Mobile Moments 2016
49. “Sure thing.
Just click below to
confirm the change.”
gearoid.io • @gearoidorourke Mobile Moments 2016
“Hey Gina, can we move
Tuesday’s booking to 9am
instead of 10am?”
Your booking has been
rescheduled to 9am on
Tuesday — Hassle.com
50. Looking at existing
behaviours: enhance
and enable — don’t force
change for its own sake
gearoid.io • @gearoidorourke Mobile Moments 2016