Skip to content
Back to work

Kenya Quest

Real places, five small tasks, one very good day in Nairobi.

Write-up in progress: some sections are still draft copy.

Role
Full Stack Engineer, Designer
Duration
—
Team
Solo Project
Status
Production
Platform
Web App
Completed
September 2026
Kenya Quest interface

01

Overview

Kenya Quest turns Nairobi into small adventures you can actually finish. Visitors turn a low-poly 3D model of the city, pick a landmark such as KICC, Karura or Karen, and follow a quest of five small tasks linking real places.

02

Problem

Nairobi has forests, waterfalls, giraffes and rooftop views, but most guides are long lists. People need a small, finishable plan for one good day.

03

Objectives

  • Make choosing a day out feel playful rather than like research.
  • Work without sign-up, keeping progress on the device.

04

Solution

  • Interactive low-poly 3D Nairobi with landmark pins
  • Quests of five real-world tasks
  • Map of quests by neighbourhood
  • Filter by mood and budget
  • Progress and stamps saved on device

05

Technology

ReactThree.jsLeafletMotionLenisTailwind CSSCloudflare Workers

06

Architecture

React SPA on Cloudflare Workers

React 19 SPA built with Vite and React Router, deployed on Cloudflare Workers. The hero city is a three.js scene; the quest map uses Leaflet.

Data. Quest data is served to the client; user progress stays in local storage.

API. Read-only quest and place data.

Auth. None — no sign-up by design.

07

Key engineering decisions

Performance. The 3D scene uses low-poly geometry so it stays smooth on mid-range phones.

Accessibility. Keyboard controls for the landmark carousel and a pause control for motion.

Security. No accounts and no personal data collected.

Trade-offs. Local progress instead of accounts: less friction, no cross-device sync.

08

Challenges

Keeping a 3D hero, smooth scroll and a map fast on one page.

A small, finishable plan beats a long list.

11

Gallery

Kenya Quest
Kenya Quest

12

Links

Have a problem worth building?

Tell me what the software needs to do and who has to use it. If it is a good fit, I will come back with scope, a build order and a realistic timeline.