[openBuild] UI Builder & Personal Library for Bubble: easily build custom design in your bubble app

That’s a huge work, very useful, thanks guys!
Do you have a “pay us a coffee” button or something similar ?

No but we do have an ‘Upgrade to premium’ button :wink:

I’ve been using openBuild premium for the last week or so and it really is fantastic and totally worth it. Saved a huge amount of time fiddling around with UI elements.

Excited to see the premium starter template which I think is coming soon!

Hi, @vincent56 I’m finding the UI builder very useful, but I can’t seem to get the checkbox element to work.

Although the conditions seem OK to me. When I preview the page the checkbox won’t change colour or icon.


I’ve used it on both my design and also on the openBuild template. I’m uncertain as to what is wrong, can offer any suggestions?

Hard to see without looking at the editor. Are you sure the checked state is changed?

I have some doubts:

  1. can i pay and when i don’t want anymore, can i stop paying?

  2. once paid, can i use it in all my projects? Or is the cost monthly per application?

  3. What security do I have? It is necessary to inviter the user with your company, giving all rights to my application.

Best regards

Silvio Gregório

[SOLVED]

The openBuild team contacted me and solved the issue.
for those with the same problem, here the solution.
Just turn your chrome setting to accept third party cookies. Thats it, problem solved!

Hi, I’m very exited to use Openbuild in my Bubble projects, but right now I’m running into this issue when I try to sign up.

No matter what I try to do I get this message.
image

Any clues what I am missing here?

Please need help, I really want to accelerate the development, openbuild seems to be a awesome tool.

Hey @vincent56,

Any updates on the new Team Plan?

Thanks for sharing this! Google is getting very strict with third party cookies and because we use an iframe in your editor it’s extra tricky. Bit glad it worked!

We’re currently working hard on new content, and not just UI components as well as the new plans.

First priority is to get the openBase template out which is basically ready to be submitted now. The documentation needs to be finished and then we will need to change some parts in the apps infrastructure to accommodate shared libraries.

We’ve been collecting really good feedback from our paid users in regards to how they use their personal libraries so we have some great ideas.

As most of you know, we also run ideable.co and it’s been challenging to divide the time properly :sweat_smile:. But we’ve been able to expand the team so all is looking good!

If something is build in open build. How difficult would it be to stop using open build if we want to move off it?

Could anyone answer my questions?

thankful

Sorry Silvio, I missed this!

You can stop whenever you want and payment stops automatically for the next billing cycle.

It’s one subscription for unlimited use for unlimited apps!

We ask you to add the sync account to your application. We use this to get some data on your app to provide the service. Mostly it’s to determine if your application has the openbuild styles or not. If you use the openBase template, you have the styles and all components you copy will also have dynamic styles. Otherwise you get inline styles.

This account is not used to access your app and you so not have to give any permissions to this app. Furthermore, the collaborator does not count towards your allowed number of collaborators.

Hope this helps!

We developed a framework based on how most apps are designed. The pixels we use for our content sizes are arbitrary but are picked to make everything look good from mobile to desktop.

That doesn’t mean you cannot use them in your own, differently sized app. Hopefully soon we are able to have our members share any of their own components with other users.

But for now openbuild components work best with the openBase template or in any other app where there is room for components in the sizes we offer.

In a way it doesn’t matter where or how you use the components. You’re free to use them as you like.

So that also means you’re not stuck with openbuild. You can use it simply as a library of great components!

Thanks for the answers.
Please, a new question arose: what is openBase model, inside Bubble?

Could you give an explanation about this?

I didn’t understand this concept.

I use Bubble and the plugins that are available there. I don’t understand about openBase model.

What are inline styles?

thankful

Openbase is simply a starter template for bubble. It comes with a lot of useful stuff like menus, navigation, user management and more.

In bubble you can manage styles (for texts, groups and other elements) in two ways.

  1. Inline. This means you setup the style for an element on the element itself. You cannot easily add this style to other elements. It’s the equivayof inline styles in css.

  2. Styles as defined in the styles tab of your editor. This is like having a css stylesheet and work with classes to define your styles. When you define styles in bubble you can easily select these for new elements. This is a lot more scalable.

The big advantage of our template is that it matches with the styles we have for openbuild components. This means that a component copied in an app based on our template will have the same dynamic style as found in your app.

What is really cool about this is that when you have changed the styles in your app, a different font or colors, copying a component form the openbuild library will take on the styles in your app.

We’re planning to create some videos around this as it’s easy to see but hard to write about…

For us users, regardless of whether it is openBase or not, is everything transparent to us?

thankful

Not sure what you mean by transparent?

Sorry, I don’t think I was so thorough.

I wonder if for us, users who just pull and drag, do the workflows, what changes, being openBuild, openBase, etc …?

Will I have to change anything?

thankful

You can sign up and use the free components. You will see you can simply copy and paste those components in your application and nothing will affect your current app!