I’m leaving Bravo again.

***** and they don’t let us help build them components. Let the user create react components and add marketplace free and paid

Same here, I stopped using Bravo 1 year ago. I sometime come and check what’s new. One day I’ll come back but for now it’s more a prototyping tool than a real nocode thing.

@Robin C i gave them a chance 4 months ago again an payed plan and all.. but the final app was not a real life product even with xano paid plan

@Dany Klein “Pay for what it is now, not based on what it could be”

I am a bit afraid to be honest. The potential is huge that is a fact, but I feel like each nocode creating tool project needs to choose between :

• Having a lot of money and build something so good that people use it. (Very few nocode tool)

• Build the service with your community

I feel like Bravo doesn’t have that much money so…

@Robin C I think the problem is more they don’t have enough stuff for that they should open it to Devs to create their own components, simple things are missing like hide scroll bar on a view it’s one Option to adf with react native dumb exemple. They could be over everyone, but they don’t give 100% I think.
I would switch to adalo if they had custom fonts, because they are getting bigger and bigger

Build the service with the Community is missing here, look at the trello roadmap there is no Communication, from ready it goes back to planned

@Dany Klein Yes this is what I meant when I said “Build the service with your community”. Lower the price of the plans, take a fee on paid plugin.

@Toby Oliver the main problem is speed, download a normal app pages are loaded shown directly. Event adalo got it don’t the speed is just amazing ( that’s the only good point they have lol ) it’s fast ultra fast. Here even tab pages take 2s to load with paid xano. You documentation is good and the support too, but there is not engouh communication around the roadmap things go from ready to planned and so one and if we ask something no news. Build bravo with your community best advice.. What changes did you did for performance? Communicate with us explain it? From this server to aws or preload ui or what is it? Basic stuffs are making bravo bad that’s the point it’s not the missing calendar component but the lunch time the api speed and more why embeed a web component? We want build native? Open it like adalo a marketplace where dev’s can create there own bravo tags would love to have a talk

@Toby Oliver and the page limit is to small with all the loading pages. Why loading pages, just let us add a loading icon and it shows on the container where needs to be loaded on that screen, and it’s should be cached for the next them the app opens and only reload on change like swr from vercel does it. I’m a dev my self and i would love to know the magic behind bravo to help make it better hope it will be possible one day