ACCESSIBILITY / IOS
CarePlus.
An app designed around the people who care.
I worked on CarePlus with Mouchtakiri Azzeddine to explore everyday coordination between a person with Alzheimer’s and their caregiver. Activities, memories and communication come together in a shared space, with distinct roles and attention to accessibility.
The project at a glance
- Area
- Human–Computer Interaction
- Technologies
- Swift · SwiftUI · Supabase
- Status
- iOS project
- Explore
- Code and documentation
- Context
- iOS project · Foundation 2025–2026
My contribution and the team
I worked on CarePlus with Mouchtakiri Azzeddine. My coding work covered the evolution of patient–caregiver flows, Supabase synchronisation, the shared medication inventory and interface review. The project began in the 2025–2026 Foundation Program.
Where the project begins
Context before code.
Everyday care involves many small steps: remembering an activity, finding a contact, recording a moment and sharing information with someone who helps. When these are scattered across tools, putting the picture back together requires additional coordination.
I worked on CarePlus during an Apple Developer Academy Foundation Program in 2025–2026. The design question concerns support for everyday life, rather than a diagnostic system. It starts with a relationship between two people with different needs and access rights.
The workflow
Design choices, one step at a time.
The project’s journey, from the initial information to what people can do.
- 01 Sign-in and role selection
- 02 Linking accounts
- 03 Shared routines and diary
- 04 Communication within the care relationship
Start with roles, before features.
Patient and caregiver have separate accounts. Onboarding requires a configuration consistent with the selected role. The link is validated through the other account’s email and role; knowing an address alone does not grant access to its content.
Both accounts must confirm the link. The first request remains pending; the reciprocal request activates the relationship and sharing.
Bring continuity to the day’s activities.
Features include activities, reminders and a medication cabinet with stock, location and expiry information. The organisational objective is to make this information available alongside the routine, without reconstructing it each time.
PDF or text import recognises Medication: and Task: lines and turns them into reminders. The format is explicit; it does not freely interpret medical reports.
Make room for memories and relationships.
The diary can hold text, pictures, audio, video and the day’s mood. The linked caregiver works on the patient’s shared activities and diary, while personal contacts, calls and game results remain associated with each account.
Persistent chat supports communication within the active relationship. Contacts with quick calling, recorded voices and a game based on personal contacts complete the everyday experience.
Consider accessibility and data access together.
The SwiftUI interface supports light and dark appearance, Dynamic Type and VoiceOver labels. Adaptable text and descriptions for assistive technologies are part of the app itself, rather than a separate version of the experience.
Supabase manages authentication, the database and Row Level Security. Access to conversations depends on membership of the active care relationship.
Inside the project
Technology has a job to do.
Tools and components, explained through their role in the system.
Swift and SwiftUI
A native iOS app with an adaptable interface. Development requirements: iOS 17 and Xcode 16.
Supabase
Email authentication, Postgres and access policies. Roles, profiles and care relationships are also defined in database migrations.
Demo mode
A Debug build can use sample content to explore activities, the diary, medications and contacts without revealing real personal data.
Current state and next steps
What exists today.
The result is an iOS application with separate roles, linked accounts, shared activities, a diary and persistent chat. The journey connects onboarding to everyday collaboration.
The work brings together interaction design, information organisation and access control. That connection, beyond building the screens, is what makes the project interesting in my computer science journey.
People and documentation
Contributions and sources.
Team: Antonio Ferone and Mouchtakiri Azzeddine. Code and revision history are available in the public repository.
Beyond the case study
Based on the public project documentation consulted on 19 October 2026. Decorative illustrations are graphic representations; real screenshots are identified in their captions.