I’ve been in the Bubble trenches since 2017, was an agency founder for a bit, and built my first Bubble plugin last year. Over the years, I’ve helped numerous clients build and optimize their Bubble apps.
One common challenge I’ve encountered is the clutter and disorganization of layers and workflows. I’ve been guilty of never getting around to it, but apps really are easier to manage and more professional for client handoff when everything’s nice and tidy like my screenshot above.
To address this, I’m considering offering a niche service where I go in and rename and organize all layers and workflows in Bubble apps for peeps, using naming conventions similar to what @heytherecreated. The goal is to make your projects cleaner, more maintainable, and easier to understand for any developer or team member.
I’d love to get your feedback on this idea!
Do you think this service would be valuable?
Is this a nice-to-have idea not worth paying for? (My biggest concern)
Would you be interested in using such a service?
How much would you be willing to pay for it?
Any thoughts or suggestions are greatly appreciated - thanks in advance for your input!
Do you think this service would be valuable?
For certain users, absolutely.
Is this a nice-to-have idea not worth paying for?
Considering nobody’s doing it for free, I do think it’s worth paying for.
Would you be interested in using such a service?
I would depending on price vs time
How much would you be willing to pay for it?
Related to previous question Obviously more complex apps (or apps that just have no semblance of organization or labeling) would take more time. It may be best to have a set of prices depending on the number of pages, number of workflows, and number of elements. Your time is valuable of course, so I’d say if you could quantity how long it would take you to organize a basic app, and how much your time is worth, that’ll help you there.
Again, I think this is a great idea and depending on the above you may just have me as a client
I have many apps (mostly old ones) where I didn’t organize the Workflows as I built them. Now I do organize them, but it’s a great idea and I would definitely pay for it.
Awesome feedback @msgiblin , thanks for taking the time to answer each! I was thinking flat rate initially, but you’re probably right that it would need to be dependent on layers and workflow count.
I’ll reach out if there’s enough interest to test this out!
Thanks @code-escapee ! Wanting to rename standard conventions / colors / icons was a feature I hadn’t initially thought of - is this because you’ve already communicated some sort of system to a client, or another reason?
@code-escapee This is where my brain went too. My thinking was I’d need a way to quickly count layers and workflows to be able to create quotes.
I’ve used webscraper.io before, so I was able to get a scraping format working consistently on a few different Bubble apps.
Relied on me manually clicking on the “expand all layers” button or workflows tab first and then scraping, so I’d have to fine-tune it a bit more to make it truly automated.
@yousif Will do! As of right now I think there’s enough interest to run a first batch with a few apps.
I think where this really shines is with freelancers or agencies like yourself.
It becomes a reliable last step of project handoff that can be outsourced. Was always the annoying part when I was building apps for clients. “Alright, everything’s working, now I just need to actually go back and tidy up those layers and workflows before I give it to the client.”
As an agency, we spend a lot of initial time just cleaning up projects. Its hard to really begin working when you don’t even know what actually is happening.
@brickstech Ahhhhh smart, I hadn’t even thought of the use case of cleaning up projects received from a client at the start of the build process. Most of my client projects have been “start from scratch” types to try and avoid this haha.
Freelancer here. I really like this idea of organization. I can see great value in your thought and would definitely test it out and be ready to pay for it. I am not a big fan of a workflow-number pricing though but rather a per user account based pricing where I can rename and re-run your product as many times I need (just like the bubble x wu discussion). I have no clue what costs your have to realize this idea but what comes to my mind is a monthly pricing around 10$/project. Or a yearly fee of 80$/project since this product is probably heavy used in a beginning or ending project phase for a day or a week only.
My questions are:
thoughts about partial renaming? E.g. only backend workflows or only red ones?
how would you handle currently manually “ordered” workflows? Like 1_wf, 2_wf, 3_wf and 01-wf, 02-wf, 03-wf or wf1, wf2, wf3
Is this a nice-to-have idea not worth paying for?
No, since it’s unique and with ever growing projects it’s becoming a more and more needed tool (almost must-have). Maybe one day this tool could be natively integrated into the bubble system. From a freelancer/agency perspective it could bring value for a new employee understanding the logic better; for demonstration purposes for clients and for handing over a project.
If a tool saves money for agencies and frees quality employee time they will pay for almost anything.
Obviously more complex apps (or apps that just have no semblance of organization or labeling) would take more time. It may be best to have a set of prices depending on the number of pages, number of workflows, and number of elements. Your time is valuable of course, so I’d say if you could quantity how long it would take you to organize a basic app, and how much your time is worth, that’ll help you there.
Classic use case for some organization.