A couple things I'd like to see addressed from the author:
- How is Active Admin's approach different?
- Why would someone choose Active Admin over RailsAdmin?
1. An administration interface must be good looking and easy to use. The interface is not for developers who understand the underlying data model, rather for operations staff who need to do their job and service our customers.
2. Administration of a production application is way more complex than a simple CRUD of database tables. Although editing data is necessary, most of the time operations staff are finding a resource and performing an action on it or looking up historical data.
3. An administration framework must be highly customizable. Active Admin makes it easy to add controller actions, sidebar elements, action buttons, dashboard widgets, custom forms, show screens and hook in to all resources via plugins.
* Disclaimer: I'm more familiar (and probably biased) with rails_admin
Also, it wasn't as nice as I would have wanted.
But this one looks really nice.