Mobile apps for wearables and IoT devices.

We built RE-AK's four-sensor research app from an empty repository and cut ANRs by more than 90% in Trackforce's guard app. We also put senior engineers inside existing teams, usually within two weeks of agreement.

Three screens of a companion app: live heart rate from a wearable with sync and firmware status, the connected boards and wearables, and live accelerometer data from an STM32 board

Hardware

From phone to chip

We build the app side of Bluetooth LE and Wi-Fi hardware, from finished wearables to bare boards.

An ESP32 development board
ESP32
A phone app listing a connected ESP32 board and a streaming STM32 board, with the wearables below
An STM32 Nucleo development board
STM32 Nucleo

Device types from client apps in the field

What we work on

We take on three kinds of mobile problem

Each one has its own site with engineering notes and the client work behind it.

01

Connected devices and neurotechnology

Apps for Bluetooth LE wearables and sensors, USB cameras and Wi-Fi boards. They keep recording with the screen off and recover data the connection dropped.

Explore connected-device engineering
Client work
RE-AK Technologies and CLEIO
Result
4 sources recorded together, screen off, for up to 4 hours
02

Field systems

Guards lose signal in basements and parkades, sometimes for months. We can design apps that save work on the device first and sync when the network comes back.

Explore field systems
Client work
Trackforce, the TrackTik app guards use every shift
Result
The offline download kept within the app's memory limits
03

Production maintenance

Much of our production work has been on apps other teams built. We trace crashes and freezes to the cause and fix them path by path.

Explore production maintenance
Client work
Trackforce, an app another team built
Result
ANRs cut by more than 90%

Selected work

Client work in these areas

All case studies

Engagement models

Two ways to bring us in

Dedicated engineering team

Best if you need one team to own a new build or an inherited app.

Discuss dedicated delivery

Embedded engineering

Best if you have more roadmap than senior engineers.

See how embedded engineering works
Who owns what
We own the app from architecture to release, then hand it to your team.
You keep the roadmap and technical direction. Senior iOS or Android engineers join your repository and sprints.
Commitment
A timeline and scope after a short discovery.
20 or 40 hours a week, with a three-month minimum.
Start
Once we agree what we will and won't own.
Typically within two weeks of agreement.
Client example
RE-AK: from an empty repository to field use within a month, then handed to their engineer.
CLEIO: a senior Android engineer inside their team. Trackforce: we led three of their developers on stability work.

Client references

GabrielDirector of Software Development, CLEIO, Quebec

Embedded engineering on a companion app for a wearable EEG device.

“…a dependable, communicative, and professional consultant…integrated smoothly into the project team, ramped up on the project context efficiently, and consistently delivered against the cadence set by the client.”
Read the CLEIO case study
Frédéric SimardRE-AK Technologies, Quebec

Vizia, a connected neurotechnology application for multi-sensor data.

“Great job Zawar Nadeem, I'm a very satisfied customer, thank you for making the Vizia Mobile app.”
Read the RE-AK case study

Contact

Tell us what's going wrong

Send the device and its spec, the phones you need to support and what's failing. If you need an engineer in your team, send the role and the start date. Engagements are available to teams in Canada and the United States.

Book a 30-minute technical call

Zawar Nadeem Founder · Principal Android Engineer Replies to enquiries within one business day and takes the technical call.
Email
info@devsflow.ca
Best for project briefs and detailed questions
Call directly
+1 (514) 963-3744
Eastern time, Monday to Friday
Where we are
Toronto-based team
Canadian working hours, with overlap for US teams arranged by engagement

Photo credits: ESP32 from Pexels. STM32 Nucleo by SparkFun Electronics, CC BY 2.0. Backgrounds removed.