Archived from the Bravo community forum (2021–2026). Some answers may refer to older versions of Bravo.
Hello, dear community.
In the app I'm building, there are sections that need to receive data from the backend, so the loader on the full screen arrives before showing the page. It doesn't look really smooth to the user, as I've shown here. I found the walk-around with the skeleton state of the page. And it looks better.
The problem is that Bravo is counting skeleton screens as standalone screens, not as a state of one screen. So if I have 20 screens inside the app, where I need skeletons, I will have already 40 screens counted.
Pop-ups and modal screens are also counted as standalone screens.
My proposal is to don't count skeletons, pop-ups, and modals as screens inside the plan, but as a state of one screen that is connected to it. Inside Bravo Studio it can be organized as screen variants like in Zeplin.
1 reply
Bravo Teams, you have added a maximum number of pages to the application, but I subscribed before adding this limit
This is illegal to apply to the limit on my subscription
I subscribed to certain details, how can they be changed?
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