The State of Django 2025 blog post is out offering a curated look at the full survey results. There is also a Django Chat episode available talking with @jeff and @carltongibson about the results.
The Forum seems as good a place as any for public discussion around the results, what was surprising, and what we should be sure to ask next year.
It is likely that the 2026 Survey will come out in January/February next year, aiming for a faster turnaround (ideally June), so any feedback you have is welcome!
4 Likes
Thanks for sharing!
One thing I noticed is that the response to “What do you use Django for?” has seen a shrink in “REST API using DRF” (61% from 2023 to 51% in 2025 survey results). This seems to match a decrease in DRF usage (60% back in 2022 and 49% in 2025) but there is also an increase in usage of Django Ninja (up to 10% of in 2025).
I can’t remember the exact wording of this question, but it may be that using a reference to a particular package is keeping respondents from responding in the affirmative that they are building APIs. Would it would be worthwhile to change the language of the responses to be tooling agnostic?
- Full-stack development
- API development
- Other
Along that line there have been a lot of conversations and questions regarding API development since DjangoCon US. Many of those conversations are around what Django developers are doing and need regarding the developer experience when building an API-first application. It feels like we are mostly bringing personal experience and anecdotal evidence to the conversation without having much concrete reference. I’m curious if the Django Survey is a viable way to gain that concrete reference. Asking questions about what API tooling developers are using now (Ninja vs DRF vs home grown), what serialization libraries they are using in production (Pydantic, DRF Serializers, cattrs, msgspec, etc), if and how they are exposing API documentation, if their audience is an internal team/their own SPA or if they are building a public API, etc. It is possible this line of questioning doesn’t fit into the vision of the Django Survey. However, it seems like a conversation that the community is excited to have, and I think starting from a place of knowledge would be super helpful.
2 Likes