Hey legends,

Welcome to Bubble Therapy™, the no-bullsh*t newsletter for Bubble builders who are one workflow away from losing their sanity.

Every week I’ll give you real talk, actual fixes, and the kind of swearing that makes debugging feel like an Olympic sport.

This first issue is dedicated to the thing that’s ruined more devs’ sleep schedules than caffeine withdrawal: Conditional Formatting.
Because nothing — and I mean nothing — can break your spirit faster than a f*cking conditional.

Conditionals start out innocent.

“When this input isn’t empty → make the button blue.”

Cute, right?
Then three hours later, that button turns grey, then purple, then disappears completely — and you can’t tell if it’s your fault or if Bubble’s just decided to gaslight you again.

You add another conditional to fix the first one.
Now it almost works, except sometimes it flickers when you breathe near it.

Congratulations — you’ve built a logic loop that could power a small emotional breakdown.

You don’t need 12 conditions for the same f*cking element.
You’re not writing a Shakespearean tragedy; you’re styling a button.

Start from the top.
Decide what matters most.
The first condition that’s true wins — everything below it might as well not exist.

If your element looks like it’s possessed, it’s because it’s listening to too many gods.

“Current user’s plan is gold AND current user’s plan isn’t gold” — yeah, I’ve seen that sh*t.

You wrote it at 3 a.m., didn’t you?
Take a break, come back sober, and write your logic clean:

✅ When current user’s plan is Gold → Do Gold stuff.
That’s it. No metaphysics required.

Most conditionals exist because you were too lazy to fix your data.
You didn’t need a conditional.
You needed a clean database and a single state that says “is this user gold?”

You don’t need 12 conditionals — you need one f*cking Boolean.

One time, I spent an entire day trying to make a header change colour on scroll.
I had six conditionals, three workflows, and one existential crisis.

Then I realised Bubble had a built-in “when scrolling position > 0” condition.
Fixed it in two clicks.

Eight hours of pain.
Two clicks.
Humbling.

Bubble’s logic engine is predictable — it just follows orders too literally.
It doesn’t care about your feelings, your design, or your self-esteem.
It will happily execute contradictory conditionals and watch you implode.

So treat it like a robot:
Give it clear, simple, single-purpose commands.
And stop emotionally projecting onto your workflows.

Conditionals are like tequila shots.
One or two? You feel clever.
Five or six? You’re crying on the floor wondering where it all went wrong.

So clean them up.
Be ruthless.
And remember — clarity isn’t optional. It’s survival.

You don’t have to be perfect. You just have to stop breaking your own f*cking buttons.

Keep building, keep swearing, and if it works…
don’t f*cking touch it.

Wes
Chief Logic Therapist, Bubble Survivors Club

Got a conditional story that nearly broke your will to live?
Send it in. I’ll roast it next week in Bubble Therapy #2 — “The Workflow Hangover: When You Forget What Triggers What.”