Ridewise, Fieldwise, and Yardwise

Every mountain biker knows the ritual. It rained last night. The radar is clear now. Nobody has posted on the trail association’s page. You text a riding buddy, who doesn’t know either. So you stay home and miss a rideable day, or you show up and chew through trails that needed six more hours.

I got tired of guessing and built a decision engine that answers the question directly: is it too wet to ride? Then it turned out the same engine could answer two more. Is this field playable? Does the garden need watering? Same physics, drying and soaking over time, asked from three directions. So it’s one Swift package and three apps that share it: Ridewise for trails and skateparks, Fieldwise for sports fields, and Yardwise for lawns and gardens, each giving a yes, maybe, or no with its confidence shown.

The hard part was never the weather data. It was turning “what happened” into “what it means for the specific thing you want to do,” and being honest about uncertainty when the model isn’t sure. Both of those are written up in the Lab, edge cases included.