Care staff
Staff work with their assigned clients, visits, and care notes through the mobile app, keeping a record of the care they delivered.
Healthcare · Care management platform
Albis Care
Care records, visits, and family updates in one place.
THE PLATFORM
What it does.
Albis Care is used in daily production by a UK domiciliary care provider. Care staff manage visits and record care notes, the office coordinates clients and staff, and relatives can receive access to updates about their family member. The platform brings those responsibilities together while keeping access appropriate to each person’s role. As of August 2026, it supported approximately 15 staff and more than 60 care clients.
MY CONTRIBUTION
The backend, the apps, and what connects them.
I have been the sole engineer and technical owner since the project began in 2024. I built the PHP REST API and database, the React Native app, the access model, and the website enquiry integration. I also own mobile builds, Google Play releases, and ongoing maintenance.
HOW IT FITS TOGETHER
The main workflows.
Office & care managers
The team coordinates care clients, staff, visits, and transport from role-specific dashboards.
Families
Relatives can view the updates they have been granted for their family member. Access is specific to that client and can be changed or withdrawn.
CARE RECORDS & ACCESS
Permissions that reflect how care is delivered.
Running the organisation and recording care are different responsibilities. I built the access model around that distinction, with a separate approach for family updates.
Keep care notes tied to the person delivering care.
Assigned care staff write the care notes for their work. Administrative seniority alone does not grant the ability to create those records, helping preserve clear authorship.
Give families access to the right updates.
The family-access feature lets the team grant, adjust, or withdraw a relative’s access for an individual client. Families see the information shared with them, rather than receiving general access to care records.
Keep permissions consistent behind the screens.
Role-specific dashboards make the app easier to use, while backend checks enforce access to records and actions. The interface reflects those permissions rather than being responsible for enforcing them.
DELIVERY & MAINTENANCE
A platform the team can keep using.
My work includes the parts beyond the screens: connecting enquiries, releasing the app, and maintaining it as the organisation’s needs change.
Connect the website without mixing workflows.
Website enquiries feed into a separate marketing workflow, keeping new enquiries distinct from operational care records.
Make mobile releases repeatable.
I resolved build and publishing issues and established an EAS Build workflow through GitHub Actions for Google Play releases.
Work within the client’s existing setup.
The PHP backend uses the client’s existing hosting, while React Native and Expo support mobile development from one codebase. The choices keep infrastructure and maintenance manageable for a small care provider.
TECHNOLOGY
What I built it with.
- PHP REST API
- MySQL / MariaDB
- React Native
- Expo
- TypeScript
- WordPress
- Elementor
- PHPMailer
- EAS Build
- GitHub Actions
- Hostinger
MORE OF THE PRODUCT
Beyond the dashboard.
MOBILE APPLICATIONS
Inside the mobile app.
Sign-in
The app’s sign-in screen, with the account email redacted.
Administrator overview
Staff, client, and visit summaries with administrative controls. Screen totals are not reported usage figures.
Driver workspace
Assigned transport and history in a role-specific workspace, with the name redacted.