HABIT

Case study / Chris Pruett

Building HABIT: From Research to a Shipped Product

I founded HABIT and led its research, product direction, branding, design, and release process. The result is an iOS app that turns a habit-change plan into something people can use in an everyday moment.

On this page
My role
Founder & Product Lead
Starting point
AP Research
Public release
iPhone and iPad

A research question became a product.

HABIT began with a question: how can research-based habit-reduction methods be used to design a personalized habit-breaking app for adolescents? I wanted to make the research useful outside a paper. That meant deciding what someone should be able to do when a familiar cue or urge appears.

The product grew around a short loop: identify the trigger, choose a replacement response, check in, and reflect on what happened. A growing forest makes repeated effort visible. The original focus on adolescents later expanded into Helping Anyone Break Irresistible Tendencies, while keeping the app’s age and safety boundaries.

The research was a design and translation study. It does not establish HABIT’s effectiveness. That distinction shaped both the product and how I explain it.

Explore the research journey

My role was to give the work a direction.

I owned the research project and the product decisions that followed it. I defined the problem, chose priorities, developed the brand identity and logos, and set the visual direction for the app and website. I also had to decide whether an iteration actually solved the problem I had described.

That involved writing requirements, reporting specific defects, reviewing builds, choosing between competing approaches, and preparing the product for distribution. A visual change needed to remain readable on a phone. A connected feature needed clear data boundaries. A release needed accurate screenshots, descriptions, and purchase disclosures.

My responsibility was to connect those details to the same product: straightforward support in the moment, with room to return after a difficult day.

From evidence to requirements.

I reviewed mechanisms such as implementation intentions, self-monitoring, reinforcement, and timely support, then weighed possible features by evidence strength, feasibility, and fit for the intended audience. They did not all deserve equal priority.

If-then planning became the central interaction: connect a recognizable cue to a small replacement action. Self-monitoring became daily check-ins and a record of patterns. Timely support informed reminders and short activities that someone could use around a difficult moment.

Visible progress became a forest rather than a clinical score. The tree is a way to recognize effort; it is not a measure of recovery or proof of behavior change. Where research described a structured intervention, I treated an app feature inspired by it as a design hypothesis, with its own limits.

Four decisions that shaped HABIT.

Keep earned growth after a slip.

A current streak and accumulated effort answer different questions. I wanted a setback to leave room for reflection without making earlier work disappear. HABIT separates current streaks from earned growth, and its six tree species progress through twenty stages. Existing saved selections also need a migration path when the available species change.

Give connected features clear boundaries.

Habit records can be personal. I made local storage the foundation and treated account services, purchases, and online support as separate data flows. The design needs to explain what a connected action sends and what remains on the device. An encrypted-sync design is also a different milestone from enabling and verifying it in production.

Review the actual release experience.

During TestFlight preparation, a duration control exposed the gap between intended behavior and what appeared on a phone. The native control was restored, while an initial-value mismatch was recorded separately. I accepted that remaining issue for the release rather than describing the whole interaction as fixed. Screenshots also had to reflect the selected build.

Make the website work beyond its opening frame.

The tree-led website needed to survive real reading and navigation. My feedback identified scrolling glitches, menu text that outlasted its closing panel, mobile layouts, and precise logo alignment. Iteration addressed those behaviors while preserving the authored camera direction. The site also provides static artwork and readable page content when motion or interactive rendering is unavailable.

The product and the system behind it.

The mobile application uses React Native with Expo, shared JavaScript logic, and native iOS and Android projects. Its core capabilities include if-then plans, check-ins, reminders, progress views, and a three-dimensional forest. The public iOS offering includes three habit trees free and up to twenty with HABIT Pro.

Core records use an encrypted local repository. Firebase provides the account and server-service foundation; RevenueCat supports subscription access. HABIT includes local Coach guidance and a separate online Coach flow with processing disclosures and server-side access controls. The privacy policy explains those distinctions in more detail.

The website uses React, TypeScript, and Vite, with Three.js for its tree scenes and Cloudflare Pages for hosting. Pages are prerendered so their content and metadata are present before interactive features load. Keyboard navigation, reduced-motion behavior, loading fallbacks, and resource cleanup are part of the implementation requirements.

From prototype to public distribution.

HABIT moved through signed-device builds, TestFlight preparation, App Store submission, and public iOS distribution. The App Store’s version history lists the initial release and a subsequent update. The website provides the product explanation, pricing, support, and privacy information around that app.

Reaching a public listing is a concrete milestone. It does not answer every question about reliability, adoption, or long-term usefulness. I keep those questions separate from the fact that the product shipped. Android remains a development effort, with its own testing and distribution work.

View HABIT on the App Store

What changed in how I work.

I learned to make feedback testable. “Make it smoother” is less useful than identifying the section, scroll direction, device width, and visible failure. I also learned to separate a successful local check from a signed-device result, and a prepared submission from a public release.

Research gave me a reason to choose a feature. Product ownership meant carrying that choice through design, implementation review, testing, disclosure, and support. The work also taught me to keep an unresolved question visible when the evidence does not yet support a confident answer.

Let’s talk about the work.

I’m interested in opportunities involving product, research, technology, and early-stage building. If you’re hiring, building something related, or interested in collaborating, I’d be glad to talk through the decisions behind HABIT and what I learned.

Contact Chris through HABIT