RailsAdmin VS Avo

Like most things, it's probably a combination of things. The Django Admin existed before Django publicly existed. That meant that once anyone started using Django they knew that they should constrain their use of Django in certain ways so that the Django Admin would work with their usage. Features that would be added to Django would be built with the Django Admin in mind. Many tools like Flask or FastAPI don't... - Source: Hacker News / 6 months ago

We briefly considered migrating to a full-grown Rails admin interface, such as ActiveAdmin, RailsAdmin, Administrate or Avo. We especially liked Avo which is built on a very modern stack similar to ours (Tailwind + Hotwire + ViewComponents). In the end, we didn’t go this route as we found some of the options a bit too restrictive (even though Avo is very flexible) and we did not feel like trying to amend it to our... - Source: dev.to / almost 2 years ago

Https://github.com/railsadminteam/rails_admin Is very popular and I find it very easy to use. Source: over 2 years ago

It's really helpful to have a way to track what's going on with your application in production, things like: number of user sign ups, status of user accounts, number of X new database entries etc. Out of the box dashboards like Rails Admin are great but only go so far, eventually you will want significant customizations. - Source: dev.to / over 2 years ago

I'm working on a rails project with rails_admin and multiple models. There are several people working on the backend and I want to remove the ability to edit some of the records which have a imported boolean set to true. This records should just be readable in rails_admin. Source: over 2 years ago

Avo — Simplified analytics release workflow. Single-source-of-truth tracking plan, type safe analytics tracking library, in-app debuggers, data observability to catch all data issues before you release. Free for 2 workspace members and 1 hour data observability lookback. - Source: dev.to / almost 3 years ago