One shared place for the things a family otherwise has to keep in its head.

Life OS is intended to become the family's everyday coordination hub: schedules, tasks, ownership, handoffs and important status in one place so fewer things need to be remembered, asked about or checked twice.

Illustration of Firthsead Life OS bringing family plans, tasks and everyday coordination into one shared view
The same visual language now used inside the private-beta app.

What can you use it for?

What Life OS helps a family do.

The private beta is deliberately focused on the parts of family life that create a lot of everyday friction. Broader areas come later only when they can be supported clearly and safely.

See what matters today

Bring today's appointments, chores and important family items into one focused view instead of searching across lists and messages.

Share access between adults

The household owner can invite another adult into the same household so the family can work from the same current information and responsibilities.

Use one shared family calendar

Add the events the household needs to know about and connect them to the relevant person when useful.

Manage recurring chores

Create responsibilities for adults or children, mark them complete and let the household see current status without scores or streak pressure.

Give children a simpler view

Children can have a protected, deliberately simpler view of their own assigned tasks, relevant schedule and the information they actually need. A child device can be connected with a short-lived invitation.

Keep factual medication status

A scheduled medication item can be marked as taken and the record can show who logged it.

Medication in Life OS is factual record keeping only. It does not provide medical advice, treatment instructions or dose recommendations.

How it is meant to be used

One family, one shared picture.

The goal is not to make everyone administer another system. The goal is to give the household one dependable place to look when memory, energy or communication is not enough.

01

Set up the household and invite the people who need access

One adult creates the household and can invite another adult into that same household. Adults can create child profiles and connect protected child devices separately.

02

Add what genuinely needs to be shared

Schedules, chores, ownership and relevant household events go where they belong. The system should reduce duplicated coordination, not capture everything simply because it can.

03

Everyday use starts with Today

Opening the main adult view should quickly answer what matters now, what is already done and who owns the next step.

A simple example

Training at 17:30 is not just a calendar event.

The load is everything around it.

Someone needs to know who is collecting, whether the sports clothes are packed, whether dinner timing changes and whether another family plan collides with it.

Life OS is intended to make that information and ownership visible without making the family reconstruct the situation from memory or a message thread.

The design principle

Complex underneath. Simple on top.

Less maintenance. More orientation.

Every screen should answer a useful question: What matters now? Who is handling this? What has already happened? What is the smallest helpful next step?

Privacy boundaries, role-based access and data minimisation are being built into the architecture rather than added later as decorative promises.

Coming later

Life OS is meant to do more, without pretending every idea already exists.

These areas are product direction, not the same thing as the current beta core.

Coming later

Reset

A calmer way back when routines have slipped, without returning to a wall of old overdue items.

Coming later

Quick capture

Get something out of your head immediately and organise it later when capacity returns.

Private beta

Built for real family life.

The beta is intended to test whether this core actually reduces coordination load in real family life.