We've actually had a few teams at YC using Bubble, either to get in or after, once they were in the program. It's awesome as it's a great validation for our technology.
Ah, you are one of the creators. If Bubble is similar to Delphi, I wouldn't call it visual programming (can you develop IF statements, loops and functions visually?).
A better name for Delphi kind of tools would be "Rapid Application Development Environment". And it's more convincing name than "visual programming" - I have never seen a successful visual programming environment.
Can't you ask to expand the permission once that becomes relevant? I imagine that people who just want to try bubble don't want to give you all their private code.
Thanks for the reply, wow you could sell it as a separate product, looks very impressive! I like the contextual videos and the fluent integration with the rest of the interface. Great work!
Bubble is such a great tool, and you really put a lot of attention to the details. I really enjoyed trying it.
My question is: So one big strength of textual languages vs visual tools(and DSL's) is expressivity - visual languages are limited to their specific domains, while you can use, say, python to build complete systems.
Do you see this distinction remaining ? or we'll have some way to build multi-domain systems visually ?
Yes, this distinction will probably remain, but we're trying to push where we need to get back to textual languages. If you need to build a machine learning algorithm, I'm not sure visual tools will ever be the way to go (though i'd love to see this).
But both ways work well together. In Bubble, you'd build your optimization algorithm as a plugin, and then you (and even better, others, non technical colleagues) will be able to use the action you've built visually. The Bubble interface becomes the common language between business, product people and coders.
Yeah, I've tried it at a few shops and it tends to be a cultural problem more than a technical one.
It's also really hard to build the right tools. It's very easy to sink 3-6mo into a tool that doesn't get a ton of usage because you either don't have partners on the other side who are invested or didn't solve the right problems.
For it to work right you need a lot of factors to go just right. When it does it's pretty incredible but feels a bit like trying to catch lightning in bottle.
I think if we want explore ways to connect these worlds we should do same as we are trying to do our architecture: separate view and logic. Most programming languages are quite messy if you think those as abstract model and therefore compilers won't have very good API (if any) for building application from non-textual inputs.
On the other hand views should be much more data-oriented. For example user actions should be copy-pasteable, editable as data and therefore usable for automation.
-Text? Easy "it has been since 60's".
-Visual (button click, drag&drop etc.)? "IMPOSSIBLE!". I claim that it's just bad habit which started as "MVP"-syndrome, continued as "Typical user won't..."-syndrome and finally ended up to "This is what GUI is"-syndrome.
Yea I think I may cut some corners but I cannot see any fundamental barriers here. Therefore I am currently researching this area and hopefully get something out at some point (or die tryin’).
Not really, as long as it’s a data driven app (and not a platform game...). About half of our paying users build startup-type, customer-facing products, while the other half is small businesses building internal management tools (like invoicing, custom CRM, etc).
When I wrote it, I was thinking along the lines of "hey, I like visual feature x in this website. It would be great to just tell bubble I want that". Just thinking out loud.