Overcoming Decision Paralysis: Building a Zero-Signup Activity Engine with Vanilla JS

We have all experienced those moments where we have free time, open our phone or laptop, scroll through feeds for twenty minutes, and still feel completely bored. It is rarely a lack of available options—it is decision paralysis. When everything is accessible at once, choosing a single activity becomes surprisingly exhausting.

Why I Built It

I wanted to build a practical tool to solve this exact loop. Most modern web applications try to maximize user retention by keeping people glued to a feed. I wanted to build the opposite: an instant, friction-free tool that gives you a single, concrete idea—a quick creative challenge, a physical task, or a mini learning project—and helps you move on to doing something active.

Key requirements from day one were zero friction: no user accounts, no onboarding flows, no tracking cookies, and no paywalls. You open the page, press a button, and get a realistic activity idea immediately.

Tech Stack

To keep performance high and maintainability simple, I chose a minimal stack:

• HTML5 & Vanilla CSS: Designed with custom properties for rapid dark mode switching, standard CSS Grid layouts, and subtle CSS transitions.
• Vanilla JavaScript (ES6+): Pure client-side logic without full framework overhead, keeping the entire application bundle under 45KB.
• Web Storage API: Utilized localStorage to save user preferences, custom activity history, and bookmark favorites without requiring a backend database.
• Static Site Hosting: Deployed via static distribution for sub-second global page loads.

Technical Challenges

1. Preventing Duplicate Suggestions Without User Accounts

Without saving user profiles on a server database, ensuring users do not get the same activity twice in a short session required a client-side solution. I created a lightweight queue algorithm in JavaScript that maintains a rolling history buffer in localStorage. Each time a random suggestion is generated, the algorithm checks the buffer history, filters out recently presented IDs, and updates the queue dynamically.

2. Schema Design and Filtering Performance

A boredom cure is only effective if suggestions match a user's current situation (e.g., indoor vs. outdoor, solo vs. group, low effort vs. active). I structured the dataset using a clean JSON schema with category tags, difficulty markers, and estimated time commitments. Filtering these attributes in real time on the client side ensures instant UI updates without network latency.

3. Low-Latency Performance Optimization

When a user is bored, even a two-second load screen can cause them to abandon the site and go back to passive scrolling. By avoiding external UI libraries and heavy JavaScript runtimes, the initial load time is nearly instantaneous even on slow mobile networks.

Lessons Learned

Building this project reinforced an important lesson: not every web application needs a backend database, OAuth authentication, or a full frontend framework. Stripping away non-essential architecture often results in a faster, more reliable, and far more user-friendly tool.

Try It Out

If you ever find yourself stuck deciding what to do next, you can try the project live at BoredNoMore. It is completely free, instant, and requires no registration. I would love to hear any technical feedback or ideas for new activity categories you think should be added!