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.







