Centered
One care journey. Several systems that need to agree.
Web, backend & mobile development
Care platform · team contribution
Next.js · React Native · Node.js · PostgreSQL · Expo
Keep the experience connected.
Members and care teams meet the same information through different interfaces. Authentication, care plans, health readings, and visit access need consistent rules beneath those screens.
Where I worked.
Contributed across the web portals, backend services, and member mobile application.
Worked on health-data trends and resource-library experiences, linking useful information to the care journey.
Contributed backend access and registration fixes, plus mobile startup and check-in presentation improvements.
The details that matter.
Roles belong to the system
Interface gates guide people to the right experience. Backend authentication resolves held roles from the database rather than relying only on the roles in an older token.
A reading has a history
Tracker data carries a source-event identity and versioning context. That makes repeated or revised incoming readings a data-model concern, not just a charting concern.
A visit needs an explicit audience
Visit access distinguishes scheduled participants from an administrative break-glass path. Care-team access deserves a specific rule, not a broad “signed in” check.
A coherent product is built through the boundaries: between roles, devices, records, and the people who need them.
Visit the public website