avo
Release notes
๐ Bug Fixes
- fix: actions paths to /avo are broken for custom root_path config @adrianthedev (#391)
By industry
By use case
You're building two apps
Build an admin panel
Rewrite your old admin
Build an ATS
Build a back office
Build a CMS
Build a control panel
Build a CRM
Build a customer support app
Build a dashboard
Build an EHR/EMR app
Build an ERP
Build internal tools
Build an inventory app
Build a newsletter system
Build a task management system
Stay in the loop
Documentation
Keep those skills sharp
Supporting the community
By industry
By use case
You're building two apps
Build an admin panel
Rewrite your old admin
Build an ATS
Build a back office
Build a CMS
Build a control panel
Build a CRM
Build a customer support app
Build a dashboard
Build an EHR/EMR app
Build an ERP
Build internal tools
Build an inventory app
Build a newsletter system
Build a task management system
Stay in the loop
Documentation
Keep those skills sharp
Supporting the community
A (HUGE!) side benefit we've seen in implementing Avo has been surfacing of platform issues - missing associations, opportunities for delegators and collaborators, etc. Our underlying models and interactions have become much more robust as we've implemented Avo as we can quickly identify relationships and optimizations without doing full-fledged, user-facing feature work.
David Lormor
CTO, Wyndy