Building for web and mobile in 2024
summary
Built a Rails-backed parent-school app called Flamingo as a hybrid plus PWA: three repositories (Rails plus iOS and Android shells) with business logic kept in Rails, five female engineers out of nine on the team, and a calendar shipped later. Native notifications use Firebase (no bills after six months); browsers required web push so the app adds a service worker with VAPID keys via pushpad/web_push and a push Stimulus controller. Hotwire (Turbo frames/streams) and the notice gem handle in‑app updates and realtime messaging, and the hybrid approach proves deploy‑fast and functional.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:51Parenting and school apps
- 4:59Progressive vs hybrid apps
- 8:56Flamingo app features
- 10:00Unexpected browser notifications
- 12:52Web push notifications setup
- 14:43Hotwire in hybrid apps
- 15:45Early app publishing tips
- 17:32Rails development speed
- 18:57Future of Rails on mobile
- 20:44Hybrid apps user experience
- 21:49Conclusion and resources
related talks
38mLet's build a mobile app
33mBuilding apps that are on FIRE
28mThe Future of: PWAs on Rails
03h 13mBuild your first mobile & desktop app as a Progressive Web Application
36mRuby Runway Finals
44mAchieving next-level code between Flutter and the Mobile Web
41mWeb, Native iOS and Native Android with one Ember js App
36mAngular+Ionic으로 멀티플랫폼 PWA 개발하기
