Some things I messed around with and built in Bubble while I was supposedly working on my app
These all just use an HTML element. No workflows with work units or anything.
You could use AI to write the code if you need.
The backgrounds are just an HTML element set in an align to parent group with text elements over them.
I think the best thing is the horoscope. It gives a new one every day for at least a year for every sign. It works on an algorithm. Most don’t know that’s how horoscopes online work… they just use an algorithm. There’s not actually someone sitting around with a crystal ball every day
Just thought someone might find it interesting.
I’m sure some of you probably have come up with some cooler stuff… it would be fun to see if you want to share.
I have a test page on every app I work on. It’s a good place to put stuff and try it out.
The games I’m showing are pretty simple, really. I was messing around with one that’s a racing game and uploaded images, etc. to use in the code, so the background and game look like a real video game. Didn’t show it because it still needs a little work and I got bored with messing around with it. Just wanted to show some simple ideas.
I’ve also built whole components and whole pages with the HTML element. A lot someone can do with it, really. Easy to use the toolbox plugin if you want to send or get stuff from the database for your HTML element.
Sometimes you have to change the code if you have more than one HTML element on a page so they don’t interfere with each other.
Anyway, thanks for the comment and idea. Enjoy the rest of your day!
It’s one of things where we get a little distracted and need to experiment once in a while. Yeah, AI has helped improve a lot of the landing pages even built on Bubble because you can drop some nice visuals. I like making long loading screens a game so they can play while they wait for something to happen if they want to.
Great topic, I think using AI to create HTML and Plugins you can really do some cool stuff.
Recently I mocked up a calendar feature in Claude Code & Buildprint and at first it suggested using Full Calendar and then I pushed back since I really liked it’s HTML mockup it created. So I had it give me Plugin building instruction to put the HTML and functionality into a Plugin. Within an hour or two I had a multi-resource calendar that is specific to my app and and more flexible than Full Calendar would have been.
I’ve also had AI wire up HTML loading popups and elements which works really well.
Nice. I would like to learn more about building plugins sometime when I get more time.
I do use a Twilio plugin since users sign into my app with their phone number and then get a 6-digit code texted to them to enter.
@lola had a great tutorial on building the plugin, which I thought was super good. I love how she broke everything down and explained how to build the plugin. I use that plugin. It’s worth watching that tutorial.
But yeah, I’m guessing that with a plugin you can expand on what you do with an HTML element.
Thanks for the tag and for watching the video @senecadatabase ! Plugins are incredibly powerful. As gf_wolfer mentioned, Buildprint now supports plugin creation, so you can absolutely vibe-code a custom plugin.
Honestly there is not much you need to learn now it’s simple commands in Buildprint like Lola mentioned or instructing AI to tell you what to put into the Plugin Editor fields.
Personally I scope what I want out of a plugin with my AI and then tell it to give me a local HTML file with the instructions I can work through where I copy and paste into the plugin editor.
It’s probably easier with Buildprint but this lets me think through the plugin functionality piece by piece so I can spot any parts I might need to ask the AI to change before having to publish and test the plugin.