---
title: "Medicaid Member Experience PWA | Smart Data"
url: https://www.smartdata.net/case-studies/medicaid-member-experience-pwa
description: "Smart Data has delivered a React PWA for 22+ months for a large Medicaid managed care organization, bringing member mobile and portal into one experience."
source: "Smart Data (smartdata.net). Markdown copy of the page; the HTML page is canonical."
---

# Replacing a legacy mobile app and member portal with a single progressive web application for Medicaid members

Smart Data is the engineering partner on a 22-month React Remix PWA for one of the largest Medicaid managed care organizations, consolidating member experience across mobile and portal.

Built on Azure React Node.js

Industry

Healthcare, Medicaid managed care

Engagement

Custom Development

The client is one of the largest Medicaid managed care organizations in the country, serving millions of members across multiple states. Their member experience was split across two surfaces: a legacy mobile application and a separate member portal. Members had to choose which surface to use, the experiences didn’t share state cleanly, and certain member-facing features were duplicated across both with their own bugs and gaps.

Smart Data is the engineering partner on a multi-year build of a React Remix progressive web application that consolidates the member experience into a single coherent surface, with internal microservices on Azure providing the integration layer to the client’s existing data systems.

## The challenge

The pre-PWA member experience had four core problems holding the platform back.

- Member experience was split across two surfaces (mobile app + member portal), forcing members to choose which to use
- Features were duplicated across both with their own bugs and gaps, and the surfaces didn’t share state cleanly
- State agency contracts require specific member-facing capabilities with detailed compliance and feature obligations
- The platform had to grow with the organization’s plans through at least 2027, not be a one-time build

Context: Member-facing platforms in regulated healthcare don’t get built well in three-month sprints. The work required sustained engineering investment and a team setup where decisions could move fast even with heavy compliance constraints.

## The solution

Smart Data and the client scoped a long-running engagement structured as integrated staff augmentation rather than a fixed-price project. Six Smart Data developers work alongside six client-side developers, two IT managers, a designer, five product owners and a scrum master. In practice, the team operates as one.

- React Remix progressive web application as the unified member-facing front end
- Mantine UI component library providing a consistent design system
- Internal microservices on Azure (Azure Functions and container apps) handling integration between the PWA and the client’s data systems
- Service Bus queues coordinating asynchronous workflows
- Custom Strapi CMS extensions so non-engineering content owners can manage member-facing content directly
- Okta identity integration for member authentication, plugged into the client’s existing identity infrastructure
- Database optimization across Azure SQL and MongoDB, with member data living across both relational and document stores
- Feature flags via Flagsmith for incremental rollouts; MixPanel for member behavior analytics; Splunk for operational logging and observability
- Single-codebase delivery that solved the dual-surface problem at the architecture level

The PWA architecture and Flagsmith feature-flag system together give the client the ability to run different member cohorts on different feature sets simultaneously, without forcing every member onto a single version of the application. New features can be rolled out incrementally, A/B tested across cohorts or rolled back for specific populations without an app store release cycle or a multi-version maintenance burden. Concurrent version support is built into the architecture, not bolted on.

Process note: The PWA approach mattered because it solved the dual-surface problem at the architecture level. One codebase serves the experience that used to require a mobile app and a separate web portal. Members get a coherent experience whether they’re on phone, tablet or desktop.

## The results

The platform consolidation delivered four operational improvements:

Consolidated a fragmented two-surface member experience into a single coherent PWA

Met state agency contractual feature obligations across the unified codebase

Replaced legacy app store release cycles with continuous shipping through PWA delivery

Built a long-term member experience foundation that grows with the organization’s plans, not a one-time deliverable

The kind of engagement where engineering depth and continuity matter more than a fixed scope. A 22-month-and-counting build with a roadmap into 2027.

Client

Healthcare Insurance

Platform and technology

- React
- TypeScript
- SQL Server
- Azure
- MongoDB
- Node.js
- Next.js
- Microservices

## Working on something similar?

Tell us what you are building and what it has to connect to. Here is what happens after you reach out.

### A short call about the work

What runs today, what needs to change and the date you are working toward.

### An engineer looks at what’s running

Scope comes from your systems as they are, before anything is priced.

### You get a written proposal

Covering scope, team, approach and price.

[info@smartdata.net](mailto:info@smartdata.net) [(937) 886-9166](tel:+19378869166)
