HomeMobileAndroidI wanted an excuse for my slow Strava runs, but Gemini gave...

I wanted an excuse for my slow Strava runs, but Gemini gave me a reality check instead

I trust my gut when a run feels off. Too bad my gut never comes with an explanation.




Add Android Police on Google




Add as Preferred Source



It happens on the most ordinary runs, like the neighborhood loop I could probably do with my eyes closed.

My knees were weak, my legs felt heavy, and I was nowhere near 8 miles. (Eminem fans, you’re welcome).

My heart rate is in the same aerobic zone as always. Yet my watch insists I’m moving at a slower pace. Why?

Is it the weather? The leg day I had the day before? I’ve had questions like these for as long as I’ve been running, and never had a good place to take them.

That’s why, when Strava announced in late October that subscribers could connect their activity history to Google Gemini, I paid attention.

What you need before you try this

A Strava subscription, a US account, and any Gemini plan

A graphic with Strava and Android Police's logo.
Credit: Strava

The connection is only for paying Strava subscribers. On the Gemini side, it works on every plan, including the free one.

Location is another factor. Strava started releasing this feature in the US on October 28 and hasn’t said when other countries will get it.

Setup takes about a minute. Open Gemini, go to Personal Intelligence, pick Strava under connected apps, sign in, and approve the connection.

Gemini pinned my slow runs to my lack of consistency

A bad week or a whole block?

Screenshot of Strava app displaying a distance milestone overlaid on a photo of several people running
Credit: RUN 4 FFWPU – Pexels / Strava

First, I asked Gemini to look at pace against effort across my full training block.

Scrolling through three months of Strava activities to answer one pacing question is miserable when you do it yourself.

After I gave it the date range, Gemini pulled that history together and mapped volume trends and pace over time.

Then it went through my activity history to see how my training cycles stacked up against each other, focusing on the weeks leading into my sluggish runs.

Gemini showed I had dropped from about 15 miles a week to roughly 8 miles, mostly because four runs a week had become two.

It suggested rebuilding my weekly mileage gradually before chasing pace again, since my aerobic base had declined along with my consistency.

The heat got some credit for my worst long run

Humidity also earned a small pace penalty

The display of the Blackview Shark 8 in the sun

I didn’t want to take all the blame, so I pointed Gemini at the worst run of my month. I wanted to know whether heat was slowing me down.

For that, Gemini used the temperature, humidity, wind, and general conditions recorded with the activity, and that day’s humidity was high.

It agreed the conditions were tough and estimated a minor pace penalty from the heat. But it wouldn’t hand me a free pass.

The weather explained a slice of my slow pace, and Gemini again mentioned that my drop in consistency was still the main reason.

Gemini found the exact mile my run started going wrong

Mile-by-mile splits without a spreadsheet

A photo taken on the Oppo Find N6

Next I tried something more granular. I suspected my pacing was doing some of the damage too.

So I picked one of my bad runs and asked Gemini to break down the splits mile by mile.

Gemini flagged the mile where my pace started to drift and set it next to my overeager start. It explained that I likely started too fast in the first 5K.

I have to admit. Reviewing split decay this way is a lot faster than a spreadsheet.

Leg day was eating into my runs

What happens when you log more than runs?

man wearing nike shoes lifting a barbell
Credit: Pexels

Besides running, I also spend decent time in the gym. Next, I asked whether fatigue from other workouts was perhaps the cause of my heavy legs.

The assistant can also find trends across the sports you log. Gemini looked at my sport mix and my metrics across sports, lining up lift days against run days.

It mentioned that I was scheduling heavy leg days right before runs, and that the missing recovery may have contributed to my sluggishness. Of everything I asked, this was the most useful connection it made.

You need to know what to look for

You have to feed it specific dates and locations to get an accurate history, which means you need some idea of what you’re looking for.

I wouldn’t rework a training plan on a chatbot summary alone. Still, Gemini gave me a harsh, yet useful reality check about consistency and cut through the comfortable excuse I had been telling myself.

Think of it like a fast search engine for your fitness history. Let it surface the trends. Open the Strava activity and check its answer against what’s there.

RELATED ARTICLES

Most Popular

Dominic
32712 POSTS0 COMMENTS
Milvus
131 POSTS0 COMMENTS
Nango Kala
7085 POSTS0 COMMENTS
Nicole Veronica
12225 POSTS0 COMMENTS
Nokonwaba Nkukhwana
12308 POSTS0 COMMENTS
Shaida Kate Naidoo
7202 POSTS0 COMMENTS
Ted Musemwa
7467 POSTS0 COMMENTS
Thapelo Manthata
7187 POSTS0 COMMENTS
Umr Jansen
7171 POSTS0 COMMENTS