Archived from the Bravo community forum (2021–2026). Some answers may refer to older versions of Bravo.
Is this possible? Use case:
During onboarding, user cannot tap "advance" until action is completed (For example, input field must be filled out before user can advance). Until then, button state shows disabled state.
I know there are "Error" states, but in many of the apps we build a button cannot be tapped/accessed/appear until a condition is met.
What's the best way to do this with Bravo? Just let me know if I'm missing something! I'm just diving in...
Thanks!
2 replies
Not sure about disabling but you can try using conditional visibility for elements.
You may have to work this from the backend and add a field or variable that returns a false Boolean value if the fields you need are empty and vise versa then bind the result to the visibility state of that button.
Thanks, Josh. That's an interesting idea. I wonder if there is a way to trigger an API call from a form once data has been entered. Does Bravo allow for that level of specificity? I'm new to it, but in the use case of a form, it'd need to do something like this:
If -> email input field contains text -> then -> display "enabled" button state.
To pull that off, we would need to trigger an API call once data is entered in the input form, and before the "Submit" action is taken.
This is fairly par for the course when we build native apps, so I'm trying to get an idea of what Bravo can/can't do as we explore using it (Before we get too far in only to realize it doesn't fit our needs).
Thanks!
Wrote something in this thread and want it removed? Request removal
Ask the community on Discord
This archive is read-only. New questions, office hours and product updates now happen in the Bravo Discord.
Join the Discord