The story behind Fenwick Ridge
From trail sketches to a puzzle idea
It all started as a quiet weekend hobby. We loved pulling out old topographic maps, tracing ridge lines with a pencil, and imagining the stories hidden in each contour. One evening, comparing a couple of hand-drawn sketches, we noticed that the patterns of elevation could be turned into a simple logic challenge. That spark felt like a puzzle waiting to be built, and we decided to see whether our map-doodling could become something people play in a browser.
The first prototype was rough — a grid of squares with a few numbered peaks, where you deduced the missing heights from arithmetic clues. It was clever, but it didn’t feel like being on a mountain. The moment that changed everything was when a friend ignored the clues entirely, dragged a finger across the map and said, “I’d go this way — it’s flatter.” That’s the game we actually wanted: choosing a line across real terrain.
Building the daily mechanic
Turning a hobby prototype into a daily puzzle required a few key decisions. First, a fixed rhythm: a new trail appears at midnight in your own time zone, giving everyone a fresh map to start the day. To keep that sustainable, we built a small generator that sculpts a ridge from the date, and a solver that checks every candidate map, throws away any it can’t climb, and works out par — the cheapest possible route — exactly.
Second, we kept the interface minimal. No ads, no sign-ups, just the map, the energy counter and a hint button for the moments when you can’t see a way through the cliffs.
Third, we added a simple streak counter. Seeing a number grow each day turned out to be a surprisingly strong motivator for our early testers, and it let us keep the game personal without collecting anything about anyone.
Playtesting and community feedback
Before opening the game to the wider web, we invited a small group of friends, fellow hobbyists and a few strangers from puzzle forums to try the first weeks of trails. Their feedback was invaluable. Some found the early hint too vague (“look for a gentler slope” is not much help on a gentle slope), so hints now point at the best next step. Others asked to revisit past days, which is why there’s now an archive that goes all the way back to Trail #1.
We also learned to watch for edge cases. One tester found a map where par could only be reached by a route that squeezed through the corner between two squares — something our rules never meant to allow. We tightened the solver to follow exactly the same rules as the player, and added an automated check that runs a year of future maps before each release. It added a bit of development time, but it paid off in the trust players place in the daily trail.
Lessons learned and what’s next
Shipping Fenwick Ridge taught us a few things about turning a personal passion into a shared experience. Start small and let the core mechanic shine before adding polish — our earliest route version was barely more than numbers on a screen, yet it already captured the fun of choosing a line. Listen closely to early players; they’ll tell you what feels confusing far better than any internal debate. And keep the pipeline light: automating generation and validation saved us countless hours.
Looking ahead, we want to experiment with seasonal touches — perhaps a winter ridge with snow-covered tops, or autumn colours on the lower slopes. People also ask about leaderboards; if we ever do them, they’ll have to work without accounts and stay entirely optional, to keep the relaxed feel that brought most of us here.
In the end, Fenwick Ridge remains a love letter to the trails we enjoy walking, translated into a daily mental hike anyone can take from their desk. We’re grateful for everyone who joins us each morning, and excited to see where the next ridge leads.