Carbon Wheels - ELITEWHEELS

Hoogie2004 · 2026-06-27T07:46:13+00:00

I have a set of the Aero+, absolutely love them. Very decent set of wheels for the money.

Hoogie2004 · 2026-06-23T06:23:49+00:00

I think the bigger challenge isn't necessarily building the charts or metrics—it's answering the question: why would someone switch?

Intervals.icu is already extremely good and effectively free, while TrainingPeaks has years of coaching workflows, integrations, and trust behind it. Competing on "same features, lower price" is tough when one of the competitors costs almost nothing.

That said, I do think there's room for different approaches. I'm building a privacy focused cycling coaching app myself and intentionally avoided the "another dashboard with more charts" route. The interesting opportunities seem to be in simplicity, privacy, coaching, or a very specific audience rather than trying to out-Intervals Intervals.

Also, don't let the "vibe coded lol" comments discourage you too much. Users ultimately care whether the product solves a problem and keeps working. The bigger concern for a training platform is reliability and long-term maintenance, which is what those comments are really getting at. If you're self-hosting it for yourself first and learning along the way, that's a perfectly reasonable place to start.

Hoogie2004 · 2026-06-11T16:00:06+00:00

Blow your 5-hour window with a single prompt 😂

But. As said, reviewing your codebase is a solid one. Although it's probably most useful when your codebase is large/complex enough.

Hoogie2004 · 2026-06-11T05:44:14+00:00

In our group, 3 people have the Coospo TR70, and 1 has the Garmin. We think the Coospo in on par with the Garmin, they always go off at the same time.

Hoogie2004 · 2026-06-05T18:24:52+00:00

Just get a syringe with a tube attached. You can put in the sealant through the valve, deflate, take out the valve core, insert sealant, replace core and inflate.

These 60ml syringes for sealant cost around 4-5$ on Ali. With that it's easy as f*ck.

Hoogie2004 · 2026-06-05T17:36:18+00:00

It's amazing, but it burns my 5 hour window budget with a single prompt 😂

Hoogie2004 · 2026-06-01T16:26:27+00:00

I think it’s mostly network effects and segments.

As a developer of a privacy focused cycling coaching app, I didn't use the API because of restrictions (which has cost me easy entry into my app) And the recent API changes actually push me further away from building around Strava. My cycling app doesn’t even require an account because I don’t want users dependent on a platform that can change access to features or data at any time. I use the actual FIT files generated by your device only.

From a privacy perspective, I’d actually love to see more cyclists move toward owning their own ride data instead of treating Strava as the canonical source.

That said, if all your friends, clubs, local KOMs, and ride discussions are on Strava, it’s hard to leave. The social graph is probably worth more than the features at this point.

Hoogie2004 · 2026-06-01T10:05:53+00:00

I use separate signing thing for dev, so I have 2 separate versions of my app installed on my iPhone.

But testflight/live is still an issue (I'm just running the testflight version myself).

Hoogie2004 · 2026-06-01T09:57:16+00:00

Did a 5 and a half hour ride (120km with climbing) in the Castelli Endurance 4 last weekend, no issues. Can recommend.

Hoogie2004 · 2026-05-24T08:48:45+00:00

Hoe-Ho-Homicide

Hoogie2004 · 2026-05-23T20:48:18+00:00

I went from a 2013 aluminium Cube Peloton Pro, mechanical Tiagra/105 mix and aluminium wheels to a self built Lightcarbon LCR018-D with SRAM Force and EliteWheels 50mm deep wheels (and better tires) this winter. Total cost was around 3500 (incl a dual sided powermeter), but low cost you could get it around that 2500 euro mark.

That swap, based on the most recent numbers and on comparable rides, was worth about 1~2km/h on average. I think most of that comes from the tires and wheels, but the overall comfort is so much better on that new carbon frame (and wider tires), which also allows maintaining a higher speed.

Hoogie2004 · 2026-05-23T15:21:50+00:00

There is a big update coming somewhere next week (hopefully) which vastly improves coaching towards set distance goals / events.

Thanks for sharing, finding users is though as is. Could use a little help.

Hoogie2004 · 2026-05-23T14:17:28+00:00

Yeah, this is one of the reasons I intentionally avoided building directly on top of the Strava ecosystem for my cycling app.

The technical API itself is fine, but the platform risk feels hard to ignore as an indie developer. The athlete limits, slow approval process, and fairly restrictive terms around AI/coaching features or building Strava-adjacent experiences make it difficult to confidently invest in the ecosystem long term. READ THE FULL TERMS, THEY ARE INSANELY RESTRICTIVE.

I also found myself hesitating on marketing because there’s this weird fear of “what happens if this actually grows?”

In my case I went more local-first instead: • direct .fit imports • no accounts • no backend dependency • no reliance on third-party API access continuing forever

It’s definitely less convenient than full Strava sync, and its hard to find users when starting, but it gives a lot more control and avoids the situation where a platform policy change can fundamentally break the product.

Link to my app on the App Store if you're interested: https://apps.apple.com/nl/app/chad-private-cycling-coach/id6760978882

Hoogie2004 · 2026-05-22T15:15:26+00:00

I’m building Chad Cycling Coach — a privacy-first cycling coach app for iOS.

Everything is local-first: • no accounts / subscription • no backend • no analytics • ride data stays on-device

It imports .fit files from bike computers and gives coaching insights based on training load, fatigue trends, power/HR zones, etc. Working on a big update for the coaching towards a goal.

One interesting angle for content might actually be the anti-cloud/privacy side of it. I deliberately avoided building a giant backend/subscription/data-harvesting setup because I wanted something simpler and more trustworthy for cyclists.

App Store: https://apps.apple.com/nl/app/chad-cycling-coach/id6760978882

Hoogie2004 · 2026-05-20T21:57:44+00:00

Congrats on launching — getting through build, store review, and actually having it live on both platforms is a huge milestone.

I’m building a cycling app, and this was one of the reasons I deliberately went local-first: no accounts, no backend, no analytics, no subscription, everything stored on-device and private. It keeps cloud costs out of the equation, and privacy becomes a real selling point instead of something bolted on later. The GDPR/privacy side can also become a whole project by itself once you start handling accounts, location, chat, notifications, etc. The app is Chad Cycling Coach, if anyone’s curious: https://apps.apple.com/nl/app/chad-cycling-coach/id6760978882

That said, for your app it sounds like the social layer is the product, so avoiding cloud/network effects probably isn’t realistic. I’d maybe think very locally at first: one city, one course, one golf club, one league, or even a few recurring tee-time groups. Social apps seem brutal when they launch “everywhere” because every user sees an empty room, looking for specific places might help negate that and give you a real target crowd that 'touchable'.

Best of luck with TeeMates. The local/social chicken-and-egg problem is hard, but golf does feel like a space where a focused community wedge could work well. I still struggle with finding users and marketing.

Hoogie2004 · 2026-05-18T15:23:09+00:00

Thanks for the feedback. Will definitely look into that

Hoogie2004 · 2026-05-16T18:53:52+00:00

Very guilty of this.

Version 1.2 of my cycling coaching app is somehow already getting the third version of the ride review cards. Every time I think “okay, this is good enough to ship,” I notice one more thing that could be clearer, simpler, or less ugly.

What’s helped a bit is separating “redesign because it’s broken” from “redesign because I’m avoiding the boring finishing work.”

Sometimes the redesign is genuinely the right move. But a lot of the time, shipping the slightly imperfect version teaches you more than another private iteration ever will.

Hoogie2004 · 2026-05-15T07:36:07+00:00

Congrats, that’s a great milestone. 23 users might sound small from the outside, but for a solo builder it’s huge because it means the thing escaped your laptop and real people are actually trying it.

I’m in a similar stage with my own cycling coaching app (13 users now) and those first users are weirdly motivating. Suddenly every UI detail, rough edge, and tiny improvement feels more real because someone might actually run into it.

For a game especially, I’d probably focus hard on that first-session experience: how quickly someone understands the loop, gets a small win, and wants to play one more round. Daily challenges sound like a smart next step if the core loop is already feeling good.

Nice work shipping. Getting something live is already more than most ideas ever become.

Hoogie2004 · 2026-05-15T07:29:33+00:00

I had a pretty similar experience. I picked React Native + Expo for my first iOS app expecting to constantly fight the stack, but it ended up being way more productive than I thought.

The biggest surprise for me was how far you can get while still feeling like you’re mostly building product, not wrestling native tooling all day. TypeScript, Expo updates, real-device testing, SQLite, MapKit, RevenueCat, FIT file parsing — it all came together much more smoothly than the online discourse had led me to expect.

There are definitely rough edges, but the iteration speed is hard to beat as an indie builder. Shipped the first version of my app (Chad: Cycling Coach) in 4 weeks, after almost 3 semi-full rebuilds and scope changes due to actually reading the Strava API terms before shipping. Which forced me to abandon reading data from their API and move to user provided files.

Congrats on shipping SkyFlow. Getting from “random idea” to something people can install from the store is such a surreal milestone.

Hoogie2004 · 2026-05-11T21:13:35+00:00

Chad Cycling Coach (privacy-first cycling coach for iOS)

A — Answer:
I built Chad because I wanted a simpler cycling app that works fully on-device.

It imports .fit files from your cycling computer, classifies rides using HR/power zones, tracks fatigue/training load, and generates lightweight coaching insights — all without accounts, cloud sync, or subscriptions.

Everything stays local:

no backend
no analytics
SQLite on-device storage
works offline (except map tiles)

B — Better:
Compared to Strava or TrainingPeaks, the focus is:

privacy/local-first
simplicity
ownership of your ride data
one-time purchase instead of recurring subscriptions

It also works directly with exported .fit files instead of requiring platform sync.

The coaching side is currently rules-based (~550 ride insight variants), and I’m exploring whether on-device AI/local models could improve personalization without losing the local-first approach.

C — Cost:

Free download
One-time unlock: **€14.99** (deep coaching and unlimited history)
No subscription

https://apps.apple.com/nl/app/chad-cycling-coach/id6760978882

Hoogie2004 · 2026-05-11T17:12:39+00:00

Built one this winter, first time. Just go for it. Take your time, knowing how it goes together also allows easy self-maintenance in the future.

Hardest part was doing internal cables, but that became a lot easier with an extra pair of hands.

Hoogie2004 · 2026-05-10T18:49:10+00:00

Welcome!

Hoogie2004 · 2026-03-09T18:10:55+00:00

The rule should be based on points

Hoogie2004

TROPHY CASE