Worried about this platform

I think you (we) should be worried. 

Paradoxically Bravo Studio allow a lot of solo preneur to reach new levels of efficiency but it seems to be Bravo is a solo venture or is lacking funding, drive or revenue that gives you (us) the feeling it is dying.

Just do it, the more you will think the more you will be afar from your dream to launch an app, trust me, just do it with an attitude "we'll see it later" and whenever an error occurs which is normal thing when we learn something new, trust me you will be able to solve half of them already by yourslef.
Rest there are good people here to help you out.

You are getting afraid you will fall even before you have learnt to walk. Which is not good, just go for it, falling and rising is a fun process as well :)

I think that errors happen often because of the nature of code (which is low, but's still there). There are lots of rules to make an idea happen and they must be strictly followed. I do am worried about API endpoints response problems tho, they should work once set.

Withme the POST its working fine, no errors! But im on it for 1 year working every day for some hours.

Well thanks for the input everyone.  I did some "No Code" shopping for about a year.  and with each platform I ran into some sort of major hurdle that could not be addressed easily.  Then BravoStudio, wow! I thought, figma to Bravo, add some tags and away we go.  I have had some issues but figured them out myself. I do agree that there are complex issues behind the scenes.  so I will continue as is and try to finish my first app and see how it goes.

Dave

I've been experimenting with BravoStudio for a couple years and almost every time I thought there was a hurdle, I managed to overcome it. It takes some time getting used to, there's definitely a learning curve and also it's important to take into account the limitations of this product so far. There is so much you can do with Bravo but only within the constraints of the tags + API's. 

Most apps are straight forward to make - API requests from your DB and back to display on the screen. Whenever you encounter a problem/hurdle, always think to yourself, Is this feasible? Often times it is, then you just have to keep going through it to fix it. I know it can be frustrating at times, but if it's possible then it should be able to work out. There's been times where it took me days, weeks, even to solve an issue.

I would say more often its not bugs, but implementation errors. There is a steep learning curve so its often users missing a tag or linking their DB incorrectly (myself included).

I think Bravo's biggest issue is the technical learning curve of backend, etc. But as evidence by things like the Xano/Figma wizard it seems like the team is trying to make backend linking easier.

My app has been live for months now with no breaking. I bet the Bravo team could speak to the architecture of Bravo, but my limited understanding is that once you launch there is some amount of stable code that is baked and uploaded. So that won't randomly break because its not changing.

-
TLDR I personally weighed out.

PROS:

• Figma based: therefore if I get funding later to develop it natively, the Figma files can be still used (unlike something like Adalo where its build in their GUI)
• Native code: The Bravo apps compile to native iOS/Android, so its not a Flutter/React wrapper. I've heard Adalo is a Reach thing, so its overheats your phone alot.

CONS

• Backends are tough to learn.
• Bravo is def slower to learn than Adalo but I think more stable.
• Monetization isn't available yet.
• No front-end analytics yet.

No problem! I saw it's available for the Business level, sadly that level is too expensive atm given i'm bootstrapping.

My understanding though, is that plans like Bravissimo will have access to it soon? At least after almost a year of Bravo investment I'm banking on it 🤞😬

Based on this convo