Skip to main content
← Data, API & Backend
Data, API & Backend May 29, 2024 · 19 replies

It's like issues never get fixed for good

Archived from the Bravo community forum (2021–2026). Some answers may refer to older versions of Bravo.

With a lot of the issues I have raised that the team has resolved previously, I’ve noticed that they reappear after Bravo Vision undergoes a new update. Having already taken a lot of effort to open a ticket, communicate with customer support, and wait for the dev team to look into the issue and fix it, now I have to repeat the process all over again, once, twice, three times. The reappearance of resolved issues not only is a waste of our resources, but also impacts our app users continuously after we tell them the issue has been resolved.

This actually poses a great risk of losing users on our platform.

Considering 1) how inefficient it is to fix the same issues over and over again, 2) how much each issue impacts and re-impacts our users, and 3) this sentiment is echoed by other Bravo users as well, I urge the Bravo dev team to explore ways to track resolved issues in a more organized manner and conduct QA in the testing environment more comprehensively in relation to the already resolved issues.

19 replies

Dany May 29, 2024

There is a big Problem with bravo it’s not Community driven

Laura May 29, 2024

Not to mention that each new Bravo Vision update comes with the possibility that one of the basic functions ceases to work, such as uploading a photo or logging in, both of which have occurred twice in the past couple of months already.

We are about to launch our app and I cannot fathom how it would be successful if our users could just wake up one day and aren’t even able to log into the app…

Laura May 29, 2024

@Dany Klein It blows my mind that there hasn’t been a huge fuss around these constant basic issues. Perhaps most people use Bravo for smaller, personal projects that don’t carry high stakes. Honestly, given the current state of the app, I think it’s best suited for those personal gigs instead of start-ups with a serious plan to launch.

Laura May 29, 2024

@Dany Klein I saw your post about leaving Bravo. What did you end up using/doing instead?

Dany May 29, 2024

@Laura Meng they could be on the top if they would listing to there users

Dany May 29, 2024

@Laura Meng i’m a dev so i started learing react native and it’s going good so far..

Dany May 29, 2024

@Laura Meng they could be so good.. but no I’m so sad they swear I believed so much in bravo

Laura May 29, 2024

@Dany Klein Yeah, we are thinking about developing the app ourselves as well. Bravo is pushing people to embark on their own dev journey lol

Dany May 29, 2024

@Laura Meng yep it’s a good thing haha

Noah May 29, 2024

I hear you guys but I’d counter that I haven’t had as many issues as you guys allude to. Yes, we’ve had problems and had to get them fixed through customer support but time to market, nothing beats bravo for lesser technical people. I hold hope that bravo will get better with time. My product is on the iOS App Store and is pretty complex yet I haven’t had insurmountable problems that increase churn. We’ll see as we grow though.

Laura May 29, 2024

@Noah Hastie I think perhaps the fact that you only published the iOS version of your app makes a considerable difference.

Although issues affecting fundamental functionalities also impact iOS (e.g., not being able to log in with the new update yesterday), Android experiences issues and reappearance of issues far more often, which include not being able to upload photos, app crashes, and formatting issues with basic text components, etc.

As much as I’d love to avoid Android, the nature of our app does not allow that flexibility. And, any official launch of an app would require the basic performance on both platforms to be guaranteed.

I agree, Bravo does offer a lot of flexibility to non-technical people. However, if we were to choose between having a bank of features vs. being able to consistently log in and utilize the most basic features, we definitely would opt for the latter to prioritize usability.

The problem with Bravo right now is that the basic needs are not guaranteed, leaving users dissatisfied.

Alex May 30, 2024

Yeah I was gonna say the same, once you publish in my experience the builds have been stable. I bet engineering could speak to this, but I think your package gets bundled and sent. So any changes they make after that point don’t matter.

I agree it would be nice if they had a public changelog or bug tracker to watch these things. Some startups do that

Dany May 30, 2024

@Alex Rothera it’s a hybrid app. So your build can get errors without a new build for that reason you don’t need to push a new build when you change things

Noah May 30, 2024

@Laura Meng I hear it. Hopefully the dev teams hear you and help you achieve a more marketable product. I hope to move to android in the future as well so I’m with you on it needing to be more solid. I still trust in the bravo team!

Karla June 3, 2024

My biggest concern is when we have to request a new bundle for fixes that need an update, any of us that use those components that need updating should be notified to create the new versions. This helps prevent these kinds of mistakes.

Laura June 3, 2024

@Karla Fernandes | design & no-code Agreed. It just comes down to needing a lot more organization and transparency with regards to fixing bugs and quality assurance. Right now we not only see the same basic issues over and over again, but also are completely in the dark about when these are fixed

Marielle Ibias Bravo team June 7, 2024

Hi Laura,

Thank you for your feedback and patience. We understand the frustration of recurring issues and are committed to improving our processes. The loading and image upload issues you mentioned have been resolved.

While we completely understand your frustration, we can assure you we track all our issues and constantly work on minimizing any patterns that emerge.

In a platform as complex as Bravo, you might occasionally see the same issue twice, but this is almost always due to factors outside our control.

Indeed, your most recent issue was actually caused by AWS. Following your report, we implemented improvements that will prevent the AWS issue from impacting your app again.

If you would like more details on any of this, please feel free to reach out so we can discuss further.

Best regards,
Marielle

Laura June 7, 2024

Thanks Marielle.

Just to understand the reasons behind the recurring issues and the team’s struggles a bit more, what do you mean by “factors outside of our control”?

Wrote something in this thread and want it removed? Request removal

Still stuck?

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