Live data from Hacker News

Show HN: Avo – Build Ruby on Rails apps faster

avohq.io

141–150 of 171 posts

Re: Show HN: Avo – Build Ruby on Rails apps faster

#141

It's great to see folks building frameworks on top of frameworks. I've started to look into full stack starter-kit frameworks that goes beyond the admin panel and here's what's out there these days. * https://bullettrain.co - Opensource, $0/year * https://jumpstartrails.com - Opencore, $249/year * https://www.bootrails.com - Closed source, ~$83/year I've even started to piece on together for my own projects at https:…

Years ago there was a site called prelang that tried to create a framework framework. It was incredibly cool, but I think it became abandoned.

https://www.producthunt.com/products/prelang#prelang

previously on HN: https://news.ycombinator.com/item?id=7985162

Re: Show HN: Avo – Build Ruby on Rails apps faster

#142
post #10

Hey HN, I'm Adrian, an indie developer and creator of Avo. For more than ten years, I built countless admin panels and back-offices for all types of apps. After a while, you start to notice patterns and extract functionality away to make the job easier. I took those patterns and applied them to Avo. Now, in just an hour, a developer can build production-ready applications that with traditional coding techniques take…

Why did you call it Avo? I'm curious because I know of at least 4 SaaS companies called Avo.

I was hopping it was Aussie slang... Like Build a rails app in one avo..

Re: Show HN: Avo – Build Ruby on Rails apps faster

#143

this is very very cool. Any plans of making this for the js ecosystem ? Unfortunately not all of us are on ruby...but everyone is on js. Would totally love something like this on React/Next.

Haha. Funny you should mention that. Me, together with my brother, built basetool, which should have been Avo but for TypeScript (framework agnostic). You give it a database URL and it will build the admin panel for you. Today was the day that I decided to sunset it, but you could try to use it with docker or compile it from source. https://basetool.io https://github.com/basetool-io/basetool

why dont you put it up on codecanyon as a theme sale ? you can still keep it open source...but this is quite good a tool. maybe you will discover the niche ?

Re: Show HN: Avo – Build Ruby on Rails apps faster

#144
post #137

@adrianthedev I gave it an hour and here are my thoughts. Generators for resources should be smarter and look a models attributes and type_for_attribute and add all the fields for me. Things like enums should be easier than needed to also specify them as select options. You also dont have any datetime field types. (edit it appears you do but the docs dont list them on the https://docs.avohq.io/1.0/field-options.html…

Thank you for trying it. I mean it! That's all I want :)

> Generators for resources should be smarter and look a models attributes and type_for_attribute and add all the fields for me. Things like enums should be easier than needed to also specify them as select options.

> The suggested generators for namespaced models ```bin/rails generate avo:resource Cms::Page``` dont seam to work

I agree. The generators could be smarter. Maybe even generate a resource when you generate a model. There's a really old PR started a while back. https://github.com/avo-hq/avo/pull/182

> You also dont have any datetime field types. (edit it appears you do but the docs dont list them on the https://docs.avohq.io/1.0/field-options.html)

We actually do have them. Date and DateTime with a wonderful date picker (flatpickr). Not sure how you landed on that page (it's for version 1.0). The correct link below. https://docs.avohq.io/2.0/fields.html

> All attributes should also be default sortable.

TBH, I avoided that by default. I'm not sure you'd like the user to sort by anything from the start, but maybe that's just a thing of preference.

> Also using the models schema should give you default filtering. Strings should be loose, numbers/enums should be exact, datetime should be ranged.

Yes. I agree that an advanced filtering system is helpful and needed. The current filtering system is powerful too. You can make complex queries (query by multiple columns) from one toggle/dropdown, instead of adding multiple filters to get sthe same result.

Thank you for this thorough review. Being a solo developer I have a lot on my plate. I'm talking development and others (marketing, sales, copywriting, etc.). When doing development I have to choose what's important and what can wait. That's why the generators are not that smart. I have a GitHub discussion started around the advanced filtering, but there's not that much ctivity around it. I'd love to bring it in soon. https://github.com/avo-hq/avo/discussions/739

Until that point I'm focusing on bringing features that help the users and fix real problems for them. That was and is my main concern going forward.

I'm sorry you think it underdelivers. I respect your comment, and I'd love to talk to you and see what you think really is missing. Except for the filters, all the other concerns are not really user-centered.

https://calendly.com/adrianthedev

Thank you!

Re: Show HN: Avo – Build Ruby on Rails apps faster

#145

Earlier quoted context omitted.

The original name was project Avocado, but I didn't find any good domain names and social media handles. I agree the naming could have been better.

Add an accent and you get grandparent (avó)

I have a hard time with english (mostly US) speaking people that pronounce it "aivo". It's actually like "avocado" "avo".

Re: Show HN: Avo – Build Ruby on Rails apps faster

#146

Hey HN, I'm Adrian, an indie developer and creator of Avo. For more than ten years, I built countless admin panels and back-offices for all types of apps. After a while, you start to notice patterns and extract functionality away to make the job easier. I took those patterns and applied them to Avo. Now, in just an hour, a developer can build production-ready applications that with traditional coding techniques take…

Have you migrated any medium or big-size ActiveAdmin projects to Avo? If so, how much work would you say it takes? UI looks great by the way.

I haven't done large project migrations but I spoke with customers that have and they said it's not that difficult. Most sat down and "did it over a weekend".

Some did migrations from their own custom admin panels "over a weekend". It's kind of crazy how easy it is to get started.

Re: Show HN: Avo – Build Ruby on Rails apps faster

#147

It's great to see folks building frameworks on top of frameworks. I've started to look into full stack starter-kit frameworks that goes beyond the admin panel and here's what's out there these days. * https://bullettrain.co - Opensource, $0/year * https://jumpstartrails.com - Opencore, $249/year * https://www.bootrails.com - Closed source, ~$83/year I've even started to piece on together for my own projects at https:…

I think this guys are doing something similar but for the JS stack - https://twitter.com/flatlogic

Re: Show HN: Avo – Build Ruby on Rails apps faster

#148

It's great to see folks building frameworks on top of frameworks. I've started to look into full stack starter-kit frameworks that goes beyond the admin panel and here's what's out there these days. * https://bullettrain.co - Opensource, $0/year * https://jumpstartrails.com - Opencore, $249/year * https://www.bootrails.com - Closed source, ~$83/year I've even started to piece on together for my own projects at https:…

There is now also mine in alpha https://businessclasskit.com/ focused on Rails defaults (Active Storage, Minitest, ...) with Paddle (important for Europeans to skip on dealing with EU taxes).

Re: Show HN: Avo – Build Ruby on Rails apps faster

#149

This looks really good. So a bit of insight from a dinosaur, I'm one of those guys who is a diehard ActiveAdmin user. I've come and gone through the other admin interfaces and nothing is as fast as ActiveAdmin when it comes to the basics. Important note is ActiveAdmin is for internal/staff only. Benefits - It doesn't need to be pretty. It simply needs to function. - Layout actually should be allowed to be information…

Thank you for this thorough description! I'll keep an eye out for the shortcomings so they don't creep into Avo.

I'd love it if you'd try Avo for a project (not just for 30 minutes) and compare the two. I think having an experienced developer on a real project would yield a real comparison.

Post reply on HN