When we first introduced Pale Blue Spring Admin, it was a bit of a tease. You could look, but you couldn't touch. It provided a read-only window into your JPA entities, useful for a quick health check, but not exactly a replacement for the "Swiss Army Knife" experience of Django Admin.
Our goal has always been simple: we love Kotlin and the Spring Boot ecosystem, but we missed the "it just works" productivity of Python/Django.
With the latest release, we are happy to say we believe we have come closer to bridging that gap.
The missing CRUD
The headline feature is simple: Editing is here. You can now create, update, and delete entities directly from the UI. No more jumping into a database console or writing throwaway REST endpoints just to fix a typo in a production row. The UI automatically generates the appropriate forms based on your JPA annotations, keeping the "zero-config" promise alive.
Add, edit, update, delete now supported
Beyond the grid: Custom UI snippets
One of the main reasons people eventually outgrow auto-generated admins is the "walled garden" effect. You need a custom button to trigger a background job, or a specific chart to visualize data, and suddenly, the library is more of a hurdle than a help.
To solve this, we’ve added Custom UI Snippets. You can now define your own UI elements to extend the portal. Whether it's a specialized dashboard widget or a custom action button, you can inject your own logic and components without fighting the library.
Custom UI snippet at the bottom of the admin portal
Closing the gap
With these additions, we believe we are very close to feature parity with the core functionality of Django Admin.
We want to write backend code in our favorite language, Kotlin, with the same velocity as the Python ecosystem. We’re building this for ourselves, but we hope it makes your life easier too.
Give it a spin: Pale Blue Spring Admin
Try it out, and let us know what you think.
Happy coding!
Top comments (0)