Context
"Delivering mobile experiences that match our users expectations"
Agenda
- development stack history at Lifely
- React
- React Native
- Demo & Code
development stack history at Lifely
"From native to web and back again"
Frankwatching app
(native iOS)
Leefplezier
(cordova/ionic)
Leefplezier
(cordova/angular)
Part-up
(cordova/react)
StartDashboard
(reactnative/meteor)
HvA
(reactnative)
React (web!)
- javascript framework
- developed and maintained by Facebook
- created because of "slow dom rendering"
- modularity / single responsibility principle
- top down data flow
- declarative state of components
React Native (mobile!)
- react paradigm with native components instead of Webview
- native navigation patterns for both iOS and Android
- modularity / single responsibility principle (again)
- render predictability
- community support
👎
- "sdk feature delay"
- specific interactions e.g. shared element transitions
- single javascript thread
- plugin/bridge dependency
- patents/uncertainty
👍
- 1 codebase
- 1 language expertise
- 1 QA (business logic)
- rich plugin/bridge ecosystem
- hot code reload
Hamvraag
"Does it compare to two native apps?"
"We don't mind designing within boundaries"
Demo
(nativeness navigatie)
Demo
(react component structure & styling)