- Wearable wellness device
- iOS & Android
DNA Vibe case study
A mobile app to turn on and manage the DNA Vibe device.
- Platform
- iOS & Android
- Features delivered
- 5
- Lead stack
- Node.js, Flutter
Overview
A mobile app to turn on and manage the DNA Vibe device.
DNA Vibe is a wearable wellness device, delivering a proprietary blend of signaling protocols in low-level red light, near-infrared and magnetic. The safety and efficacy of these products have been well established through multiple double-blind clinical trials and FDA approvals.
DNA Vibe provides a mobile application for their device so users can turn it on and manage the device, set session parameters, run sessions, and provide feedback.
- Category
- Wearable wellness device
- Platform
- iOS & Android
- Built with
- Node.js
- Flutter
- LoopBack
- MongoDB
- PHP
- NGINX
At a glance
- 05Problems solved
- 05Features delivered
- 02Platforms
- 06Technologies
- ClientFlutter
- ServicesNode.js, LoopBack, PHP
- DataMongoDB
- Cloud & hostingNGINX
The problem
- 01
Client wanted the development team to understand their product and provide a solution for managing the wearable wellness device with the help of an app.
- 02
Client was concerned about the technology used to build this application.
- 03
Client required a unique ID to get bonded with each device so that the same device can’t be operated by two different accounts.
- 04
Client wanted to implement different signal levels that show within the app so the app could automatically be stopped if users tried to change the values mid-process.
- 05
Client wanted to have the functionality of tracking sessions run by users to help the team of the client review the provided feedbacks.
The solution
Core features
- 01
We understood the functionalities of the wearable wellness device during the requirement gathering phase and provided the confidence to the client by documenting the complete process flow with an architecture diagram.
- 02
We used the Flutter technology to achieve both iOS & Android apps along with the Nodejs in the backend. The client was impressed with our usage of Google’s mobile UI framework that provided fast & expressive apps on both iOS & Android.
- 03
We mapped each device with the unique ID from the backend which helped the client avoid the same mapping of a single device with different accounts. For this, we asked the new user to provide the unique ID to link that device with their account.
- 04
We successfully implemented the signaling matrix for receiving the responses from the devices and to achieve this matrix functionality, we have used Bluetooth Low Energy (BLE) technology. For this, we have used the library from the Flutter framework so that the device can communicate with the mobile application.
- 05
We provided a timer functionality for tracking the time spent by users on the app and for helping track how long users have worn that device.
Under the hood
- 01 · Client
What people touch: the product on iOS & Android.
- Flutter
- 02 · Services
The logic behind it: APIs, business rules and integrations.
- Node.js
- LoopBack
- PHP
- 03 · Data
Where the product keeps its records.
- MongoDB
- 04 · Cloud & hosting
How it is served, scaled and kept running.
- NGINX
- One Flutter codebase serves the mobile apps, so every release reaches iOS and Android together.
Build your team
Share where the roadmap is blocked and the capabilities you need. We’ll map a practical team and delivery model.