Routes that read the rain.

DryRide is an iPhone-first route-planning and live-guidance product for motorcycle riders who would rather miss the rain. It compares practical Apple MapKit routes with WeatherKit rain and wind data, then explains the time-versus-weather trade-off in plain language.

It is a Happy Webs product: product strategy, route logic, interface design, iPhone engineering and the launch website were developed together rather than handed between separate teams.

The problem is not finding a route

Conventional navigation is very good at finding the fastest line. For a rider looking at a moving rain front, the fastest line can still be the worst choice. A twelve-minute detour may avoid the heaviest weather; leaving five minutes earlier may keep most of the journey dry.

The product question became: how do you compare routes by the weather the rider will encounter at the time they reach each road?

DryRide samples route options against forecast conditions, estimates wet-road exposure and makes the trade-off visible before departure. During the ride it keeps checking from the live position and can surface a meaningfully drier option as the forecast moves.

Route intelligence riders can understand

The interface does not ask someone to interpret a weather radar while planning a journey. Each option presents the practical measures together:

• expected journey time and distance
• projected wet-road mileage
• rain severity and when it begins
• why a drier route is being recommended

An example ride to Glossop Bike Meet shows the fastest route at 1 hour 11 minutes with 15.2 wet miles. The balanced Driest Ride takes 1 hour 24 minutes with 6.4 wet miles: 8.8 fewer miles in the rain for a thirteen-minute trade-off.

Three modes, one clear decision

Weather tolerance changes with the ride. A short commute, a long Sunday route and an appointment with a fixed arrival time do not need the same optimisation.

DryRide gives the rider three explicit modes:

• Cautious: prioritise dry roads while a practical route exists
• Balanced: avoid heavier rain while accepting a light shower when it saves meaningful time
• Fastest: protect arrival time when the remaining rain is minor

The mode changes the recommendation, but the evidence stays visible. The product advises; the rider decides.

Privacy and safety are product requirements

DryRide needs a rider’s location to calculate guidance, but it does not need an account, an advertising profile or a trail of journeys tied to an identity. The first release is designed around Apple MapKit and WeatherKit with no account, no advertising and no cross-app tracking.

It is deliberately presented as a planning and guidance aid, not safety-critical navigation. The interface tells riders to plan before setting off and pull over before interacting. That boundary shaped the content, interaction states and product language from the start.

From working product to launch

The iPhone app is built and being prepared for App Store release. The public website uses real product screens and real route scenarios rather than concept UI, so the promise can be judged against the interface that will ship.

DryRide is useful proof of range for Happy Webs: consumer product thinking, mapping and weather integrations, real-time decision logic, native-app UX, privacy boundaries and a focused launch story in one coherent build.