Avo 4 - Plan, Feedback and Ideas #3764
Replies: 5 comments 11 replies
-
All great ideas... But of all these ideas, I think REST API and Workflows might be the most revolutionary as they open up infinite more possibilities of what you can build with Avo. The ability to quickly turn your resource adapters and actions into an API would reduce the cost of app development significantly, particularly for those apps that offer some sort of API or need an internal API for the mobile app counterpart. |
Beta Was this translation helpful? Give feedback.
-
Not sure if we have this now or not.
|
Beta Was this translation helpful? Give feedback.
-
Advanced
|
Beta Was this translation helpful? Give feedback.
-
Must have feature: Dependent field
|
Beta Was this translation helpful? Give feedback.
-
It would be great to have a better support for delegated type. Maybe part of this could come from the nested records feature that is being currently build. ExampleIf we take the the examples from the doc it would be nice to be able to go to an |
Beta Was this translation helpful? Give feedback.
-
Let's start a conversation around what Avo 4 can be.
A few things we were thinking about:
Committed on doing
Maybe
Avo::Resources::Course::Link
) ?Not doing right now
Workflows?Might not do it. Sounds like a big feature in itself. Maybe it's better to integrate with n8n or zapier?Board view
Roadmap (view)
Beta Was this translation helpful? Give feedback.
All reactions