Member ID cardYour coverageID •••• ••••Add to Apple Wallet
Claim submitted
Processing
Paid
Find a doctor
Apple Wallet ID cardsWCAG 2.1 AAone hybrid codebase
Overview
Overview
Blue Cross Blue Shield of Michigan serves 5M+ members across the state.
I led frontend development for the member app — claims tracking, coverage lookup, virtual ID cards, prescription management, and in-network provider search — rebuilding a slow legacy Cordova app into a modern hybrid mobile experience on IBM MobileFirst, with WCAG 2.1 AA accessibility baked into the component layer.
The challenge
Healthcare apps serve the widest audience in software.
The legacy Cordova app was slow, had limited native capability, and members couldn't find basic plan information, which translated directly into support-call volume. Rebuilding natively wasn't an option on the budget; compromising on accessibility wasn't an option at all.
Every memberyoung families to elderly users
Findable plansthe real support-call driver
Accessiblenever optional
The solution
Hybrid, accessible and built around member intent.
Delivered a hybrid app with Ionic + AngularJS on IBM MobileFirst that felt native on both iOS and Android from a single codebase. Restructured the information architecture so members could actually find plan details, shipped Apple Wallet virtual ID cards (the #1 field request), and enforced WCAG 2.1 AA at the component primitives so every new screen inherited accessibility automatically.
Accessible primitivesClear IAWallet ID card
Architecture
Hybrid shell, enterprise core.
A hybrid mobile app with Ionic and AngularJS running on IBM MobileFirst for enterprise auth, API gateway, and feature flags. Accessibility is enforced at the component layer — not bolted on at QA.
Client
Ionic
AngularJS
TypeScript
SCSS design system
Mobile Shell
Cordova plugins
Apple Wallet passes
Touch ID / Face ID
Native-feel UI
Platform
IBM MobileFirst (auth + API gateway)
Push notifications
Feature flags
Versioned APIs
Backend
Node.js + Express
MongoDB
Redis cache
Encrypted storage
One request, start to finish
Member logs in through IBM MobileFirst and gets a scoped token
Claims and coverage are fetched with a Redis-backed cache
Virtual ID card is added to Apple Wallet via a Cordova plugin
Prescription refills are scheduled and synced in the background
In-network provider search runs with geolocation and specialty filters
Decisions
Five calls and why I made them.
Call 01
Ionic + Angular over a full native rewrite
Serving 5M diverse members on a fixed budget. Hybrid delivered 90% of native feel at roughly half the engineering cost, with a single codebase across iOS, Android, and web. A native rewrite would have shipped half the features in the same time.
Call 02
IBM MobileFirst as the backbone
Enterprise auth, API gateway, feature flags, and push — all regulatory-friendly — out of the box. Let a small frontend team spend its time on member experience instead of rebuilding the security stack from scratch.
Call 03
Accessibility-first component library
5M members includes many elderly and vision-impaired users. WCAG 2.1 AA baked into primitives (inputs, buttons, navigation) meant every new screen inherited accessibility automatically, instead of being audited and patched at QA.
Call 04
Virtual ID cards in Apple Wallet
The most-requested feature from the field. Apple Wallet integration eliminated the #1 support-call reason (lost or forgotten physical card) and made the app the first thing members opened at the doctor's office — every other feature rode on that retention lift.
Call 05
Rebuild the information architecture, not just the UI
Members couldn't find plan info — a UI refresh alone wouldn't fix it. Restructuring the IA around member intent (what am I covered for, how much does it cost, where do I go) drove a 30% drop in support calls independent of the visual rebuild.
Reflections
What I took away.
Information architecture is the real redesign
Leadership wanted a visual refresh. The actual problem was that members couldn't find plan information, and a fresh coat of paint wouldn't fix that. Restructuring the IA around member intent — what am I covered for, how much does it cost, where do I go — drove the 30% support-call drop. The visual rebuild is what got photographed; the IA rebuild is what moved the number.
Accessibility at the primitive layer is free forever
Serving 5M members means serving a huge range of age and ability. We enforced WCAG 2.1 AA at the component level (inputs, buttons, navigation) rather than auditing screens at QA. Every new screen inherited compliance for free. The team that owns the primitives owns the accessibility story — that's been true on every product I've built since.
Hybrid was the right answer for the constraints we had
Ionic + Angular on IBM MobileFirst wouldn't be my first choice today, but on that budget, with that team, serving that member base, it delivered 90% of native feel at roughly half the cost. I've learned to be suspicious of any 'always use X' technology opinion — the right architecture is the one that fits the constraints you actually have, not the one your Twitter feed admires this month.
Outcomes
What shipped.
Members5M+Members served across Michigan
App Rating4.6Up from 2.8 stars
Support Calls-30%Reduction in service-line volume
AccessibilityWCAG AAEnforced at the component layer
Stack
Technology
Frontend
AngularJS
Ionic
TypeScript
SCSS
Mobile Shell
Cordova
IBM MobileFirst
Apple Wallet
Native Plugins
Backend
Node.js
Express
MongoDB
Redis
Security & A11y
Touch ID
Face ID
Encrypted Storage
WCAG 2.1 AA
Features
What it does
Ionic + AngularJS hybrid app running on IBM MobileFirst platform
Virtual ID cards with Apple Wallet integration — top-requested member feature
Real-time claims tracking with status timeline and push notifications
In-network provider search with geolocation and specialty filters
Prescription management with refill scheduling and reminders
WCAG 2.1 AA accessibility enforced at the component layer — full VoiceOver / TalkBack support
Biometric authentication (Touch ID / Face ID) via Cordova plugins
Lifted app rating 2.8 → 4.6 and drove a 30% reduction in support calls