Yes or No Decision

Outsource a binary decision to a fair coin — optionally with "maybe" as a third outcome.

How this works

A purpose-built decision maker for the moments when you genuinely don't care which way a small choice goes — should I get pizza or sushi, do I take the long route home, do I reply to that email tonight or tomorrow. The widget pulls a single random bit (or one of three buckets in maybe-mode) from `crypto.getRandomValues` and shows the answer in a colour-coded pill so you can take it in at a glance. The optional question field is purely cosmetic — typing your question doesn't change the odds — but seeing the question on screen alongside the answer is more satisfying than just a bare "Yes." It also paves the way for the actual point of this kind of tool: paying attention to your gut reaction the moment the answer appears. If "Yes" lands and you immediately feel relieved, that's the real answer. If "Yes" lands and you immediately want to flip again, that's also the real answer — just the opposite one.

The formula

No-maybe (50/50): bit ← crypto.getRandomValues(Uint8Array(1))[0] & 1 answer ← bit == 0 ? Yes : No With maybe (33/33/33): byte ← crypto.getRandomValues(Uint8Array(1))[0] reject if byte == 255 (rejection sampling) bucket ← floor(byte / 85) // 0..2 answer ← bucket == 0 ? Yes : bucket == 1 ? No : Maybe

In maybe-mode the byte's effective range is 0–254 (255 is thrown away to keep the three buckets exactly equal in size — 85 values each). The rejection probability is 1/256 ≈ 0.4%, so the loop runs once almost always. Without maybe-mode there's no rejection step at all because 256 is evenly divisible by 2.

Example calculation

  • Question: "Should I order pizza tonight?"
  • Tap Ask. With maybe off, a single bit decides → "Yes."
  • Notice your reaction. Relief = order. Doubt = your gut already preferred something else.

Frequently asked questions

Does typing my question affect the answer?

No. The question text is shown back to you on the result for context but never enters the random pull. Two different questions, same coin: if you get "Yes" twice in a row, that's just the coin, not the universe agreeing with you.

When should I use maybe-mode vs plain yes/no?

Plain mode for actual decisions you need to make. Maybe-mode for situations where the right answer might be "wait" or "don't commit yet" — should I text them back now? plain says yes/no, maybe says wait. Three-way is also fun for parlour games (Magic 8-Ball substitute) where the dramatic pause of "Maybe…" is half the appeal. For real decisions, the maybe just kicks the can down the road, so use it sparingly.

Why does the answer "tumble" before showing?

Same reasoning as the coin flip — pure UX. The bit is pulled instantly when you tap, but a 600ms pause before showing the answer makes the result feel weighty rather than auto-completed. It also gives your brain time to start forming a preference, which is exactly when noticing your gut reaction matters most. Showing the answer instantly would skip past that moment.

Is "best of 3" or repeated asking valid?

Statistically the math is the same — 50/50 is 50/50 no matter how many times you ask. Practically, repeated asking until you get the answer you wanted is just laundering your gut feeling through the widget, which means the gut feeling already had the answer and you should just go with that. The widget is most useful when you commit to taking whatever the first pull says, no take-backs.

Related calculators