React Native and PWA: A Tale of Two Architectures
summary
A medication tracker for hemophilia models drug decay and records manual infusions with a donut chart showing current protection; condition affects about 1 in 20,000 and the drug wears off ~48 hours, missing doses is life‑threatening and treatment costs ~€10,000/week in Germany. Implementation uses React Native with a partial PWA prototype; PWAs win on size and load (Tinder cuts load to ~4.7s and Android binary size by 90%, Uber PWA = 50KB), while React Native enables HealthKit integration and geofencing but breaks easily with OS changes (demo fails on iOS13).
AI-written summary · about
chapters (13)
- 0:00Introduction and speaker
- 1:03Building mobile experiences
- 2:32Medical app problem
- 6:44Why JavaScript and choices
- 8:10Progressive web apps explained
- 11:01PWA trade-offs
- 13:49Apple’s PWA stance
- 14:12React Native overview
- 16:20React Native pros
- 17:22React Native cons
- 18:48Choosing between PWA and React Native
- 20:36Platform complexity
- 21:20Solving real problems
related talks
32mA Tale of Two Architectures
59mProgressive React Apps
32mProgressive Web Apps
05mThe Great Convergence with React
27mReact Native at Uber Eats - handling scale and complexity
06mLightning talk from Ken Wheeler
36mThe journey through the hybrid mobile apps with JS
52mCreating Mobile Apps Drupal and React Native