The plan comes to the app.
Share states and data, but design different interfaces for each context of use.
Welfare and membership
Provide continuity between the daily mobile task and the operation of the accompanying team.




The evidence shows complete application and panel displays with test fixtures without actual health data.
The solution needed to bring together plans, sessions, progress, communication and membership management.
Share states and data, but design different interfaces for each context of use.
Differentiated customer authentication and administrative panel permissions
React + Capacitor, administration and API application maintained in separate repositories
The mobile phone had to keep clarity with one hand; administration needed more density and control.
Greater continuity of service and less duplicate work between accompaniment and administration.
Expected value; adoption and operational burden should be measured. Return requires baseline, investment and measurement period.