What we really think of it
Bubble is a good tool for moving fast, and a bad choice for building what has to last and grow. We would rather say so at the start than in the second year, when the question becomes expensive.
When we recommend it
An internal tool for twenty people. An application testing a use you are not sure about. A need whose scope will move a great deal in the first six months. In those cases, the time gained is well worth the limits accepted.
When we recommend developing
As soon as the application becomes the heart of your business. As soon as users are counted in thousands. As soon as performance counts, or fine-grained business rules come into play. Bubble’s ceiling is a growth problem, not a starting problem, and it can be anticipated.
The question of leaving
A Bubble application does not export to code. If you have to leave, you rebuild. That is not a deal-breaker provided you know it: what you keep is knowledge of the need, which is often the hardest part.
Our position
We are not an agency specialising in this tool, and that is deliberate. We use it when it is the right choice, and we develop when development is. A supplier with only one tool will always propose it.
