21–30 of 124 posts
hmmmm, "No Credit Card Required" you can sign in with Github! Just give us access to all your private repositories! Ummm, no. That's just rude.
Personally, I very much prefer people to ask me for a social, rather than storing my password.
Earlier quoted context omitted.
Thanks for the kind words :) 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, no…
That's actually very close to how modern game engines with with large teams(substitute designers/artists for product/business) work. Very cool stuff, kudos.
hmmmm, "No Credit Card Required" you can sign in with Github! Just give us access to all your private repositories! Ummm, no. That's just rude.
I see signup with email+password, or google, or github. Did I miss something? It seems perfectly legit, there are alternatives, and github seems much more appropriate than facebook here. Personally, I very much prefer people to ask me for a social, rather than storing my password.
Earlier quoted context omitted.
I see signup with email+password, or google, or github. Did I miss something? It seems perfectly legit, there are alternatives, and github seems much more appropriate than facebook here. Personally, I very much prefer people to ask me for a social, rather than storing my password.
I don't mind using github for identity, but it wants access to private repositories.
No code required!.. unless you want need something that isn't a date picker or Google maps widget, then yeah you need to write code [0]. [0] https://manual.bubble.is/building-plugins/building-actions.h...
Yes, that's the vision. But then other people can use the plugin without coding, so the work is only done once. Disclaimer: I'm the founder, but didn't initiate this thread. Happy to answer questions though.
It would have to use standard pro level libraries and tools underneath, with the easy UI being essentially and abstraction over of subset of the functionality. This would allow it to retain great usability, but still with no limitations for advanced users.
Of course this hasn’t really happened yet, but I think it’s because the right balance, architecture, and respect for both user experiences has not been applied. It would also involve leading and tightening some standards to allow things to work together more consistently. Remember how things were before package managers? Why couldn’t there be a better way to standardize scaffolding operations and configuration for example?
I realize a lot of this seems to be pulling in two different directions, but so many of the pieces already exist, and so much of pro effort is wasted on grunt work tasks like getting things glued together that should be easier.
Earlier quoted context omitted.
I don't mind using github for identity, but it wants access to private repositories.
Oh got it, sorry. Yeah, I can see reasons, but they should definitely split the authorization in 2 parts if you want to also allow access to private repos.
Earlier quoted context omitted.
Yes, that's the vision. But then other people can use the plugin without coding, so the work is only done once. Disclaimer: I'm the founder, but didn't initiate this thread. Happy to answer questions though.
Curious how many paying users you have.