Skip to content
Back to Selected Work

BrightLimits

I started BrightLimits to explore a simple question: can a screen-time app help families agree on routines without making every conversation feel like enforcement?

It is an early product exploration, not a released app. The screens shown here are illustrative and use no real family or device data.

The problem is more human than technical

Families are balancing school, entertainment, communication, and downtime across more devices. The conversation can quickly become about enforcement instead of shared expectations and routines.

That led me toward a calmer product direction: make expectations visible, give children useful context, and make it easier for a family to review and adjust a routine.

What the product needs to do

The concept starts with a small set of product questions: how a family creates a routine, how everyone understands it, and how the routine can be reviewed without turning the product into a monitoring tool.

Set routines in plain language.

Give parents and children clear visibility.

Make review and adjustment feel normal.

Three product choices that matter

Keep the experience calm

A family product should make routines easier to understand without adding pressure, judgment, or unnecessary noise.

Make controls understandable

Parents and children should be able to see what a routine means and when it can be reviewed or changed.

Earn trust before adding features

Tone, privacy, and clarity matter more than building a long list of controls before the core experience is right.

The product direction

The interface explores a softer way to present routines, progress, and family review while keeping settings straightforward.

Illustrative BrightLimits mobile screens showing family routines, screen-time visibility, and review options

Illustrative mobile product direction showing routine setup, family visibility, and simple review moments.

Design exploration, not a released app.

What the exploration has reinforced

The most important decisions are about trust and scope, not the length of the feature list.

  • A family product needs the right tone before it needs more features.
  • Visibility can support a conversation without becoming surveillance.
  • Keeping the idea narrow makes the product decisions easier to evaluate.
See how these choices connect to my Working Principles.