A Tale of Two Architectures
summary
Built a personal dosing app for hemophilia that shows a donut chart and models drug half‑life, implemented with React Native plus Apollo/GraphQL, demoing a fiddly keyboard‑avoidance bug that finally works; compares that to a progressive web app which is smaller and easier to ship — cites 66.7% of developers use JavaScript, Tinder cutting load from 11.91s to 4.69s, Pinterest gaining 60% engagement and Uber’s 50KB core — chooses native for HealthKit integration and on‑device control.
AI-written summary · about
chapters (10)
- 0:00Start
- 6:49Declarative Ui
- 13:22Progressive Web App
- 14:35Uber
- 16:25Pwa Checklist
- 17:56Downsides to Pwas
- 19:48React Native
- 21:54React Native Dom
- 23:32Cons
- 30:05Issues in Terms of Browser Compatibility with Pwas and Mobile
related talks
22mReact Native and PWA: A Tale of Two Architectures
29mLessons from Using Bleeding Edge Tech in a Startup
27mBuilding high quality mobile apps with React Native
01h 01mReact Native: A Better Way to Do Mobile
39mPerformance issues: the usual suspects
25mGoing Native
20mDissolving Boundaries: The Fusion of React app and Native Apps!
32mPractical Performance Tips Building Progressive Web Apps