HNHacker News
TopNewBestAskShowJobs

adrianthedev

453 karma · joined December 28, 2016

Product-Minded Software Engineer. Author of https://avo.cool and https://basetool.io, previously at Adore Me, Two Tap and Acquia

Check out my work: https://avo.cool - Admin panel framework for Ruby on Rails that saves your time. Move 10x faster without writing boilerplate code https://basetool.io - View and manage all your data in one place like a pro

submissionscomments
adrianthedev··on Show HN: Avo – Build Ruby on Rails apps faster
I believe that no tool is perfect. Not even Rails. We reach for other gems and sometimes do things not "the Rails way" and we get the job done.

And there's a fallacy there. We don't go saying "Rails doesn't do everything I need it to do, so I'd rather spend more time to write my framework from scratch". But we're (and I'm including myself too) very quick to say things like that about certain tools just because "it's never been done before", "Nobody uses an off-the-shelf package to build their app on", "I'll hit a ceiling with it...", and so on.

Yes, Avo isn't perfect, and yes, Avo isn't right for any kind of project. There are some that are more suited and some that aren't. Sometimes you might hit a "ceiling" with Avo, but I baked in a ton of "escape hatches" (add own content on multiple levels, override views, override controllers, multiple ways of interacting with the data, Stimulus JS). Using these "escape hatches" (I gotta stop using that term), will help you get the job done.

This message is not fingepointing towards you or anyone else, and I respect everyone's way of doing things, but we should take some time and reflect on that. We don't go and build linuxes, nginxes, pumas, railses and other pieces of tooling everytime beacause we might get stuck at one point. We make it work. Same should apply with pieces of software like Avo.

Thank you for the message!

adrianthedev··on Show HN: Avo – Build Ruby on Rails apps faster
The Active Admin to Avo converter sounds like a good idea, and I'll wait until I hear about this request from more users. I use my time where the users need me to use it.

Oh, yeah. No offense taken. Thank you for the compliment!

adrianthedev··on Show HN: Avo – Build Ruby on Rails apps faster
The more the merrier! I haven't tried it yet but I'm stoked there's movement around it. I love the "Rails defaults" convention. I do the same with Avo.

One problem I had with Paddle is that they haven't accepted me in their program. It would be cool if you'd be able to create some kind of partnership and fasttrack that process somehow.

Good luck!

adrianthedev··on Show HN: Avo – Build Ruby on Rails apps faster
As a disclaimer, I've done PHP (WP, Laravel, custom), Javascript (Node, JS, TS, back-end, front-end, full-stack) and Ruby, so I'm speaking from my experience.
adrianthedev··on Show HN: Avo – Build Ruby on Rails apps faster
I sometimes think Rails is one of the best kept dev productivity secrets out there.

Let the doubters doubt...

adrianthedev··on Show HN: Avo – Build Ruby on Rails apps faster
Yes, it's nice to see the ecosystem go green again. I love Rails and I want it to flourish.

I think bullettrain.co is open core as well. They haven't announce the pricing for the subscriptions packages yet, but I can't wait to see what they come out with.

Regarding "settled libraries", I am all for that. I'd rather have conventions all over and know that devise is on every app, but the truth is that each app is different and has different requirements. That's why Avo is deisgned to work with multiple libaries.

Good luck with monolith and let me know if I can help. I think having Avo in monolith and other similar projects would contribute on that "settled libraries" convention.

adrianthedev··on Show HN: Avo – Build Ruby on Rails apps faster
Yes, they intersect in features.

The barrier that I'm trying to break and push through is that the result is not a hidden away admin panel where only a small number of core team members go to update some record. The result is a beautiful consumer-ready interface that you give to your user.

Avo is your app. Not a part of your app. Avo is the UI your users see when they go and interact with it.

Thank you for the message.

adrianthedev··on Show HN: Avo – Build Ruby on Rails apps faster
The real-time building of the app was an hour and 10 minutes. I posted a screenshot with the recording below. That recording contains also some setup on my part, it's not just actual coding on the app.

https://share.cleanshot.com/hPUskT

The 10x speed-ups were actually data-entry which definitely nobody wants to see in real-time or would benefit from.

The 2x-3x speed-ups were for the generators and slow typing speeds.

I know the tendency is to exaggerate things, but I'm not for that. I like honesty because it's not complicated. When one lies they have to keep that in memory for the next time :P

So yeah, the video is sped up, but the message is correct.

adrianthedev··on Show HN: Avo – Build Ruby on Rails apps faster
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.

adrianthedev··on Show HN: Avo – Build Ruby on Rails apps faster
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.

adrianthedev··on Show HN: Avo – Build Ruby on Rails apps faster
I have a hard time with english (mostly US) speaking people that pronounce it "aivo". It's actually like "avocado" "avo".
adrianthedev··on Show HN: Avo – Build Ruby on Rails apps faster
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!

adrianthedev··on Show HN: Avo – Build Ruby on Rails apps faster
Yeah, my bad there. Jumpstart ships with Administrate, not rails admin.

I'm humbled to have built something that could ship with Jumpstart. Thank you for the kind words!

adrianthedev··on Show HN: Avo – Build Ruby on Rails apps faster
Yes, they do intersect in some areas as you can build CRUD UIs with both. Avo takes it further to give it a nicely designed UI, all the "missing" features like extending the interface, adding custom content, supporting all associations thoroughly and more.

I think of it like the next iteration of these kinds of tools.

Have you built something using administrate?

adrianthedev··on Show HN: Avo – Build Ruby on Rails apps faster
Ok. Got it! It's mostly about the phrasing. Pushed changes now.

"It’s better for the customer and for jumpstart." It's true.

adrianthedev··on Show HN: Avo – Build Ruby on Rails apps faster
I haven't used motor admin extensively so I couldn't speak about it's features very precise. It seems to me that motor admin is like a giving a power tool to your end-users. It's empowering the citizen-developer. They can make their own admin panel. You might end up with a good product, but it also can go the other way and build something not that good.

With Avo, you, the developer, draw the lines on what the user can and can't do. This way you make sure you give them the best experience.

adrianthedev··on Show HN: Avo – Build Ruby on Rails apps faster
Yes, sure.

They are tools that work together nicely. I use both on our infrastructure websites (https://avohq.io). Jumpstart is an amazing starter app that gives you accounts, billing, notifications, and others, and with Avo you can take over and build your admin panel/back-office fast!

I've spoken with Chris Oliver and started work on adding Avo to Jumpstart and to have it as an alternative to rails_admin.

adrianthedev··on Show HN: Avo – Build Ruby on Rails apps faster
I'd say that the classic direct competition are Active Admin, Administrate, rails admin. They are the OG admin panel builders in the Rails world. They focus a lot on building just classic CRUD admin panels.

I focused on making Avo a whole app development platform. It's not that hidden place where just a few team members go to update some records, but the actual UI that you give to your users.

I'll make sure to create an "alternatives" page with competitors.

adrianthedev··on Show HN: Avo – Build Ruby on Rails apps faster
Thanks for the kind words!

Avo is built using Hotwire (Turbo and StimulusJS) so no fancy framework (React, vue, svelte) under the hood. We love Stimulus and goes very well with Rails development.

That beign said, Avo supports adding your own custom content (erb templates) and your own asset pipeline (webpacker, sprockets, or something else), so in theory you could inject React or Vue sprinkles here and there.

adrianthedev··on Show HN: Avo – Build Ruby on Rails apps faster
I wouldn't know. I'm not that connected with the Python ecosystem. Maybe someone else can shed light. I only know about Django Admin.
adrianthedev··on Show HN: Avo – Build Ruby on Rails apps faster
Yeah, for sure! This post, or Avo's existence is not about bashing other tools.

Each project has it's own requirements and budget.

Thank you for your message!

adrianthedev··on Show HN: Avo – Build Ruby on Rails apps faster
> "Developing with plain Rails and a minimum of gems is linearly difficult while developing with a set of DSL/generators like Avo can lead to a complexity spike from 1 to 11 in no time. And the worst thing — at a random stage of development"

I agree 100% with your statement! Really!

Thank you!

adrianthedev··on Show HN: Avo – Build Ruby on Rails apps faster
Haha. You're trying to stir sh*t up.
adrianthedev··on Show HN: Avo – Build Ruby on Rails apps faster
Yes brother! I remember the days when I was building "an internal admin for the agency". Something to have for all apps and customers.

We'd build it for customer 1, and then for customer 2 we'd add some features and change some. Same for customer 3, 4, 5, 6, 7. After a few years we ended up with 10 different apps that should be the same. No documentation, sometimes the developer that worked on the app is no longer with the company, a real mess.

This way, it would be like using Rails. Documentation, release, maintenance, the whole shebang!

Thanks for sharing!

adrianthedev··on Show HN: Avo – Build Ruby on Rails apps faster
Thank you for the kind analysis! I see you understand the product very well from the start! Yes, it's built with the knowledge of past projects you mentioned above and is deisgned to be very easily "escaped from". I know that "escaped from" might sound like you're trapped, but the experience is not that. Avo works with you to build the app you want.

Looking forward to see what you're going to build, and get in touch with me on Discord or Twitter.

https://avo.cool/chat

https://twitter.com/adrianthedev

adrianthedev··on Show HN: Avo – Build Ruby on Rails apps faster
Do you think my branding is similar to avo.app?
adrianthedev··on Show HN: Avo – Build Ruby on Rails apps faster
I would say that the Community version (free) covers most of what Active Admin does. The search is paid with Avo (and included in AA).

The Pro users are those who need to build upon Avo. They need custom content (fields, resource tools, custom pages), and they need to make it look the same as the rest of the app. Avo provides view components that help with that. This way you create a seamless UI for your users.

I think of Avo as more than just and admin panel framework (although power tool sounds great), but the place where you build your app. It becomes the app your users see.

Regarding API based apps, yeah, that's something I'd loke to support soon. Offer HTTP adapters where you coudl hook in your Stripe/Shopify/Intercom/Custom API endpoints.

Regarding complexity, I tried to cram as much as I could (whenever I push out a new feature, I add it) to the demo site[0].

One of the biggest apps I've seen has about 41 resources, 431 fields, and quite some complexity because it's a multi tenancy app that serves three marketplace platforms. There's a lot of complex scoping applied to the data to match the accounts and views.

But, yeah, I'd love to see an app that size. I think the project is still young (about two years. version 2.0 three months old) and these kinds of projects tend to get built out with time. I can't imagine there are a lot of teams with an app that size you mentioned that are in a hurry to rip out everything they have to replace it with Avo (or any other package or app) in such a short time. Even our customers above are slowly switching from their homegrown admin panel to Avo.

Right now, the UI customization wasn't our main concern. I do want it to look amazing so I work a lot (alongside the designer) to keep it looking excellent. This being Rails, you can always override the partials and view components to add your own and tweak Avo's. The first iteration of UI customization will be to enable the developer to change the colors of the UI.

Regarding general customization, you can already plug in Avo on multiple levels. One can add new fields, sections on resource pages, totally new custom pages, etc.

Avo is ready for customization complexity.

[0] https://avodemo.herokuapp.com/

adrianthedev··on Show HN: Avo – Build Ruby on Rails apps faster
Oh, I see what you mean. What kind of "gigs" they get. "Starters" or "continuers" (maintenance).

Gotcha! Personally I started a lot of projects. Probably more than 50%. And the money were good, but not as good as doing maintenance for a big company with a big product.

adrianthedev··on Show HN: Avo – Build Ruby on Rails apps faster
Well... Avo's pricing is exacty like Jumpstart's (except the $750 for unlimited). So pay $250, get Avo (or Jumpstart) with a year of updates. When you stop paying, you keep what you have until that point and no more updates. Isn't that the same? Am I missing something?

Also, you do make a point regarding agencies "sign a client up for a bunch of services". I'll try and experiment with that. Thanks for the nudge!

adrianthedev··on Show HN: Avo – Build Ruby on Rails apps faster
Oh darn. I forgot about the demo site to beef up the hosting for this post. I'll do that this week. I'll probably move it to a separate instance.

Yes, it's hosted in the US.

Thank you for that and unploy. I'll have a look.

← PreviousPage 2 of 5Next →