Designing Useful Randomness for an Open-Web Discovery Extension

YxYo — Wed, 29 Jul 2026 18:03:35 +0000

Most “random website” buttons have the same failure mode: they are random for about three clicks, then the experience becomes repetitive, noisy, or unsafe.

I wanted to explore a different question:

Can serendipity feel surprising without feeling careless?

That question became Web Wander, a free Chrome and Firefox extension for discovering unexpected corners of the open web.

Randomness is not the product

Pure randomness is easy. Useful randomness is a design problem.

A good discovery session needs several kinds of variation:

different providers and provider types
different destination domains
broad wandering and focused wandering
safeguards against search pages, login gates, unsafe downloads, and obvious spam
enough memory to avoid immediately repeating what someone just saw

Web Wander currently rotates across 24 discovery providers. Those sources include independent-web indexes, curated collections, archives, academic resources, media discovery services, and small-web projects.

The extension also offers 56 categories, custom keyword wandering, web-era browsing, and dedicated video and music modes. The point is not to predict the perfect next page. It is to give someone a useful way to leave the same feed for a few minutes.

The interface has to explain the randomness

A mystery button can be fun, but it also creates uncertainty. Where will it send me? Why did I get this result? Can I influence the next one?

I ended up treating control as part of the discovery experience:

Browse all rotates across the enabled provider mix.
Browse by category narrows the journey without turning it into ordinary search.
Custom keyword mode lets a passing curiosity guide the next destination.
Web-era modes make time itself a browsing filter.
Provider controls let people enable or disable discovery sources.

That balance matters. Too little control makes randomness frustrating. Too much control turns the product back into a search engine.

Repetition is a state problem

A random choice can still repeat patterns. Even if two URLs are different, they may come from the same domain, the same kind of provider, or the same narrow corner of the web.

Web Wander keeps preferences, provider queues, a wander count, and recent destinations locally in the browser. It varies recent providers, provider types, and destination domains before navigating.

The useful lesson was that “don’t repeat the previous URL” is not enough. Repetition has several layers:

exact URL repetition
domain repetition
source repetition
source-type repetition
category repetition

Treating these as separate signals makes the experience feel much larger.

Privacy changes the architecture

Web Wander does not require an account. It does not send browsing history, destination history, cookies, referrers, advertising identifiers, or an extension-specific user identifier to a recommendation service.

Most wandering uses provider routes, public catalogs, or fixed non-personal discovery requests. When someone deliberately uses custom keyword mode, that keyword may be sent to compatible search and discovery sources so candidate results can be assembled. The useful candidate pool and ranking remain local.

This constraint removes a familiar growth shortcut: building a progressively richer behavioral profile. But it also keeps the product aligned with its purpose. A tool for escaping predictive feeds should not quietly build another predictive feed.

Discovery should send people outward

Another design choice was to open discoveries on their original websites.

The destination is not converted into a card inside Web Wander. It is not wrapped in an engagement feed. The extension is a doorway, not a replacement for the open web.

That makes the product less “sticky” by conventional metrics, but stickiness is not always the right goal. Sometimes the most honest success metric is whether the tool helped someone leave the tool.

What I am testing now

The project is live on Chrome and Firefox.

The questions I care about next are:

Does controlled randomness stay useful across a longer session?
Which categories produce genuine curiosity rather than novelty clicks?
Is the privacy explanation clear before installation?
Where does the provider mix feel uneven?

If you try it, I would value blunt feedback on discovery quality, repetition, and whether the controls make the experience clearer.

Disclosure: I built Web Wander. It is free, and this post explains the product and the design decisions behind it.