
Building Art Way: why I picked django-ninja over DRF in 2026
Context Art Way is a booking SaaS I built solo for a creative studio — dancers, musicians, and event organizers renting rehearsal rooms by the hour. The domain is narrow: rooms, bookings, users, notifications. Scale is modest — dozens of bookings a week, a single VPS running Django + Celery + Postgres behind nginx. Nothing that needs sharding or a gRPC mesh. What did matter: the frontend is Next.js 15 with React 19 and TypeScript, consuming the API from both client and server components. A typed frontend changes the economics of your API design. Type drift between backend response shapes and frontend interfaces is a constant source of bugs, and in a one-person project there’s no code-review safety net to catch it. OpenAPI wasn’t optional — I needed a machine-readable contract that the frontend could consume. And boilerplate is the enemy of a solo developer: every file I write to wire up DRF is a file I can’t spend on actual features. ...

