Hi Bubble fam, Wesley from Flusk here
It’s been a few months we’re working underground on something game-changing for the Bubble ecosystem and the way you develop Bubble applications at scale.
We are specialized in Bubble security and are already running Flusk Vault, a tool that performs automated security audits on Bubble apps. But that’s not the topic today.
My co-founder Victor and I started Bubbling a few years ago. We went from Bubble freelancers to teaching Bubble at Ottho, the 1st teaching organization in France.
All this to tell you that we’re professional Bubble developers, and know as much as you how hard it is to scale a Bubble application to a high level and get the important metrics and alerts to know what’s wrong (and when it’s wrong).
When you start to get some traffic on your app, it becomes impossible to keep track of what’s happening and which unexpected errors your users are facing.
I’m pretty sure no one will disagree: the Logs tab on Bubble is horrible to work with.
When you start Bubbling, you just don’t go because you don’t understand anything.
And when you become good enough to actually understand how Bubble works, you sometimes need to know what happened with a specific User and how he came to a specific situation on your app.
- Digging though the workflows with the current UI/UX is hard.
- The way the logs are ordered is rarely the order the workflows runs on your app
- It’s everything but visual, in opposite to the nature of no-code
- You have to be pro-active by looking for errors yourself. There’s no global error handling methods
- You don’t have any global statistics about your workflows: how long they took to run, how many WUs they consumed, % of success, …
At scale, and even before, you want to be aware of any errors that your users might face.
As of today, you have 2 ways to find errors:
- Filter all your logs, enjoy that nice UI, find some error logs, replace them in the context (good luck with this) and try to fix them
- Wait for a user to create a bug report
And what about the errors happening on the back-end?
As no client is currently running those actions, the ONLY way of catching them is to go by yourself, on a regular basis, check for server-error logs.
An awesome tool like Bubble needs something better.
Flusk Monitor is still in a very early stage. We’re running a private alpha testing phase at the moment, and plan to switch to open beta in the next few weeks.
See the end of the post for early-access.
Images tells way more than I, so here’s a preview.
Maybe another one to see how you could analyze your workflows:
All those problems we all face have a solution, and it’s called Flusk Monitor.
It’s your Bubble app’s sniper.
Reprocess your logs and display them in a visual way.
Like a Make scenario, with each node being a step of your entire workflow, with the enriched data to be able to troubleshoot efficiently.
This way, you can find out which step of your workflow failed, why, and what’s the current data in it.
List log-viewer with analytics.
In a clean interface, visualize the last logs from your app and quickly identify errors.
Explore with enriched data from the previous steps of your workflow, and get insights such as duration, the page this wf was run on, success % of this workflow, and much more.
Finally a way to be notified on errors, boosted by AI.
As soon as a User faces an error on your app, you will be instantly notified.
We trained an AI model over 9,000,000+ logs entries to detect whether an error log should be considered critical or not.
You don’t want to be spammed by random errors.
But if a Stripe workflow fails, you’ll instantly be notified by Email and Push Notifications.
The same we had for Flusk Vault:
And this even works for backend workflows!
From now, I’ll regularly post under this thread to reveal a few features as we integrate them.
The goal of this thread is for you to express what you need to build scalable Bubble apps, and for us to get feedback on our ideas/next builds.
Flusk Monitor is currently under private alpha. We’ve brought together the best experts and agencies founders to give Flusk the right direction from the beginning.
Open beta is planned for early August.
Want to join private alpha?
Reply to this post, and I’ll get in touch by DM.