Project challenge
Cyclists, both amateurs and professionals, need to keep their bicycles in perfect condition to safely take part in races and challenges and achieve the best possible performance. One of the fundamental aspects of ensuring this is proper maintenance control, especially tracking the installation of each component. This control makes it possible to anticipate the ideal time for replacements, helping to prevent accidents, reduce long-term costs, and extend the lifespan of parts.
In response to this need, the idea emerged to develop a product dedicated to bicycle maintenance management.
The proposal is to create an application that allows users to record important information about each component, such as installation date, mileage, place of purchase, and price paid. With this, cyclists will be able to better plan their maintenance, compare prices, and replace parts at the right time—based on real data and usage history.
In this article, I will present more details about the developed application, its intentions, target audience, and objectives, with the goal of contributing to the cycling community so that riders can cycle more—and more safely.
///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
Start of Development
The starting point of the development process was conducting research aimed at better understanding users: how they behave, which applications they already use, what their daily routines are like, and what barriers everyday life imposes on the practice of cycling.
Identified Problem
During this process, a common issue became evident: the lack of control and record-keeping of data related to bicycle equipment. This absence of information compromises the optimal use of components.
A worn-out part, for example, can negatively affect the condition of other components—leading to unexpected issues, unplanned visits to the mechanic, last-minute purchases, excessive expenses, and a reduced lifespan of bicycle parts.
Benchmarks
Existing applications on the market that, in some way, address cycling-related information were analyzed. However, most of them primarily focus on the user as an athlete—their performance metrics, personal goals, and social networks, leaving the equipment in the background, without offering a proper space to store relevant data.
The evaluated applications were:
-
Strava
-
Garmin Connect
-
Intervals.icu
-
TrainingPeaks
-
Cannondale
All of them, except the last, are widely used by the cycling community. However, their focus is on human performance, with no specific features for bicycle maintenance or equipment tracking.
Strava, for example, allows users to select which bike was used in a given activity, but does not provide space for comments, reminders, or detailed records about components.
The Cannondale app, on the other hand, despite having an equipment-focused approach, is limited to users who own Cannondale bicycles. This restriction significantly limits its practical and broad use, as cyclists often own bikes from different brands.
To recall purchase dates and amounts invested in parts, cyclists frequently rely on bank statements, emails, or even conversations in messaging apps such as WhatsApp, highlighting the lack of a practical and efficient system for organizing and managing this type of information.
Benchmark Summary
It would be beneficial to integrate the analyzed applications (which focus on personal data) with the application proposed in this project (which focuses on equipment). One would complement the other, keeping the entire process aligned and well documented.
CSD Matrix
To establish clear direction for user research, a hypothesis analysis was carried out using the CSD matrix, outlining what we already know, what we assume, and what we need to discover.
User Research
To understand users’ habits, aspirations, and how they relate to the maintenance of their equipment, both qualitative and quantitative research methods were conducted. A structured questionnaire was used as the main research tool, including objective questions and an open-ended section for opinions at the end of the interview. Below are some of the key points analyzed:
Fifteen people were interviewed during the process; all of them practice or have practiced cycling at some point in their lives. The survey results show that most participants are between 36 and 45 years old (63.6%), identify as male (54.6%), are currently employed (72.7%), have been cycling for at least three years (81.9%), use their bicycles both for leisure and sports training (54.5%), do not actively record maintenance or equipment replacements (81.8%), own two or more bicycles (81.8%), consider it important to track the mileage a component has accumulated (95%), and find it interesting or very interesting to receive maintenance alerts for their equipment (100%).
Presentation of Results:
Highlights:
High participant engagement: Many participants spontaneously contributed observations about their routines and challenges related to maintenance.
Relevant suggestions: Some participants pointed out specific types of information they would like to record, such as chain replacement dates, component brands, the location of the last service, and other technical details.
Interest in personalized alerts: A striking finding was that 100% of respondents considered receiving maintenance notifications to be “interesting” or “very interesting.” This clearly demonstrates interest in solutions that help organize and anticipate bicycle care.
Insights:
The research results not only validate the app proposal but also broaden the perspective on its features and growth potential.
Beyond recording technical information about equipment, participants showed openness to complementary features such as:
-
Partnerships with bike shops and specialized workshops, which could offer exclusive benefits, personalized reminders, or even integrated maintenance services;
-
Integrations with other popular apps, such as Strava or Garmin Connect, allowing automatic synchronization of usage and mileage data;
-
Educational content and preventive maintenance tips, especially helpful for beginner cyclists to better care for their bikes, avoid premature wear, and promote greater safety.
These insights point to clear paths for the evolution of the product, turning it into a comprehensive support platform for cyclists’ equipment.
///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
Based on the previous stages - user profile analysis and the identification of their needs, frustrations, and behaviors - a persona was developed to guide the app’s development in all aspects: features, tone of voice, design, usability, and value proposition.
Thus, Bruno was created, a character who represents the platform’s core target audience.
Personas: a fictional character representing a group of real users.
Empathy Map: a visual tool used to understand the user.
Journey: Mapping behavior in response to a situation.
Proposed Solutions to Mitigate Pain Points:
Based on the analysis of the identified pain points and needs, specific features were proposed to make the app a useful, practical, and comprehensive tool for cyclists.
-
A channel to record bicycle maintenance and service data
-
A channel with customizable alerts about equipment usage
-
A channel to track bicycle-related expenses
-
A channel to record the place and cost of equipment purchases
-
A channel with tips about races and equipment maintenance
Prioritization Grid of the Proposed Ideas:
Based on the research and ideas, the development of the channels was initiated.
///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
The Proposal
To create an intelligent channel for controlling and organizing information about bicycle components, enabling cyclists to:
Schedule maintenance, avoid emergency replacements, compare purchase options, and perform substitutions at the right time. A bicycle equipment management tool that puts cyclists in control, based on real data and historical usage.
///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
Start of Development and Wireframes
To take the first steps in developing the planned channel, low-fidelity wireframes were created with the goal of structuring navigation and organizing BiciFit’s main features in a clear and intuitive way.
The first stage was the development of the home screen, which simply presents the main paths the user can follow. From this screen, different flows were mapped to represent the key actions within the system. Among the possible flows, two were prioritized for the initial prototyping phase: adding a new bicycle and registering a maintenance service.
These initial flows served as a foundation to test the navigation structure, validate interaction logic, and ensure that the app was accessible and functional from the earliest sketches.
Task A: Adding a New Bicycle
A flow that allows the user to register a bicycle in the system.
-
Add a bicycle to the channel;
-
Fill in the information for the added bicycle;
-
Complete the task by saving the new bicycle.
Task B: Registering a Maintenance Service
A flow for adding a new maintenance service performed on the bicycle.
-
Add a general maintenance service performed on one of the bicycles;
-
Enter general comments, the date the service was performed, and the cost;
-
Enter specific information about what was done to the rear wheel;
-
Finish by saving the maintenance record.
After the development of the low-fidelity wireframes, usability tests were conducted with real users to evaluate whether the app’s functionalities could be performed intuitively.
Aspects analyzed: task completion and completion time, level of difficulty, flow suitability, identification of negative points, and a final space for open comments.
Example of how the tests were conducted:
Data from the tests performed :
Task 1. Add a new bicycle.
Task 2: Record Information for a New Bicycle.
Task 3: Add a Maintenance Service to an Already Registered Bicycle.
Task 4: Add Specific Component Information to a Maintenance Record.
///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
After the research phase, the process moved on to a more high-fidelity creation of the channels, exploring the visual concept and brand identity, UX writing, color palette, and other elements. In addition to the smartphone version, specific versions for Web and Tablet were created, expanding the app’s reach and accessibility. This stage took into account the improvements identified during usability testing.
Conceptual moodboard: exploring ideas and directions to be taken.
With the concept and a color palette defined, a Style Guide was developed to be applied throughout the channel development, aiming for harmony and simplicity across elements and colors.
Style Guide: a guide to be applied across the developed screens.
///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
High-Fidelity Prototype
Several screens were developed to accurately illustrate the experience users will have when using the app. The main goal of this prototype is to validate usability, assess the clarity of navigation and content, and ensure visual consistency.
///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
Some App Flows Developed
Task A:
Add a new bicycle to the app.
Task B:
Open the page of one of the bicycles and add a completed maintenance service with specific information about the wheels.
///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
The development of BiciFit was guided by the needs of its target audience, going through all stages of UX and UI. From the initial exercises to the final project presentation, it is rewarding to see the product’s evolution, which was designed to meet real cyclists’ needs and bring more practicality to users’ daily routines.
We would like to thank everyone who contributed throughout this process—by participating in research, providing feedback, and offering support. This exchange was essential for the product to reach its current form.
The pursuit of empathy with the user guided all phases of the project, always placing them as the top priority. As a result, BiciFit aims to be more than just a functional solution, fulfilling its purpose of offering greater safety, convenience, and cost savings to its target audience.
