Backlog
17Under consideration
Integration of Wahoo and Garmin APIs
Integrate Wahoo and Garmin APIs into Geer to allow direct syncing of ride data, component usage, and activity metrics without relying solely on Strava. Geer currently depends on the Strava API to import user activities and associate them with bike components for tracking usage and maintenance intervals. While Strava provides a solid infrastructure, it limits Geer’s accessibility to only Strava users. Many cyclists, especially those using Wahoo or Garmin devices, track their rides without syncing them to Strava—or prefer to keep their data within their native ecosystems.
Manual Input for Pre-Existing Usage Metrics
Allow users to manually set a pre-existing usage for components. That would be particularly useful when a user acquires a used component with known prior usage (e.g., a second-hand cassette for a trainer).
Multiple Languages
People might like to enjoy Geer in their own language. Please feel free to comment here, from where you are and what language you speak 🙂
Inventory Management
Allow users to track spare parts inventory (chains, cassettes, brake pads, tubes, etc.) stored at home. The app would help users know what replacement parts they have available before a component needs servicing. Cyclists with multiple bikes or who buy parts in bulk may lose track of which spare parts they have in stock. This could lead to: Ordering parts unnecessarily (duplicates) Running out of critical parts when needed Inefficient use of storage space Add an "Inventory" section where users can: Log spare parts with quantities (e.g., "3× Shimano 11-speed chains") See compatibility with their bikes Get notified when inventory runs low Track which parts are installed vs. in storage
Consider the altitude for break system wear
Enhance the accuracy of brake pad and disc wear predictions by factoring in altitude data from Strava activities. This will allow Geer to better estimate brake pad mileage, especially for users who ride frequently in mountainous or hilly terrain. Current brake pad mileage estimates are primarily based on distance or time. However, riders who accumulate mileage in mountainous areas experience significantly more braking — especially on long descents — which leads to faster pad wear. This results in underestimating the actual wear for those riders. Incorporate total elevation loss (descent) as a factor in brake pad wear calculations. Activities with high descent values should contribute more to brake pad wear than flat rides, even if the distance is identical. This could be implemented by introducing a weighting system based on vertical meters descended.
Add bikes manually without Strava
Adding bikes manually outside of Strava would be very helpful to track maintenance of bikes from family members who are not on Strava. The current mileage needs to be added manually then, but that is OK.
Component Nesting (Grouping)
Request Enable hierarchical component relationships where parts can be installed inside other components (e.g., tires on wheels, cassettes on rear wheels, brake pads in calipers). When swapping the parent component, all child components move together. Problem Many components have lifecycles closely tied to parent parts. Currently, users must manually track and swap each individual component, which doesn't reflect real-world usage where entire assemblies are swapped together (complete wheelsets, cranksets with chainrings, brake calipers with pads). Solution Allow components to be installed inside other components (recursive nesting) Child components inherit usage from parent component's installation periods Swapping a parent component automatically moves all child components Common groupings: wheelsets (rim, hub, tire, cassette, rotor), cranksets (cranks, chainrings), brake sets (caliper, pads, lever) Usage tracking calculated based on parent component, bike, and installation dates
Ideal psi/bar displayed based on component setup
As a cyclist with different bikes and tyre formats (gravel, road, etc., with different widths), I always need to refer to my Excel sheets to check the ideal pressure for each tyre in different conditions (wet/dry). A preconfigured setup based on all the tyres hard-coded at bike level would be beneficial.
Inspection Prediction
Introduce a smart Inspection Prediction system that notifies users when it’s time to check or service components – but not in isolation. Instead, Geer should intelligently bundle upcoming maintenance tasks and surface them at just the right time, so users can take care of everything in one go. By grouping upcoming tasks and predicting when a combined inspection makes sense (e.g., before a race, after a long trip, or based on usage patterns), Geer becomes a proactive assistant rather than a reactive checklist.
Scan-to-Log Maintenance via QR or NFC Tags
Imagine placing a QR code or NFC tag on your chain waxing pot, brake bleed kit, or tool box. Every time you perform a maintenance task—like waxing your chain—you simply scan the tag, and Geer automatically logs the service. This feature would allow users to link physical tools or workspaces to digital service entries in Geer. It reduces friction, avoids forgotten log entries, and brings physical-world interactions into your bike maintenance tracking.
Next up
2Committed and queued
Display Total and Per-Year Mileage for Each Bike
A user suggested enhancing the bike overview by including both the total mileage and the mileage per calendar year for each bike. This would provide valuable insights into usage patterns over time and improve the overall utility of the bike tracking functionality.
Establish more ride types
At the moment, you can assign components to indoor and outdoor ride types. A user requested to add more ride categories like gravel and all the others, which will also make setups like multiple wheelsets much easier to manage. Expand the existing ride category system (currently indoor/outdoor) to include: Additional ride types (Ride, Mountain Bike Ride, Gravel Ride, E-Bike Ride, E-Mountain Bike Ride, Velomobile) Assign components to specific ride categories Automatic tracking based on ride type from Strava
In Progress
1Actively being built
Done
15Recently shipped
More than two Service Intervals
Many riders out there have more than two maintenance tasks for some of their components. Such as cleaning, waxing and replacing their chain.
Hide retired Strava bikes
Bikes marked as “retired” in Strava are still being displayed in Geer. Since retired bikes are no longer in active use, they should not appear in the bike selection or component tracking views within the app. That would improve clarity and usability by reducing clutter and focusing only on currently active bikes.
Indoor specific tracking
Being able to mark components as indoor only would enable users to track certain components only when they complete indoor activities in Strava.
Bike Setup Onboarding
Right now, the initial setup can feel manual or overwhelming. Introduce an engaging and efficient onboarding experience to help new users get started with Geer by setting up their bikes and essential components in a quick, playful, and guided way. Ideas: Essential components as presets. Maintenance task suggestions that make sense
Ridden distance on main page instead of distance left.
Ridden distance on main page instead of distance left. I found the old values better, or at least add an option to change it.
Bundle Mails
When several components reach an interval I get a mail for each component at the moment. It would be nice to bundle these notifications into one mail in that case.
Dark mode Implementation
Nothing to describe here 🙂 I'd like to enjoy this app also in dark as I do with many others too.
Geer should track Strava activity tag for flagging an indoor ride
I think Strava has changed this at some point, but my rides do not get properly tracked in Geer if using an indoor only part. I do have a bike which I also run outdoors, so there is no “indoor” bike in Strava. However Strava adds a tag to the activity which tracks it as indoors. But it seems that Geer is not using that? At least the part which I have set to indoor only does not get any usage. Thanks, Tobias
Add description/notes for each component
In the current system, the user can rename a component when it is added (or edited). However, it is not possible to add a general description for the component, such as purchase date, serial number etc. Similar to a completed maintenance action for a component, where a notes section is available to the user, a free text element should be added at component level in addition to the component name.
Suggested Service Intervals Based on Component Type
Implement a feature that provides tailored service interval suggestions based on the specific type of component. This would assist users in determining when servicing a particular component is most appropriate or necessary. For example, different components (e.g., chains, cassettes, or bearings) have varying maintenance requirements, and having recommendations would simplify maintenance planning.