How we built a mobile application backend with Django in 10 weeks
summary
A Django + DRF backend gets built in ten weeks for a mobile app: added mobile number to the user model, switched to token authentication via DRF and a passwordless package backed by an SMS provider, mocked endpoints for weekly mobile releases, and introduced a read‑only GraphQL feed to replace hitting seven to eight REST endpoints. Migrations and refactors work but cost time, documentation and common tools across teams matter, load testing forces larger dynos and autoscaling, and the app ships on schedule though the team is exhausted.
AI-written summary · about
chapters (7)
- 0:00Introduction and setup
- 4:12Planning and architecture
- 12:23Authentication and development
- 23:55Hackathons and GraphQL
- 27:35Scaling and model changes
- 38:19Launch and delivery
- 42:41Lessons learned
related talks
26mDjango at
28mThe promised Django Land; the tale of one team’s epic journey...
22mLearnt lessons in a big Django Project
31m"Notes on Over-Engineering: A Project Post-Mortem"
21mBuilding maintainable Django projects: the difficult teenage years
23mThree Django Apps in a Trenchcoat: Writing an event management website with not a lot of time
16mBrazil: How we are gaining space with Django
38mA Global Team Tackles World Problems with Django 🧭