Download to read offline
Uploaded byVal Scholz
React Native - Why Designers should use React native. And everyone else too.
The document argues that designers and developers should use React Native due to its rapid prototyping capabilities, which are essential for success in mobile apps. It highlights the challenges associated with native and hybrid apps, such as slow development and deployment cycles, and emphasizes React Native's advantages, including instant reloads and code reusability across platforms. Additionally, it contrasts imperative and functional UI approaches, showcasing the benefits of React Native's design architecture.
React Native - Why Designers should use React native. And everyone else too.
- 1. Why designers should useReact Native. And everyone else too.
- 2. Val Scholz @valscholz CPO atChatGrape Founder Mingel; WeGrove Past Swat.io; Mindmeister
- 3. the true entrepreneuris a DOERnot a dreamerNolan Bushnell
- 4. Rapid prototyping is core tosuccess
- 5. Easy in web,but it sucks on mobile
- 6. Native Apps HybridApps 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
- 7.
- 8.
- 9. Slow deployment cycle OTAUpdates* *Apple said it’s ok
- 10. Separate platform teams Codere-use between Web, Android and iOS
- 11.
- 12.
- 13.
- 14.
- 15. Document Object Model VirtualDOM Next StatePrevious State Difference
- 16. Autoresizing vs Autolayout FlexboxLayout Flex Direction Justify Content Align Items
- 17.
- 18. Official React NativeWebsite https://facebook.github.io/react-native/ React Native Blog http://www.reactnative.com/