The organiser
Needs plans and responsibilities to connect, so adding an event does not mean explaining it again in three other places.
TOOLS
Xcode
ChatGPT
Xcode
ChatGPT
Familiar
A more connected home.
A family organiser for the plans, responsibilities, and little things that make up a day.
- Role
- Product design & iOS development
- Timeline
- 2026 ongoing
- Category
- Family organiser · iPhone
01 · Overview
What does our day look like?
Familiar brings the household’s plans, responsibilities, and everyday details into a native iPhone organiser.
A family plan rarely belongs to just one person. A school run changes someone’s morning; dinner adds things to a grocery list; a task needs an owner. I wanted those relationships to be visible instead of scattered across separate tools.
I carried the project from product structure and supplied visual concepts into a working SwiftUI app. The work covered the daily overview, creation flows, calendar, family profiles, lists, meals, memories, and local persistence.
The design challenge
Make the shared day easier to understand.
Show what is next, who is involved, and what still needs doing without turning Home into a wall of widgets.
My roleProduct design & iOS development
PlatformiPhone · SwiftUI
Core relationshipPeople ↔ plans ↔ responsibilities
Build statusFunctional local app
About the evidence Concepts, implementation, and checks
The supplied concepts and research brief informed the product. App screens are actual Simulator captures. Diagrams and structural studies were made retrospectively to explain the implementation. No interviews, household study, or reduction in mental load is claimed. CloudKit sharing is disabled pending signed configuration and multi-account validation.
From a household brief to a working app.
I moved between the supplied design direction, the relationships in the data, and the experience on the phone.
- 01
Frame
Focus on the questions a household asks each day.
- 02
Structure
Connect members, events, responsibilities, and lists.
- 03
Design
Translate the authored visual direction into native screens.
- 04
Build
Implement local workflows with AI assistance.
- 05
Refine
Review Home, exercise the flows, and check persistence.
02 · Discover
One household. Different things to keep track of.
The brief pointed to three perspectives: organising the day, contributing to it, and knowing what is expected. These are working assumptions to test with households.
The partner
Needs a useful briefing and a clear way to contribute, rather than a second calendar to maintain.
The teenager
Needs understandable responsibilities and autonomy. A family interface should be clear about what others can see.
The category already bundles a lot.
I reviewed official product descriptions while assembling this case study. This is a desk comparison, not a hands-on benchmark.
Cozi
Bring the household details together.
Cozi combines a family calendar, shopping lists, to-dos, and meal planning. The relationship between a meal and the shopping list is especially relevant to Familiar.
The design implication
Official feature overview ↗Moving between household jobs should preserve the details already entered.
FamilyWall
Coordination reaches beyond the calendar.
FamilyWall brings schedules, lists, meals, and location features into its family organiser. That breadth makes scope and privacy decisions visible product choices.
The design implication
Official product overview ↗A places feature needs an honest explanation of how the location was supplied.
The direction for Familiar
Start with a readable daily briefing and connected local records. Keep manual check-ins explicit. Treat dependable multi-person sharing as work to validate, not a promise made by the mockup.
03 · Household journey
From “what’s happening?” to “it’s taken care of.”
The journey follows a day of coordination. Its thoughts and feelings are hypotheses, not invented participant quotations.
The work behind a simple briefing.
This story map separates the everyday activities from the smaller interactions needed to support them. The lower row identifies what still needs testing.
04 · Structure & flows
One plan, seen from different places.
Today, Calendar, and Family present the same events in different contexts. They do not create separate versions of the plan.
A day with no events
Home shows an empty schedule instead of making an old event look upcoming.
A responsibility completed
The task updates locally; a recurring task can create its next occurrence without duplicating it.
A place, not a live signal
Places are manual check-ins. There is no background tracking or implied live safety status.
05 · Design iterations
The concept set the direction. The app revealed the details.
The supplied Home concept established the warm household dashboard. The native work turned that direction into editable plans and connected local actions.
Supplied visual concept
A household briefing, not a productivity cockpit.
The family row, next event, schedule, and household tools were already central to the visual direction. I kept that hierarchy while making the interface work with real data and native controls.
Concept-only live status and location treatments were not presented as implemented capabilities.
A second pass on the native Home.
The first build squeezed important information into small spaces. This pass gives responsibility, membership, and privacy information enough room.
01
Keep Add member visible
Move creation out of the clipped avatar strip. Give it a named, accessible action.
02
Give tasks their own space
Full-width rows show the task and its assignee, with a usable completion target.
03
Make the status honest
Use an upcoming or current event, never a past event relabelled Up next. Explain manual check-ins in full.
The structure underneath the screens.
These separate sketches and wireframes were created after implementation to explain the layout. They are not historical process artifacts.
Retrospective sketchs
Retrospective wireframes
06 · Visual design
Warm enough for home. Clear enough for the day.
Cream surfaces, forest actions, and a small family of muted accents carry the supplied brand direction into the native app.
The identity
FamiliarThe house and sun establish the identity. In the app, the house shape also anchors Today in the navigation.
Native app colors
#294F43Forest
#F8F6F0Cream
#18201FInk
#DF785BTerracotta
#DBA743Mustard
#819879Sage
#9E90C5Lavender
These values come from the native Palette. The implementation adapts the supplied concept palette rather than claiming the two are identical.
Typography
SF Pro Rounded + SF Pro
Rounded system type gives the family name and page titles a welcoming character. Standard system type carries schedules, member names, and controls.
The supplied brand board proposed Inter. The native app uses system fonts; no Inter font is bundled.
Iconography
Home, calendar, and list-grid shapes are vector redraws from the supplied icon direction. Supporting actions use SF Symbols.
A recognisable voice. Native controls.
Bold rounded headings establish the entry point. Regular and semibold system text keep the operational details legible.
A font specimen rendered with platform APIs, not a recreated application screen.
Components from the working app.
Native pixel extractions preserve the actual typography, icon shapes, spacing, and states.
Family members
Native app detailNext event
Native app detailSchedule rows
Native app detailList filters
Native app detailPrimary navigation
Native app detailTask rows & assignees
Native app detailManual check-ins
Native app detailMeals & little moments
Native app detail07 · The app
The household, in working screens.
Today, Calendar, Family, and Lists share the same local records. The centre Add action opens the creation menu.
Screen tour · actual native captures
Start with the day
See family members, the next event, the schedule, and remaining responsibilities.
A tour of native screenshots. Select a screen, then enlarge it to inspect the details.
What is verified, and what is next
The local app supports event editing, recurring tasks, list checkoffs, meals, notes, and photo memories. Four model tests passed in this refinement pass; the earlier project record also documents three UI tests. The new Home build was installed and reviewed in Simulator. Task completion updated the remaining count and persisted after relaunch; the places, meals, and memories destinations were checked in the running app. CloudKit sharing remains disabled pending signed provisioning and two-account checks. Device permissions, notification delivery, VoiceOver, and household usability need separate validation.
08 · Reflection
A useful Home has to earn its space.
The design became clearer when I treated the daily briefing as a set of relationships rather than a collection of attractive tiles.
A little lessto keep in your head.
Swipe to read all six takeaways →
A plan should follow the people involved.
01Connected records
A task needs an owner, not just a checkbox.
02Responsibility
A calm layout still has to carry real detail.
03Visual hierarchy
Manual check-ins need an unmistakable label.
04Privacy
Shared screens do not prove dependable sharing.
05Product honesty
The next study needs the whole household.
06Validation
What I would test next →
Ask two household members to plan dinner, assign a recurring task, update groceries, and find each other’s plans. Observe whether responsibility is clear, whether both people contribute, and whether they understand what is shared.
Sources and project notes
Project evidence
Familiar SwiftUI source, native Simulator screenshots, supplied screen concepts and brand board, and the project’s verification record. The supplied research document contains unresolved citation tokens, so it is treated as a brief rather than verified primary research.
Desk references
Cozi · official feature overview; FamilyWall · official product overview. Reviewed for this case study; no competitor pricing or usability scores are asserted.
Visual provenance
The app icon and supplied concepts are project assets. The banner is an AI-generated brand composition referenced to the actual house mark; the homepage cover uses the original app icon. Components are native pixel crops. Diagrams, sketches, and wireframes explain the build retrospectively.
Release boundary
This is a functional local app, not a released family-sharing service. Optional CloudKit code is not evidence of production sync, live location, granular roles, or remote deletion.