Weight loss mobile app
About a project
When dealing with startups, we are usually very picky. Our priority is to cooperate with startup founders, who not only have a sustainable budget for a project, but rather a pain-relieving solution on their minds. This case describes our cooperation with one of such startups.
We partnered with a well-funded startup in the health-related sector. The Client came to us with an idea to build a weight-loss mobile application based on personal metrics. The project had its challenges and nuances, which only strengthened our interest in it.
We needed to collect and analyze personal health metrics fed by wearable devices. That is, for instance, the number of calories spent based on kilometers biked, walked, or went up/down the stairs, heartbeat information, active and resting heart rate, weight changes, and other metrics.
The project required integration with wearable devices directly (such as the Garmin API, Strava, and other proprietary devices with publicly available APIs).
Our goal was to collect the information in centralized storage, analyze it, and produce historical and predictive analytics.
The Client also wanted us to set up a communication channel for weight-loss consultants and their patients via internal text messaging, audio messages, and video calls regarding weight-loss progress. Our Client would also like these sessions to be recorded for later use.
We provided a team of dedicated developers, QA engineers, and an architect. Then, the Client and our UX/UI designer met personally here in Canada. Together, we analyzed all the requirements and started to produce the UX/UI screens and prototypes. During the face-to-face meetings, we were engaged in active dialogue, helping our Client to understand and prioritize the project's needs. Working together, we built an efficient interface.
The personal meetings in Toronto allowed us to create some UX/UI right there before the Client's eyes, so there were no grounds for differences of opinion on the upcoming development processes. It also helped us to assemble the team in the shortest possible time.
We left our internal development process unchanged - an 8-hour working day, 5 days a week. As a result, our team architected a cross-platform mobile app, integrated it with a data-driven backend and wearable 3rd-party devices, and built reporting around it. Synching data among all the devices was an exciting challenge, which we managed to overcome due to the effective architectural decisions. We also developed a strategy for QA and automated testing via TestCafe, Browser stack, and automation for API testing via SoapUI and automated runs.