Effective mobile applications prototyping with JavaScript
summary
Hybrid prototypes use JavaScript to validate ideas fast: Cordova + HTML is quickest for complex visualizations and reusing web code, while React Native yields more native-feel and better overall quality but demands learning new layout/styling, tying native modules (Bluetooth freezes reported), and extra build steps. Expo removes much setup pain for React Native. Expect to reuse business logic libraries, handle platform JS engines and webview inconsistencies, and meet app-store requirements about native feel and unused permissions.
AI-written summary · about
chapters (18)
- 0:00Start
- 2:05Prototype
- 6:20And what?
- 7:37Shape the Expectations
- 9:31Current Options
- 12:14JS Execution
- 17:28How We Benefit From Cordova
- 18:40How We Benefit From RN
- 21:10More Pain... (Short Story About Styling)
- 22:27Pain of Cordova
- 25:02Code Sharing for Views
- 25:49Penetrating Application Stores
- 27:37Prejudice
- 28:28Unpleasant Reality
- 30:28Is it THAT Bad?
- 31:08Get Rid of App
- 31:49Conclusions
- 32:07Thank You!
related talks
36mThe journey through the hybrid mobile apps with JS
23mCoding Mobile with the Pros
06mSuccessful rapid prototyping with React Native
52mWhy you should use React Native for your next mobile app
48mMobile Apps with JavaScript - There's More Than Web
27mBuilding high quality mobile apps with React Native
36mMobile applications with JavaScript
26mIntroduction to Cross‑Platform Development with React Native and Expo