Tiiks vs Velolog: A Finished Product vs a Thin Strava Counter

Velolog is a new, small Android app that pulls Strava mileage and warns on chain, pads, and tires. Here is how that early counter compares to a finished native product with a catalog and a widget.

The smallest useful maintenance app is a counter. Connect Strava, watch three parts, get a warning before the chain, the pads, or the tires are done. You can describe that product on one screen. Velolog: Bike Maintenance, from 2Matter OÜ, is in that shape. It is Android-only, listed as a new and small app, with a site at velolog.cc. Small is not a disguise. It is the current size of the thing you can actually install and run.

Automatic Strava mileage is the honest core. If you already record rides, a counter that does not ask you to type kilometers is ahead of a paper notebook. Warnings for chain, pads, and tires match the three parts most riders actually replace on a schedule. The marketing site also talks about a fleet and about swapping components. That is a larger story than three warnings. On a very new app, treat the story as a direction, not as a finished floor.

A thin counter can still be the right tool if those three parts are the only ones you will act on. It becomes the wrong tool the first time you care about a cassette, a rotor, a chainring, or a fork service, or the first time you want a catalog model and reviews instead of a generic warning. New is not a moral failure. It is a scope. You should know which scope you are buying. A warning that only knows three consumables will stay quiet while the rest of the bike wears, and you will call that silence “nothing due.”

What Velolog ships today

Velolog connects to Strava and applies that mileage to maintenance warnings. The warnings the product is known for are chain, brake pads, and tires. That set is not random. Those are the consumables that fail on a schedule most riders recognize, and they are the three you can explain to someone who does not want a workshop app. For a single bike and a simple habit — “tell me before the rubber or the chain is gone” — a small Android counter is a complete idea. Completeness here means the idea is finished, not that the bike is covered.

The marketing site goes further: fleet language, component swap. That is the shape of a bigger product. On a very new, small listing, those lines tell you what the maker wants the app to become. They do not by themselves make a catalog, a review set, or a widget. Until the app is no longer new, judge it as an automatic mileage counter with three loud parts, and treat fleet and swap as claims to re-check on the site and the store page when you install.

A finished native product

Tiiks is already a native app on iOS and Android, not a first listing. Automatic Strava sync writes distance onto each fitted component, not only onto three consumables. The parts catalog is a real library of models and specs. Verified rider reviews include real mileage. Service versus replace is a decision on that history, and the bike keeps the full record. That set is what “finished” means in this comparison: the surfaces exist on both phones, and the part is an object, not a warning label.

The home-screen widget is the other finished piece. You glance at status without opening a counter. That only works if the underlying object is already a bike with parts, not a warning list of three items. We built Tiiks as that object. A new counter can grow into it. It is not there on day one because the store page mentions a fleet.

Chain, pads, and tires versus every component

Three warnings are easy to understand and easy to ship. They also define the ceiling. A cassette that is eating a new chain, a rotor that is below minimum, a cable that is fraying, a bearing that is due — none of those are “chain, pads, tires.” If Velolog later warns on more slots, the comparison changes. Today the product you can describe with confidence is those three. Until then, a quiet app is not a healthy drivetrain. It is an app that was not asked about the other parts.

Tiiks tracks per-component mileage across the bike’s slots. The chain still matters. It is not the whole bike. When you replace one part, the others keep their own counts. That is what “full bike history” means in practice: not a single odometer with three alarms, but a set of parts that age together and get serviced or replaced on their own numbers.

Fleet language on a site versus a catalog in the app

A marketing site can say fleet and swap before the app has a parts identity. That is normal for a new product. It is also the moment riders get ahead of the software. You install expecting to search a model and read a review. You get a counter that knows Strava and three wear types. The disappointment is not that the counter is small. It is that the site described a workshop and the app is still a gauge. Re-read velolog.cc the day you install, not the day you first bookmarked it. New products move. Your expectation should move with the binary, not with the headline.

Tiiks puts the catalog in the product you hold. You assign a real part, you read specs, you read verified rider reviews with mileage. Swap and multi-bike stories only matter after the part is a known object. If Velolog’s site is what you want, check whether the installed Android app actually performs those fleet and swap flows before you plan a season around them. Do not take a new site as a finished workshop.

A new Android counter versus iOS, Android, and a widget

Velolog is Android. If you are on iPhone, there is no comparison to run. If you are on Android and you like living with a very new, small app, the counter may be enough for chain, pads, and tires. Tiiks is native on both platforms, with a home-screen widget. “Finished” here does not mean famous. It means the surfaces exist: catalog, reviews, history, service versus replace, widget, both stores. A thin new counter can be honest and still not be that set.

Auto mileage is the input, not the product

Automatic Strava mileage is the right input for any modern maintenance app. It is not, by itself, a maintenance product. Once the kilometers arrive, you still need somewhere for them to land, a decision about service versus replace, a history, and a way to see status without hunting. Velolog’s job today is to land those kilometers on a short warning list. Tiiks’ job is to land them on catalog parts and keep the bike’s history. If all you wanted was the input, the thin counter wins on simplicity. If you wanted the rest of the sentence, you want the finished app.

If three warnings are all you wanted

Velolog fits if you are on Android, you already use Strava, and the only alerts you will honor are chain, pads, and tires. A new, small app is acceptable because the job is small. You are not asking it to be a catalog or a widget. You are asking it to count. If that sentence is the whole brief you would give a friend, you do not need a finished workshop on day one.

Look elsewhere if you need iOS, if you care about components beyond those three, if you want a parts catalog and verified reviews, or if you want status on the home screen. Fleet and swap copy on velolog.cc is a reason to watch the product, not a reason to assume the workshop is already built. A thin counter that later grows is still a thin counter on the day you install it.

Questions we get

Is Velolog a new app?

Yes. Velolog: Bike Maintenance by 2Matter OÜ is a very new, small Android app with a site at velolog.cc. New means the feature list can move. It also means you should judge what is installed today — Strava mileage and warnings for chain, pads, and tires — not the largest sentence on the marketing page.

Does Velolog warn on more than chain, pads, and tires?

The product as described here warns on those three. If the listing later adds more slots, re-read it. Do not assume a cassette or a fork interval exists because a counter already knows Strava. Tiiks applies per-component mileage across the bike’s parts, then service versus replace on that history.

The Velolog site mentions a fleet and component swaps. Is that the app?

It is what the marketing site describes. On a thin, new counter, treat fleet and swap as a direction until you have run those flows yourself. A site can outrun a first Android build. That is common. It is not the same as a catalog, reviews, and a widget already in your hand.

If you want a finished native app on iOS and Android — catalog, reviews with mileage, full history, and a home-screen widget — that is the job Tiiks is built for.