3 ms·
When I was skimming your homepage I was thinking “I really wish this was built on Hotwire” and then I saw that it was. That architecture choice makes me think
by tomhallett 4y ago
When I was skimming your homepage I was thinking “I really wish this was built on Hotwire” and then I saw that it was. That architecture choice makes me think your bold claims might actually pan out, :).
The fact that the ways to customize/escape are “vanilla rails” and avo is deployed within my app as an engine, make this very very interesting.
As compared to:
* something like retool which is deployed (ie hosted) as an additional layer which calls an api my app exposes. Great for huge organizations, but overkill for a small team (similar to SPA vs Hotwire tradeoff)
* activeadmin where escaping the standard path is extremely hard. Not to mention it’s built on gems which are no longer in favor (inherited resources, etc)
* administrate which I really enjoyed, but felt like the support/roadmap was more of a side project vs an “open core/commercial offering”
- adrianthedev 4y agoThank 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://avo.cool/chat https://twitter.com/adrianthedev https://twitter.com/adrianthedev