I built a countdown timer for Bubble… but I didn’t want it to be just another timer.
So I made it:
• Smooth, animated, and clean
• Persistent (doesn’t reset on refresh)
• Fully customizable (days, hours, minutes, seconds)
• Works without backend setup
The goal was simple:
Make something that feels like a real product, not just a component.
A lot of Bubble apps look functional… but lack polish.
Small details like this completely change how users perceive your product.
If you’re building with Bubble, this might help you improve your UI instantly.
Demo
Would love feedback from other builders.
Does this plugin use work units?
My countdowns, I use a custom state with no plugin which is work unit friendly
No, it doesn’t use work units.
The countdown runs fully on the client side using JavaScript, so there are no repeated workflow triggers or server calls. It’s designed to be lightweight and efficient, similar to a custom-state-based setup but with more flexibility and features.
1 Like
Thanks.
I try not to use plugins unless I’m too lazy to code them myself into Bubble.
I want someone to build a plugin to handle all the custom states that are used in Bubble.
I did look into it one day… it can be done, but with the way Bubble operates, it would be a big task.
Anyway, I got busy with other things and didn’t continue building the plugin.
I think it would be a cool plugin that a lot of people would use
2 Likes
What’s the use case that would make the plugin better than just using custom states? The only one I can think of is for custom states that are lists you can configure to be set on page load without workflow, but other than that I’m short on ideas of how/why a plugin to replace custom states would be valuable.
