Building Revela: Real-Time Bidding (Part 3)

Making every bid count: live updates and rules that keep auctions fair.

What We Wanted

Auctions need to feel live. When someone bids, everyone sees it. The clock is clear. The previous high bidder is notified. And no one can "snipe" in the last second—so the outcome feels fair, not gamed.

Getting that right is mostly product and rules, not exotic tech.

Rules Before Code

Before any bid is accepted we check: Is the user verified? Is the auction actually open? Does the bid meet the minimum increment? Can this user bid (e.g. not the seller)? Bids are processed in a single atomic step so two people can't both "win" the same price. All of that is standard—the important part is having the rules explicit and enforced consistently.

Anti-Sniping: Extend, Don't Block

The annoying pattern is a bid in the last few seconds so nobody can respond. We didn't want to add complex rules or hidden end times. So we went with a simple rule: if a bid lands in the last 5 minutes, the auction extends by 5 minutes. One clear trigger, one outcome. It removes the incentive to snipe and keeps the UX predictable.

Live Experience

Viewers subscribe to the auction; when a bid or extension happens, everyone gets the update. The previous high bidder gets a notification. No custom protocols—we use a familiar real-time channel and keep the payload minimal (current bid, countdown, no bidder identity). The result is a live feel without overbuilding.

Takeaway

Real-time bidding is less about the transport and more about clear rules (who can bid, when, minimum increment) and fair play (anti-sniping by extension). Simple, transparent behaviour beats clever implementation.

See it in action: revela.club — or reach out if you're designing marketplaces or auction flows and want a lean, human-centred approach.