Keepwell

Context

Important personal responsibilities are often spread across paper documents, calendars, notes, emails, and memory. Keepwell brings the dates and future actions that need attention into one personal application.

The product covers responsibilities such as vehicle vignette and inspection dates, insurance renewals, contracts, subscriptions, and custom life-admin items. Its purpose is not simply to store those records, but to make clear what needs attention and when.

Product challenge

Different life-admin items share similar behavior without being identical. Some expire once, some renew, some repeat on a schedule, and others require a future action. Keepwell needs to represent those differences through one understandable product model while keeping the experience practical on a phone.

Reminder delivery is central to that model. A record is only useful if the relevant responsibility is surfaced when action is needed, without turning the application into a dense management dashboard.

Product thinking

Keepwell is deliberately designed around a general life-admin item rather than a fixed set of vehicle, insurance, contract, or subscription workflows. This keeps the product open to custom items and additional categories as real usage expands.

At the domain level, the important concepts are the responsibility itself, its relevant dates, its reminder behavior, and whether the action happens once, renews, or repeats. That shared model makes different records understandable without forcing every category into a separate product flow.

Role & responsibilities

Stoyan owns the product definition, UX/UI direction, application development, domain modeling, reminder behavior, notification setup, and ongoing testing with real records.

The work combines product decisions with implementation: defining which information matters, keeping common actions clear on mobile, and validating reminder behavior through actual use rather than treating the application as a static demonstration.

Reminder & notification experience

Items are created with the dates and future actions that matter, with reminders used to surface those responsibilities when attention is required. The experience connects the stored record to the action the user needs to take.

Reminder notifications have been implemented and tested with real application data, and notifications are being received successfully.

Application structure

The application is organized around the life-admin domain rather than around one hardcoded category. Item records, relevant dates, reminder configuration, recurring behavior, and future actions form the product concepts needed to support both current and custom responsibilities.

This structure is intended to accommodate new real-life records as the product develops while keeping the user-facing model consistent.

Mobile-first UX

Life-admin information is most useful when it can be added or checked quickly from a phone. Keepwell therefore takes a mobile-first approach that prioritizes clear entry flows, readable dates, and simple status visibility.

The interface is intended to feel like a calm personal application rather than an enterprise administration dashboard, even as it represents different categories and reminder lifecycles.

Current state

Keepwell is functional and is being used with real records. Reminder notifications have been tested successfully, and development continues through ongoing use and the addition of further records such as contracts and insurance policies.

Active development reflects product iteration with real data: the application is already working while its coverage of day-to-day responsibilities continues to expand.

Outcomes

• A functional application is already managing real life-admin records.
• Reminder notifications have been implemented, tested with real data, and received successfully.
• The product is being expanded through continued use with additional real-world records and categories.