OurNext: helping families share the care of an ageing parent.
- Client
- Year
- My own product
- 2026
OurNext
Know what is happening. Know what is next. Share the load.
Building
- Built with
- FlutterDartSupabasePostgreSQLTypeScriptNode.js
Overview
Know what is happening. Know what is next. Share the load.
OurNext is for adults coordinating care for an ageing parent who still lives at home in England. One shared care space holds the appointments, letters, provider contacts and tasks, so the family can see what is coming and who has agreed to do it.
The parent can take part if they want to, and the rest of the family joins by invitation.
Challenge
Care information arrives everywhere, and the chasing falls on one person.
Letters, appointments and messages land in different places, and one person ends up re-entering them, chasing everyone else and remembering who said they would do what.
Reviews of existing caregiver apps kept pointing to the same needs: share only what each person should see, link a notification straight to the thing that needs doing, and stay useful to someone doing it alone. It also has to know its limits: no diagnosis, no treatment advice, no symptom triage.
Solution
Clear next actions, tasks people accept, and sharing that is narrow by default.
Tasks are requested, accepted, declined, handed back and completed, with the history kept, so everyone knows who agreed. Appointments carry the provider, the letter, the questions to ask and the transport. Each helper gets only the access they need, and the owner can preview exactly what a helper will see before inviting them.
Underneath is a Flutter app on Supabase, with a TypeScript API and a PostgreSQL schema built around owner, editor, viewer and helper roles, single-use invitations that expire, and an audit history of every change.
Where it stands
Being built, carefully.
The foundations are in: accounts, care spaces, shared tasks, appointments, helper access and an in-app notification inbox, covered by 22 automated test cases for isolation, expiry, revocation and two people editing at once.
For now it runs on synthetic data only. Real health information waits until sign-in and hosting meet the standard it deserves.
4
access roles: owner, editor, viewer, helper
22
automated test cases