Flusk Vault

Add a notes section to an error log so user can record what has been done in an attempt to resolve the issue. This would be helpful for errors that reoccur or that need some additional monitoring to see what is happening.

This is one of the most common mistakes among big apps, and it does take quite some time and maintenance to keep updating the database connections as well as pages workflows into a visual documentation for a bigger dev team.

Get contextual tips related to an error about how to fix it.

Show errors associated with a workflow with a badge next to it.

For the analytics, it would add quite a bit of value to know the views per page (url parameters, paths, etc.). A heatmap of interactions would be the cherry on top of the cake.

It would probably be nice to be able to define alerts for when an app reaches 90% (or any value) of the current WU included in the app's plan.

Identify the performance impact (extra page load seconds) for every plugin on both pages where the plugin is installed or not.

API parameters are currently marked as an issue when they appear to be sensitive. However, if you added an API key outside a Bubble parameter (such as in clear text in the URL or the body), they won't be detected.

I love the fact that you can see monthly active users, though, I believe that having a way to parse by MAU, WAU, DAU as well as retention (MoM churn) would be amazing!! These are critical KPIs for startups