Got an idea, a pet peeve, or a "why doesn't it just…"? Drop it here, upvote what others posted. Geer is built by cyclists in the open. Your votes shape what we ship next. And yeah, we actually read this stuff.
In Progress
Assigning Bike Components to Multiple Bikes
Enable users to assign bike components to multiple bikes, enhancing flexibility for tracking shared components across different setups. Uses cases: Shared Components Across Bikes: Users who share components such as a wheelset between two or more bikes (e.g., a road bike and a gravel bike) can accurately track their usage without duplication or manual adjustments. Single Bike with Separate Strava Bikes: Cyclists who have split their single bike into two bikes in Strava (e.g., one for outdoor rides and one for indoor trainer sessions) can still track shared components like the chain or cassette seamlessly.
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.
Planned
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.
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.
Price comparison of parts
Show price comparisons and deal alerts for bike components directly in the app. When a user views a component (chain, cassette, etc.), show current prices from multiple retailers and notify them when parts go on sale. Users need to: Replace worn components but don't know current market prices Miss out on sales/deals because they're not actively shopping Waste time manually checking multiple bike shops Buy at inopportune times (paying full price when deals are available) Especially problematic when: Component wear is predictable ("I'll need a chain in 3 weeks") Users could wait for a deal if they had advance warning Bulk buying would be cheaper but users don't think about it Basically an idealo function build in.
Filtering by Component Type
Currently, users can filter their components by bike. However, it would be helpful to also filter by component type, regardless of which bike they’re assigned to. For example, this would give me a much clearer overview of all my chains.
Planned
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
Data Export (CSV, Excel, ... )
Allow users to export all their data (bikes, components, maintenance history, mileage) as CSV or Excel files. This ensures data portability and enables users to create backups independent of the app.
Strava API + Weather API for more accurate chain wax intervalls
Theoretically, I could obtain GPS/route data from Strava's API and cross-reference it with weather and surface data (via other APIs) to create a more accurate result on when to replace chain wax.
AI Look
Please make this app not look like every other vibe coded AI “design”. It’s not just your app, but also the website and even your personal website. I like the idea, but this has so much more potential and depth to offer. Give your customers a bit more quality and a unique experience.
Quick-swap for parts you rotate (chains, etc.)
Some riders rotate multiple chains: one on the bike while the other gets waxed. Right now swapping them takes two separate actions: open chain 1's detail page, uninstall it, then find chain 2 and install it. Idea: a single "Swap" action. Pick the part that's on the bike, pick the spare that replaces it, done. The old part goes back to your shelf with its wear data intact, ready to come back next rotation. Chains are the obvious first case, but the same thing would work for any part people keep spares of. Cassettes, tires, wheelsets.
Bulk install and uninstall
As an example, I have two wheel sets. I track cassette wear (more like cassette mileage, I wax my chains, wear takes very long) and tire wear on both. On one wheelset, the rear wheel is newer than the front wheel. So far, I need to go through each component and install and uninstall each. A feature to bulk install or uninstall several components at once would be a convenient addition.