RumblePoint's mountain-bike software lineage starts before RumblePoint became the public studio identity. On September 22, 2009, Total Square released Mountain Bike Trails for iPhone, an early dedicated MTB trail-discovery app built around a problem riders knew well: the trail could be great and still be surprisingly hard to find.
The surviving App Store metadata describes more than 5,000 MTB-specific trails, over 50,000 miles of riding, GPS-assisted directions, nearby bike shops, difficulty information, and international coverage. In 2009, putting that much riding context into a phone was not a small change in interface. It changed what a rider could reasonably expect to know before leaving the pavement.
The phones changed. The maps changed. The original problem did not: help a rider find the right dirt and understand what waits when they get there.
A small app, at exactly the right moment
Mountain Bike Trails arrived while the App Store itself was still young. The product was intentionally direct: find trails near me, search by place, understand difficulty, get to the trailhead, ride. It did not need a grand platform story. A useful map, a location-aware phone, and mountain-bike-specific data were already a meaningful combination.
- 2009
Mountain Bike Trails
Released for iPhone by Total Square on September 22, with a directory of more than 5,000 MTB-specific trails.
- 2010
Total Square × IMBA
Total Square partnered with the International Mountain Bicycling Association to offer Mountain Bike Trails free during Interbike week.
- 2026
TrailFu
The question returns at a much larger scale: not just where the trail is, but whether it is the right ride, what the dirt is doing, what survives offline, and what exists around the destination.
Then IMBA and Interbike entered the story
In 2010, Total Square partnered with the International Mountain Bicycling Association to make Mountain Bike Trails free during Interbike week. Contemporary Bikerumor coverage preserved the moment. It is a small artifact now, but it matters because it shows the product was not merely an abandoned prototype sitting on a development machine. It was in the mountain-bike world, being used and promoted inside the industry.
Why come back?
Because the map got better and the decision got harder. Riders can now find enormous amounts of trail information, yet the useful questions extend well beyond location: Is the trail open? Is it likely to ride well after the weather? How do these segments become a coherent route? What survives when the trailhead has no signal? What does the local riding community know that a generic map cannot? Where are the Bike Parks, providers, events, and places to stay that make the destination work as a trip?
TrailFu is our answer to that larger version of the problem. The trail map is still there, but it is the beginning of the product rather than the finish line. Destination context, route intelligence, changing dirt, offline discovery, local knowledge, and clear authority boundaries all exist because the rider's real decision grew beyond 'where is the trailhead?'
History is useful only if it raises the standard
We describe Mountain Bike Trails as one of the earliest dedicated MTB trail apps on iPhone. We do not call it the first ever without historical evidence strong enough to carry that claim. The point is not to win a trivia question about the App Store. The point is that we have been thinking about this particular rider problem for a very long time, and the modern version deserves a much deeper answer.