qtktest

Scaling the Vision: From One Test to a Suite

The traffic from the first test proved the demand. Now, I had to build a real product.

1. Expanding the Test Library: Based on psychological research, I added core cognitive tests:

   • Number Memory: A classic digit-span test for working memory.

   • Visual Memory: A pattern recognition game.

   • Verbal Memory & Typing Speed: These were later additions that catered to productivity hackers and language learners.

   • Key Decision: Every new test followed the same rule—simple UI, instant feedback, and a clear benchmark. No login required to play, which removed friction.

2. Technical Evolution: As complexity grew, I introduced a lightweight React frontend for better state management in the memory games. The backend remained Node.js/PostgreSQL, but I added Redis for caching leaderboards and frequent user data. The most critical architectural decision was making each test page statically generated where possible, ensuring lightning-fast load times.

3. The "Viral" Engine: Percentile Rankings. This was the magic. After each test, users don't just see a score. They see: "You are faster than 78% of people." This single line of text is what makes people want to share their result. It’s a built-in growth lever. People would tweet, "I'm in the top 5% for reaction time!" driving free, targeted traffic.