Athle-Sense is a wellness tracking app designed specifically for athletes. The app helps athletes monitor their physical and emotional wellness on a daily basis, providing valuable insights into when they may need to add extra training sessions or take a break to avoid overexertion.
With Athle-Sense, athletes can track various metrics such as sleep quality, energy levels, mood, hydration, and more. They can also set wellness goals and receive personalized recommendations based on their individual needs and performance.
In addition to the standard features available to individual athletes, Athle-Sense also offers a paid Pro version that allows coaches to create groups of athletes and monitor their wellness for a defined period of time, such as during a competition season. This allows coaches to make data-driven decisions about playing time and advise their team on how to improve wellness.
- The developer of Athle-Sense app had a challenging experience when developing the app. Initially, they found it difficult to determine the requirements before starting the development process, as the team kept coming up with new ideas and changes. This led to significant feature creep, especially in how the data would be visualized.
- Developing the app within a short timeline was also challenging, as the initial timeline seemed sufficient but the changing requirements made it difficult to make progress. The review process also took longer than anticipated, which made the timeline even tighter. The developer realized the importance of user testing, as testing the app with real-world situations would have helped to identify and address issues such as firebase query limitations.
- He also learned that getting the main functionality of the app often doesn’t take too long, but it’s essential to pay attention to finishing touches like disabling buttons when loading, allowing users to change their passwords, and providing onboarding. These finishing touches took a surprisingly long time in the second version of the app.
- The developer advised starting with theme constants as early in the development process as possible. This would have made it much quicker to add a dark theme later on in the second version.