Avo beyond admin panels
I'ma self-taught developer on my journey to become a successful indie dev.
For more content follow me on Twitter @adrianthedev
Search for a command to run...
I'ma self-taught developer on my journey to become a successful indie dev.
For more content follow me on Twitter @adrianthedev
No comments yet. Be the first to comment.
I want to share my experience regarding AI-driven development.I know it's not a new and shiny thing, and it's been around for a while now, but some things should need some time to take it through its

I think it's important that the Ruby community knows what just happened in San Francisco last week. 400+ Rubyists got together and shared ideas and visions. They exchanged opinions and presented the past, present, and future of Ruby. I went to very ...

Tl;DR; We're taking a break with Friendly.rb. We had three beautiful editions, incredible fun, and learned so much in the process. This happening changed us, the hosts in ways we could not imagine. We're taking a break because things have happened in...

What do you need in your digital brain? That's how I think about Avo now. It's not some closeted admin panel where only five people dare to go because touching the data wrong might crash the app. It's the place where you invite your whole team to run...
Here's something that's been on my mind lately about the Rails ecosystem. For the past 10 years, there's been massive investment in dev tooling, especially for JavaScript and TypeScript companies. They take some of that funding and deploy it to marke...
Own it - A blog from Adrian Marin
24 posts
Sharing my lessons on becoming a thriving #indiedev.
🚀 Launching Avo into the world! - 🥑 A beautiful, easy-to-use Ruby on Rails admin panel framework
I've been marketing Avo as an admin panel framework for years. And it's a very good one, but I think it's time to make the distinction between a "thrown-together" admin panel that nobody really uses (because they're afraid of touching the data or they don't have test coverage) and robust, optimized, well-tested, and documented operational software.
I never bashed other solutions. I tried to learn from them. They were built in different times with different technology and probably different goals in mind.
Avo isn't this "glorified database browser" that only does basic CRUD. One thing our users and I noticed right away was that these labels—admin panel, internal tool, content management system, CRM—they all blend into this fully customizable digital brain of your product.
And that's what we're all about: providing the tools you need to build the infrastructure to run your company.
Tools that evolve with you from one person to a few hundred people, like some of our customers have. Tools that are battle-tested by multiple organizations at once. Tools that have the features you need before you need them. Tools that put your mind at ease and enable you to ship the more unique aspects of your app instead of boilerplate.
So I'm curious: where do you draw the line between "admin panel" and "operational software"? What are your pain points with internal tooling right now?