Rippin' notes
Essays on making rides happen.
Thoughts on motorcycle squads, better ride planning, local discovery, AI trip building, and why the best ride app should start before the ride does.
Launch reading
Built for the rider loop.
These posts explain the product point of view behind Rippin': the crew, the route, the plan, and the memory afterward.
Why motorcycle apps need squads, not just ride logs
Ride stats are useful, but most rides start in a group chat. Rippin' treats the crew as the center of the product.
Read the postHow AI trip planning should work for motorcyclists
A good moto trip is not the shortest line. It needs scenic roads, fuel, food, lodging, weather, and realistic day pacing.
Read the postRide planning beats ride tracking for getting people outside
Tracking captures what happened. Planning makes something happen. The best app needs both, in the right order.
Read the postSan Diego motorcycle rides, routes, and Rippin segments
Start with Palomar, Sunrise Highway, Julian, coastal coffee rolls, and rider-submitted community roads.
Open the guideRider updates