The "Why" Behind Hyperdjango

I’ve always had a love-hate relationship with building reactive frontends in Django. On one hand, Django offers the best backend tooling out there. On the other, the frontend experience has always felt… lacking.

For a long time, the only real options were to split the app into a decoupled SPA using DRF or Django Ninja , or go the HTMX route.

I really liked HTMX at first, but the more I built with it, the more I ran into the "boilerplate wall." I found myself writing entire views and heaps of backend code just to toggle a UI element or handle a tiny state change. Plus, integrating modern JS libraries was a headache. Django Vite exists, sure, but it comes with its own set of implementation hurdles.

I started experimenting with ways to solve this.…