Selected work / Singapore / walking
Routelette
A playful Singapore walking-route picker with region, length and mood controls.
The idea
Let the constraints choose the walk.
A map sits beside slot-style controls and a detailed route card. The selection keeps the initial route, a park choice and the route-selection interface.
Distances, access and route conditions are historical source data. Verify current conditions before walking; these screenshots are project documentation.
Three selected moments
A closer look.
Move through the selected stills.
01 / Selected moment
The first route
A cross-island route appears alongside the constraint controls.
Open full image ↗
02 / Selected moment
A park in focus
Selecting Bishan–Ang Mo Kio Park updates the route details.
Open full image ↗
03 / Selected moment
Rolling the choices
The roll action explores the available choices within the constraints.
Open full image ↗Make something of your own
Build your own.
Take the idea into Codex and adapt it to your own subject, sources and audience.
Reconstructed recipe · Not the original prompts
An end-to-end recreation has not been tested.
01BriefDefine the experience
Build a walking-route picker for [CITY] with region, length and mood controls. Inspect the repository and its instructions first, preserve existing work, and ask for the intended audience and available source material. Recreate the interaction idea rather than promising an exact copy of the original. Start with one complete, useful flow.
02IngredientsPrepare sources and assets
Use a small source-backed route dataset with stable IDs, geometry, distance units, access notes, official URLs and checked dates. Distinguish total mapped track length from one continuous recommended walk.
03InteractionBuild the core flow
Implement lockable constraints, a reproducible shuffle option, clear empty states, map/list synchronization and an explanation of why a route matches. Keep directions as explicit external links; do not require location permission for basic browsing.
04Verify & preserveLeave a working handoff
Use a restrained layout with readable typography and clear navigation. Check the production build, keyboard access, mobile layout, reduced motion, missing assets and network failures. Keep all key information available in HTML. Record what actually passed. Leave source, a lockfile, setup instructions, data provenance and unique assets in a small rebuild kit. Exclude secrets, dependency folders and caches. Capture a few representative moments for a showcase. Do not claim an exact backup or tested regeneration unless a restore was performed.