An app for COVID-19 second wave: how we built a competitor to Headspace in 5 months

Since the beginning of the pandemic, the profitability of mobile health and fitness apps increased by about 280% around the world. These apps help people solve two problems in lockdown: lack of physical activity and increased level of anxiety. Let me tell you how we developed a breathing app for the second wave of Covid-19 with our client.

Reading time: 6 minutes

healthcare app development
Table of contents

App for the second wave of coronavirus

In May 2020 Caroline and Dominic from Singapore requested us to create UI and UX design for an app with breathing exercises. They had the expertise and a client base: Dominic was a fan of breathing practices, while Caroline was giving yoga and breath classes, and with the beginning of the pandemic she moved her classes online. We were a great match because of the past experience building a similar app for sleep. 

Every new mental health app has two giant competitors: Headspace and Calm. But these apps are focused on meditation and sleep monitoring. However, the breathing exercises are a part of meditation and are pretty important: breathing affects mood, health, and overall condition. Proper breathing can help to calm down at a critical moment, that’s why it’s better to create a mobile app for such courses to be always at hand.

Most of the competitors lacked breathing courses. Moreover, the content in our app was original, some exercises were unique — for example, the ‘breath pendulum’. The original content really motivated the client to develop the app.

The project budget was $30,000 funded from the client’s personal savings.

Turnkey project and a familiar technology stack

Dominic and Caroline asked us to create UI and UX design. Initially, they planned to hire another company for MVP development. But during phone meetings, we agreed that we can complete the whole project. What we included in the MVP: registration, watching courses, breath pendulum, push notifications, admin panel, and background playback. The users’ profile pictures, referral system, watch history, and offline mode were cut from the MVP scope.

Design: gray concrete and lush green

Caroline and Dominic had design preferences but they had no idea how to bring them to life. They wanted to combine lush green, gray concrete, and light wood. Photos became the core part of the design. The clients strongly opposed the illustrations because they were sure it wouldn’t work for the target audience. To make the app look more lively, we used images with nature patterns: water, plants, and rocks. We suggested two design options and the client loved one of them.

healthcare app development

Content types

At the MVP stage we included three types of content:

  • Breath-related articles that state how breathing affects our life;
  • Caroline’s audio and video lessons on breathing techniques that are easy to listen to on the go;
  • Breathing exercises.

The app creates general mixes and special daily playlists. They include lessons and exercises that are updated every day. All these sets are meant to solve three problems: deal with anxiety, recover muscles, set the right mood for a positive day.

healthcare app development

We paid a lot of attention to the audio lessons. In the app, they are divided by problems the user wants to solve.

healthcare app development

We developed the Pendulum mode. It’s a builder that allows users to customize practices for their needs. When users want to practice, they can create a custom exercise (choose breathing intervals: 5, 10, 15 seconds and duration of exercise), and the system will generate a soundtrack for the users so that they breathe in the beat of it.

healthcare app development

Team and technology stack

Our team consisted of three developers, a UI/UX designer, a manager, and a QA specialist. We used our usual technology stack — React Native + Nest.js. React Native is great for mobile app development, especially for an MVP. We used the React Admin library to create CMS — there were a lot of ready-to-use functions for creating an admin panel. But you have to be careful with this library: it requires perfect understanding, and not all the features work as it’s stated in the documentation. As usual: Stackoverflow and Github issues can help with it. However, it wasn’t the first time that we used this library, so we were ready for that.

To speed up, we took the best parts of the library and wrote some features by ourselves. We combined the parts — and it worked great.

See also  Photographers, $250,000 of investments, and 300 screens of 'some sort of' design. Purrweb’s case

Out-of-scope features and bypassing Instagram restrictions

At the development stage, we were worried that it will be difficult to play audio when the screen is locked. It’s important since we claim that the app allows users to ‘practice breathing on the go’ — the users should be actually able to go. It was another time we were happy with the chosen technology stack: it was easy to implement the feature thanks to parameters in React-Native-video library and we didn’t need to reinvent the wheel.

Using plugins to bypass restrictions

For the app launch, we needed to build a landing page to let users enter the store and download the app. We decided to use Gatsby — it helps to load websites 2-3 times faster compared to WordPress or Wix. We wanted to upload posts from the Breathmethod Instagram account to the landing page automatically. For that, we decided to use a Gatsby’s plugin — ‘gatsby-source-instagram’. But when we started coding, it turned out that the plugin only helps to get the list of posts, and it wasn’t enough: we wanted to integrate the full posts and keep the feed up-to-date. 

Then we used the plugin to get access to the Instagram posts, created an algorithm that sorts the last 10 posts, and implemented a slider. Then we connected our repository with the landing page to Netlify (service for hosting web apps) — it supports dynamic apps built with Gatsby. The problem is that Instagram doesn’t have webhooks which would inform Netlify of changes in the feed (there are changes, but Instagram has reduced functionality of the ‘gatsby-sourse-instagram’ plugin to fight with fakes — so we couldn’t monitor the new posts automatically). That’s why we used Zapier, a service that helps to automate Netlify’s deployments. This way we update the Instagram feed on the landing page on a daily basis and keep it up to date.

healthcare app development

Signing in with Face ID: easier than we thought

It was the first app in which we needed to integrate signing in via Face ID, so we thought it would be difficult. We wouldn’t call it a must-have feature for a breathing app, but the client insisted on adding it. We scheduled the work for two full days but managed to finish everything in one day: it turned out to be a lot easier. We made it so that the app can scan a device to find out whether it has a Face ID/Touch ID or not. If the device has Face ID — the app will offer to use it, if the device has Touch ID — the app will propose using the user’s finger instead, or if the device has nothing like this — it will ask the user to think up a simple code.

healthcare app development

Heartless conversion

In the end, we had trouble with another detail that wasn’t taken into account: the client wanted to receive money from the subscriptions in US dollars. But their Google Developers Console account was connected to a Singapore bank account — that’s why all income was converted into Singapore dollars. Creating a new account and linking it to the app might have taken time that we didn’t have. After the release, Dominic and Caroline changed the account at an easy pace.

See also  Cutting scope and fixing bugs in someone else’s API: how to finish a 3-month project in 2 months

Struggle with App Store and breathing with Apple TV

We developed a stylish and minimalistic app that is delivered through the SaaS model. The app has a trial version for one or two weeks and a subscription for a month or a year.

The app is now available on the App Store and Google Play, but we had to fight for publishing with Apple. For several weeks the store claimed that the app has no subscriptions. It often happens to apps with payments inside. We talked to App Store support multiple times and sent a lot of screenshots to prove that the app meets all the requirements.

We planned to release the MVP in three months but finished the work in five months. We ran out of schedule because it took the client a long time to prepare the content. Streaming in Zoom and improvising is one thing, but creating content ‘to last’ with professionally recorded video lessons (placing light, framing, editing) is different. We plan to further develop the app for Apple TV because our technology stack allows to reuse the existing code and make a TV version of the app fast. If Caroline and Dominic decide to make larger improvements, we’ll develop the users’ profile pictures, referral system, watch history, and offline mode.

How useful was this post?

Rate this article!

19 ratings, аverage 4.7 out of 5.

No votes so far! Be the first to rate this post.

As you found this post useful...

Follow us on social media!