Case study · Digital health · Product Engineering & QA

Four health apps, where a bug is a health risk.

Moberg provides mobile development and quality assurance for Sidekick Health across four apps — including Meno!, a medically verified product that shipped its first public release in 2025.

The client & the project

Digital therapeutics, so the QA bar is set by medicine.

Sidekick Health is an Icelandic digital therapeutics company, founded by two medical doctors, whose gamified digital care platform supports patients with chronic conditions — working with pharmaceutical companies and health insurers to improve outcomes and lower the cost of care. In this category, software is part of the treatment, and it is regulated and verified accordingly.

Moberg's role is mobile development and quality assurance across four Sidekick Health apps: Sidekick, the base app; Concierge Care, for the US market; Meno!, a medically verified product; and Ypso, built primarily with Ypsomed to support their SmartPilot medication devices and targeting medical verification.

The solution

Engineering and QA as one discipline, across four codebases.

The portfolio spans platforms and purposes. The base Sidekick app and Concierge Care serve care programmes at scale; Meno! is medically verified, with its first public release shipped in 2025; and Ypso pairs the software with Ypsomed's SmartPilot medication devices — an app whose counterpart is a physical device a patient depends on. Development work runs across Flutter, Swift, Kotlin and JavaScript, with Moberg engineers embedded in the product teams.

The interesting part of this engagement is not a feature — it is the rigour. For medically verified software, quality assurance is not a phase before release; it is a system of evidence. Test coverage, traceability from requirement to test to result, and disciplined release processes are what make the word "verified" mean something. Moberg's QA work is built to that standard, and the same habits raise the floor on the non-regulated apps too.

That standard shaped Meno!'s path to its 2025 public release, and it is the bar Ypso is being built against as it targets medical verification of its own.

The challenges

The honest part.

Stakes

A bug is a health risk

In digital therapeutics, a defect is not an inconvenience — it can touch a patient's care. "Probably fine" is not an acceptable test result.

Rigour

Verification is evidence, not a badge

Medically verified software demands traceability: every requirement mapped to tests, every release backed by a paper trail. The process must survive an auditor, not just a sprint review.

Breadth

Four apps, several platforms

Flutter, Swift, Kotlin and JavaScript across four products with different markets and regulatory postures — consistency of quality has to be deliberate, because nothing else provides it.

Hardware

Software meets a device

Ypso supports Ypsomed's SmartPilot medication devices. When the app's counterpart is hardware in a patient's hand, integration testing gets real in every sense.

The value

What it bought Sidekick Health.

Sidekick Health gets sustained mobile engineering and QA capacity across four products without diluting its own teams — and gets it at the standard its most demanding product requires. Meno! reaching its first public release in 2025 as a medically verified app is the concrete proof: the process held all the way from requirement to release.

The same discipline compounds across the portfolio. QA built for the medically verified case makes the base app, Concierge Care and Ypso steadier by default — and positions Ypso credibly for the verification it is targeting. Launch day is the easiest day; in regulated health software, every release after it has to clear the same bar.

KPIs & numbers

The shape of this one.

4
apps developed and maintained
1
medically verified app shipped — Meno!, 2025
Multi-platform
Flutter, Swift and Kotlin across the portfolio
Under the hood

The stack on this one.

Cross-platform

Flutter

Shared mobile codebases where one implementation should serve both platforms.

iOS

Swift

Native iOS development where the platform demands it.

Android

Kotlin

Native Android development, same reasoning.

Application

JavaScript

Application and tooling code around the mobile products.

← All stories

Get in Touch