Why designers should
use React Native.
And everyone else too.
Val Scholz
@valscholz
CPO at ChatGrape
Founder
Mingel; WeGrove
Past
Swat.io; Mindmeister
the true entrepreneur is a
DOERnot a dreamerNolan Bushnell
Rapid
prototyping
is core to success
Easy in web, but
it sucks on mobile
Native Apps Hybrid Apps
Slow development cycle
Slow deployment cycle
Separate platform teams
Poor performance
Non-native feel
Hard to debug
Stateful, muteable UI
Hard to manage complexity
Hard to verify correctness
Hard to maintain / re-use
React Native
Slow development cycle
INSTANT RELOAD
Slow deployment cycle
OTA Updates*
*Apple said it’s ok
Separate platform teams
Code re-use between
Web, Android and iOS
Poor performance
Native UI Views
Imperative UI
Functional UI
Imperative UI
9 Transitions
Functional UI
3 States
Document Object Model
Virtual DOM
Next StatePrevious State Difference
Autoresizing vs Autolayout
Flexbox Layout
Flex Direction Justify Content Align Items
+ =
Example
Official React Native Website
https://facebook.github.io/react-native/
React Native Blog
http://www.reactnative.com/
React Native - Why Designers should use React native. And everyone else too.

React Native - Why Designers should use React native. And everyone else too.