Introducing Unicorn UI - a new component library for Bubble with 300+ native app components, built entirely with AI.
We built it in 12 hours, using Buildprint, with no manual edits.
It contains components for dashboards, marketing pages, tables with pagination, forms, AI chats, and more.
It mixes custom components with components from open source libraries, to give you and AI agents like Buildprint more inspiration and end to end working examples to implement in your own app.
Buildprint will automatically take ideas and patterns from this component library, so that your app has the best UI possible.
This is the most extensive component library for Bubble, and it’s free for everyone to use. What’s more, it’s not just limited to UI. The library includes backend components too, such as a multi-step AI Agent with tool calling built natively in Bubble.
Beautiful! Thank you so much NQU!
Is there a recommended migration plan you recommend? My apps are heavy on the now obsolete Elemium library.
I’ve asked Buildprint a couple times and received different answers. One recommended that I “start a new app.”
Buildprint will automatically use Unicorn UI components to help improve its own UI gen. If you want to explicitly tell it to use a certain component you like, just mention @unicorn-ui in chat and specify which components you are interested in!
Now working on some cool maps/calendars/charts that are built natively in Bubble with no plugins, and integrate nicely with workflows so you can combine that completely custom UI with native Bubble workflows!
We use inputs as a kind of ‘state’ that the HTML element can set from within it. So, when I move an event in the custom calendar, we set the hidden input variable, which lets us use a native Bubble workflow trigger.
It means we can use custom UI with any arbitary functionality, whilst still being hooked into the workflow engine, and not having all the hoops of Bubble plugins to jump through.
I took a look at the charts, used option sets (this part is arbitrary) combined with HTML elements referencing a library, I haven’t seen that before. Any reason to use a plugin? I feel like with how good AI is at generating boilerplate HTML (Buildprint or otherwise) you can just customize individual chart elements perfectly and plug and play using your dynamic data source.
wait til monday for me to officially publish those new components, then ask Buildprint ‘using Unicorn UI, replace all my date pickers with Unicorn UI date pickers adapted for my design system’
but the approach we’re using for some of these components is that it’s kind of like a mini plugin - your HTML is your code, and inputs become the exposed states + workflow event triggers.
