Where it started
My niece was heading into her final year of school. Wellbeing, scouting, sport, school, university applications, home and friends were all competing for space in her head, spread across paper, emails and memory. The problem wasn't a lack of motivation. It was losing track of something written down somewhere she wasn't looking.
Adult productivity tools bring the language and pressure of work. Apps aimed at younger users often add streaks, badges and notifications. She didn't need another thing asking her to perform.
Patchwork brings those parts of her life into one place, making it easier to keep track of commitments, plans and notes without adding another system to maintain.
I designed it around her needs and the language she uses, with each part of her life organised into a world with its own colour and illustration. Her feedback continues to shape the product as she uses it.
The first version took about a week, working in my spare time. It's now a working application she uses daily, with new features tested as the product grows. For now, it remains invite-only, built around her needs and those of a small group of friends.



Cosy on purpose
Patchwork is meant to feel cosy: a soft place for a week that can feel overwhelming. Its visual language takes inspiration from the Asian culture of making everyday things cute. Drawings have faces, stickers add personality, status messages sit on washi tape, and bright colours bring character without overwhelming the interface.
I started in Figma by defining the visual language rather than prototyping the entire application. I established the brand, typography, palette, components and design tokens first: a warm stone canvas, white cards, dark green anchors and fourteen accent colours for the different worlds.
The design system then became a working set of components in code. Each of the 40 components has a typed contract and a written specification. Values trace back to Figma, and missing definitions are flagged rather than filled in by guesswork. Accessibility was part of that system. Text colours for each world meet a 4.5:1 contrast ratio in both light and dark themes.
Patchwork
Design system · v1
Warm stone, one dark green anchor, white cards. Quicksand for headings, Inter for the rest.


Each world keeps its accent in both themes. Every drawing is redrawn for dark, never dimmed.
Any item can wear one, and it becomes the thing you recognise it by. One artwork for both themes.


Your own line, or a new one each day, typed on one of 19 tapes picked at random each visit.
Real components, captured from the demo, light and dark.






Two interfaces, two contexts
Patchwork is phone-first, but mobile and desktop aren't the same interface at different widths. They support different situations.
Mobile is for the day: Today's plan, the different worlds and quick actions, available while on the go.
Desktop is for stepping back: The week at a glance, pinned items and more room to plan.
Light and dark themes follow the device setting. Light mode stays readable outdoors; dark mode is gentler in the evening. The same design system connects both, while the information hierarchy adapts to the context.


Defining how it behaves
Some of the most important design decisions aren't visible in screenshots. They determine how the product responds when plans change, deadlines pass or a user decides not to do something.
- Nothing scoldsOverdue means overdue, not failure.
- A task can be skippedIt stops being late without being marked as completed.
- Postpone is different from editMoving a future deadline is normal; postponing an overdue task is an explicit action.
- Pins stay pinnedThe app never rearranges the user's chosen shelf.
- Lessons are context, not tasksThe timetable can be viewed, but lessons don't automatically become tasks, reminders or email items.
I documented these behaviours before implementation. The specification became the reference for how the product should work, connecting the design decisions to the code and providing a basis for review.


Built with AI
I made the product, behavioural and visual decisions, then directed AI coding agents, mainly Claude Code, through the implementation.
What made this workflow effective wasn't clever prompting. It was giving the agents clear constraints and reliable references: a behavioural specification written before the features, a design-system handover tied to Figma, focused briefs for each build session, and a deliberate implementation order.
I reviewed the results against the original decisions and corrected deviations as they appeared. The design artefacts provided continuity between what I intended and what the code produced.
The first core version took about a week, working in my spare time. The product has continued to grow, through daily use, with new features added as needs and ideas emerge.
Architecture shaped by the product
The same principles shaped the architecture. The goal was to keep behaviour consistent across the application and make the underlying data dependable.
Task status is derived when it's read, rather than stored by a background job. A task is overdue because its deadline has passed, not because a separate process has updated its status.
There is no push-notification machinery. One server-side reminder list feeds the phone, desktop and daily email, keeping them consistent. The email runs on the application's own scheduler because the hosting platform's scheduler uses UTC and would drift from local time when the clocks change.
Backups came before features. Every change is recorded as an append-only event and replicated off-site. Restore procedures were tested before the first real item was added.
Patchwork holds details of someone's personal life, so the administration interface is deliberately limited: it shows system health and operational counts, never personal content.


It kept growing
The first version covered the essentials. Everything since has come from using Patchwork day to day, adding features when a real need emerged.
Search
Find anything in the account, down to a line inside a list. Search ignores accents, so “krakow” also finds “Kraków”.
Checklists
Tasks can contain their own lists, such as packing for a trip. A recurring weekly shop returns every Monday with empty boxes.
Habits
A habit appears in the day's plan and is completed one day at a time. It never becomes overdue.
Lesson statuses
Mark an individual lesson as cancelled, taught by a substitute or important. The status applies to that lesson on that day only.
The daily email
A single daily summary, delivered in the morning or evening, showing what's coming up.
The demo
A fictional week that always starts from today, stored in a separate database that's discarded when the session ends.



A sentence becomes an item
Magic is Patchwork's first AI feature, recently added. Write a sentence such as “Coffee with Grandma on Sunday at 4”, and it turns it into an event or task, filling in the relevant details: category, world, date, time, repetition, place, checklist and reminder.
The key decision was the model. A conversational LLM generates text that can rephrase or invent details, which then have to be converted back into structured fields. Magic uses Jev, TypeSafe's decision model, which selects from predefined options rather than writing free-form answers. For each entry, it answers around 45 fixed-choice questions, each with a confidence score. The application handles date calculations itself.
The result is structured input without giving the model control over the underlying data. Uncertain values are left for the user to resolve, and each entry costs a fraction of a cent to process.
When Magic is confident, the item is saved and opened. The user can check it immediately, without an extra confirmation step. When something important is unclear, the usual creation form opens with the available details filled in. The uncertain field stays empty, with an explanation of what's missing. The original input is preserved in either case.
- Your words, never rewordedMagic extracts the title and place from the sentence rather than rewriting the user's text.
- An extra, never the coreMagic is opt-in, labelled Experimental, and unavailable when the service is down. The regular creation flow remains available.
I tested the model before designing the interface, using 71 real sentences, including tricky dates. At launch, 70 were handled correctly, with an average processing time of about 0.4 seconds and a cost of $0.0005 per entry.
Testing also informed the interaction design. Removing a separate confirmation step made the successful path faster, while opening the standard form gave users a straightforward way to resolve uncertainty.



Try the demo
Patchwork is invite-only, but the demo runs the real application with fictional data.
Create, edit, complete and skip items without affecting a real account. Magic is available for a limited number of attempts per visit.
The demo uses its own database, which is discarded when you leave.
A product in daily use
One high school student needed a better way to keep track of a busy life, across school, wellbeing, hobbies and everything in between.
The first version was working. The design, behavioural rules and implementation came together in a product she could open every day and use to make her life a little easier to manage.
Daily use became the basis for further development. The product continues to evolve around real needs, with design decisions carried through to implementation.
