I'd had the idea for months, the prototype for weeks, and yet I became stuck on how I was going to build my MVP. I wanted to play the part of both the technical founder and creative architect, and yet I found myself leaning towards... Bubble.
And there's nothing wrong with Bubble, it's just that I see myself as more technically sound. However, I do have certain needs that Bubble can solve for me better than I can otherwise.
I have migraines. When I have a migraine, I need to be able to see exactly what is going on in front of me. I can't imagine how the code works itself out, I must see it. Bubble gives me that ability.
I have a very specific data architecture in mind. With Bubble, I can focus on the data architecture, look and feel rather than the learning curve of a new framework.
So I sucked up my pride and sat down and learned Bubble. And my product and maintenance will be better or it.
Hmmm... this post looks like a promotional one, huh? ;-))))
That's great! If it works for you and your users, that's all that matters!