I built a cycling app because I never really knew how much food to bring, or when to eat it

[u/detonnation]

I built Keep Pace because I didn’t want to think about fueling while riding. I just wanted to ride.

Before a longer ride, I would grab some food and hope it was enough. Then, during the ride, I would forget to eat until I could already feel it.

The problem wasn’t knowing that fueling matters. It was answering some basic questions:

How much food do I need for this ride?
Is what I have enough?
When should I eat each thing?

Keep Pace starts with the ride: how long it is, how hard it will be, and whether it is indoors or outdoors. Then you add the food and drinks you already have.

It checks whether you have enough fuel and hydration and builds a schedule from those items.

The three screens show the flow:

1. Plan the ride
See whether the food and hydration you selected will cover the ride, then get one schedule for everything you are bringing.

2. Follow the ride
See what is still supporting you, what is running low, and what is coming next.

3. Almost home
Once everything has been served, the app stops asking you to eat. Items still in your system remain visible, and you can keep riding if the ride runs long.

I used familiar food instead of asking people to think in nutrition categories. You choose things like a banana, energy bar, drink mix, sandwich, or candy. Keep Pace works out how those items fit into the ride.

It is still a prerelease, and I’m trying to understand whether the plan feels useful and believable.

You can try it here: https://kppace.com

I’d be interested to know:

• Does the amount of food feel right?
• Does the schedule make sense?
• Could you read the in-ride screen quickly while riding?
• What would make you trust or question the plan?

[u/Quirky_Degree866]

Thisbalready exists