[samwillis]

The Django admin is a superpower, it's a x10 productivity multiplayer at the beginning of (or even far to far into) a project.

However, I also dislike so much of it. The hacks I have used to contort it to do what I want I would be embarrassed for another developer to see...

Former Django fellow Carlton is working on a nice toolkit called "Neapolitan", it's early stage, but is designed to enable building CRUD views very quickly. There is a good chance that in time it, or a layer on top of it, will become the perfect successor to the Admin.

https://github.com/carltongibson/neapolitan

[raphael_kimmig]

We have been working on something that sounds similar. It ain’t perfect yet, but we are using it quite a bit already.

https://github.com/django-beam/django-beam

[appliku]

The common wisdom was always not to rely on it for any of your users (for far too long) and build something separate as soon as possible. But i must admit that lately it got much much better. I only recently discovered that you can have multiple admins with it's own admin models. So way less hacks.

I actually want to try build an app just to see how far I can push it with Django admin and see how hacks it will end up.

[pedrovhb]

I haven't seen it used by users, but it's amazing for non-technical staff (PMs, support to some extent, etc). They can inspect and modify the database while making sure everything still validates, run batch jobs, actions, etc and it's all very low effort to implement. No need to fetch a dev to debug an issue with data or understand whether the cron job run or why it may have failed. It helps with understanding a platform's internals, which improves understanding and communication all around.