Valley of Digital Inc
A different point of viewLoading page
Skip to content

Kenko — Habit & Wellbeing App

Small routines. A useful daily rhythm.

A mobile habit app concept with a clear daily view, manageable routines, and considerate progress feedback.

The productMobile application
The focusDaily routines
Our contributionProduct direction & interface design
The contextOriginal studio concept
Kenko original mobile application design study showing daily routines
Illustrative product interfaces and sample data. Original studio design study, without claimed client outcomes.

A product with
a clear purpose.

Kenko is a mobile product study for people who want a manageable daily routine. Sage, ivory, and small coral accents create a calm interface, while the screen hierarchy gives one useful next action prominence. The product direction supports personal habit tracking; it does not offer diagnosis, treatment, or claims about health outcomes.

Who it is for

People building everyday habits who need lightweight planning and feedback without an overwhelming dashboard.

The challenge

Habit applications can ask for too much setup, reward activity without context, or make a missed day feel like failure. Kenko explores a smaller set of screens that explain the current routine and let the user adjust it. The challenge is to make progress understandable while respecting different schedules and levels of participation.

  • Make the first routine easy to define.
  • Give the daily screen one clear priority.
  • Let people adjust reminders and participation.
  • Explain progress with plain language.

Useful choices.
A coherent interface.

Kenko detailed interface design showing the next step in daily routines
A closer look at the interface direction.
01

A personal starting point

Onboarding asks for a small number of preferences and an initial routine. Each question explains how the answer changes the experience. The user can review the choice and begin without completing a long profile.

02

A considered daily view

Routine cards show the intended action, its current state, and the next useful control. A simple week view provides context without competing with the main task. Missed actions can be rescheduled or left incomplete without misleading feedback.

03

Progress with perspective

The progress screen distinguishes completed activities from plans and allows a user to review their own pattern. Reminder settings are accessible from the same context, with clear choices about timing and notifications.

From context
to the next action.

Step 1

Choose a routine

The user selects a manageable activity and reviews when it should appear. They see a preview of the daily screen before confirming the plan.

Step 2

Complete or adjust

The daily view offers an understandable action and feedback. If the plan no longer fits, changing it is a normal part of the journey.

Step 3

Review the pattern

The user can look back at recorded participation, update reminders, and choose the next routine without a claim that the app has measured wellbeing.

The decisions
behind the screens.

Kenko product design overview
Proposed implementation direction

A proposed mobile build would define local state, account synchronization if needed, and notification permissions separately.

Reminder timing and stored routine data need review across time zones, offline use, and device changes.

Accessibility checks would include text scaling, touch targets, focus order, and reduced-motion preferences.

A focused first scope

  • Routine onboarding
  • Daily activity and week view
  • Progress and reminder settings
  • Offline and empty-state concepts

Questions a working
product must answer.

This study establishes a reviewable design direction. A production project would test the selected journey with representative users, realistic data, and agreed acceptance criteria. These questions define the next review without implying results have already been measured.

  • 01Can someone create and change a routine without coaching?
  • 02Is the meaning of completed, skipped, and planned activity clear?
  • 03Do reminder choices remain understandable when permission is declined?

Have a similar product in mind?

Share your audience, the task you want to improve, and the constraints that matter. We can discuss a scope built around your own context.

THE START OF SOMETHING

Tell us what
you’re imagining.

A little context helps us start. Fields marked * are required.

Your details and project requirements
Which services are you interested in? *

Search and select all that fit your project.

0 selected · 34 services shown

We’ll use your details to respond to this enquiry. Text updates require the separate opt-in above.

This form is protected by reCAPTCHA. Google’s Privacy Policy and Terms of Service apply.