oh my hours

Screen time dashboards have a persuasion problem. A daily tally of minutes is abstract, easy to rationalize and easy to swipe away. A weekly summary rarely changes what happens the following Monday. Most people who have tried to cut back on their phone know the routine: look at the number, wince, carry on.

oh my hours, developed by Yaroslav Neznaradko for iPhone and iPad, changes the unit. Instead of totaling minutes, it counts how many hours of your day stay free of distraction. You choose the apps or categories that pull you off course, and the app renders the day as a grid of hourly cells. Open one of those apps and that hour is gone. Stay away and the cell survives. A checkpoint at your limit offers a last exit: close the app and keep the hour, or carry on and lose it. A day limit sets how many lost hours forfeit the entire day.

The app occupies narrow ground on purpose. It is neither a blocker that locks you out nor a conventional usage report that tallies after the fact, so it runs entirely on self-accountability. That places it in a specific slot: the user who finds hard blocks infantilizing and passive reports toothless. 9to5Mac called it a “rather nifty concept” worth trying, particularly for people who haven’t found existing screen time tools helpful, and that is the right audience to have in mind.

The surrounding package is disciplined. Data stays on the device, with no account, no server and no analytics, and history exports to CSV. Day, week, month and year views track progress, backed by home screen and lock screen widgets, shareable images and hand-drawn icon sets. The free tier covers day and week views, basic widgets, the default icon set and export. The Full Version adds month and year views, their widgets and more icon sets.

Public reception is too thin to read much into. The US App Store shows a 4.0/5 average from just three ratings. One reviewer credits the app with keeping distractions down and adding accountability. Another reports a scheduling limitation that matters for a specific group of users, covered below.

• Hourly Day Grid: Each hour of the day is a single cell, kept or lost depending on whether you opened a distracting app during it.
• Custom Distraction List: You pick individual apps or whole categories, so the definition of “distraction” belongs to you.
• Checkpoints: At your limit, a prompt offers the choice to close the app and save the hour or continue and forfeit it. Checkpoints can be switched off.
• Day Limit: A threshold of lost hours beyond which the whole day counts as forfeited.
• Progress Views: Day and week views on the free tier; month and year views with the Full Version.
• Widgets: Home screen and lock screen widgets, with month and year widgets reserved for paying users.
• Shareable Images and Hand-Drawn Icon Sets: Exportable visuals of your record plus a personalization layer, with one icon set free and more in the paid tier.
• On-Device Privacy: No account, server or analytics; full history exports to CSV on every tier.

Hours as the Unit

Changing the unit changes the behavior it rewards. Minutes are continuous. The cells in oh my hours are binary: each hour is kept or lost. That produces three consequences, two good and one awkward.

First, it punishes the reflexive check. The ten-second glance that a minute counter barely registers costs a full hour here. That glance is the habit loop most people want to break, and pricing it heavily is the correct design decision. A minute-based report tells you that quick checks added up to very little. This grid tells you they cost you the morning.

Second, it rewards batching. Because a cell is lost whether you spend one minute or fifty in a distracting app, the rational strategy is to cluster distraction into fewer hours. That is a soft form of time-blocking, delivered through incentive rather than instruction. Users who already structure their day in blocks will find the grid maps neatly onto how they work.

Third, the awkward part: once an hour is lost, the marginal cost of continuing drops to zero until the clock turns over. A minute counter keeps charging you; this grid stops charging the moment the damage is done. The clock boundaries are arbitrary too. A glance at 9:58 and another at 10:03 burn two cells for five minutes of activity, while a 55-minute scroll inside a single hour costs one. Anyone who treats the grid as a game will feel both edges, and the design offers no obvious correction for either.

Checkpoints and Stakes

The checkpoint is the mechanic that most justifies the app’s existence. It inserts friction without a wall: continuing is a deliberate act, and the loss is self-inflicted and recorded. For users who resent being locked out of their own phone, that framing is healthier than a block, because it keeps the decision with the person making it while making the cost explicit.

Checkpoints are optional. Switching them off turns oh my hours into a pure ledger, recording losses after the fact with no moment of intervention. The flexibility is welcome, but we would steer most users toward keeping them on; without that decision point, the app drifts toward the passive reporting it claims to replace.

The day limit raises the stakes from the hour to the day. A threshold that forfeits the whole day sharpens motivation in the morning, but it reproduces the lost-hour problem at a larger scale. Once the day is gone, the remaining cells have nothing left to protect, which invites the familiar “what-the-hell” spiral. The week view softens this by putting a single blown day in context, so we would treat the day limit as a tool for experienced users rather than a default.

The Honor System

The refusal to block is a design stance, and the app is upfront about it. For self-motivated users who respond to visible records, streak-style pressure and a clear tally, self-accountability is enough. For users whose phone habit is compulsive rather than casual, it is not. Any system that depends on the user’s own restraint can be ignored by that same user, and oh my hours has no enforcement layer to fall back on. Buyers should know which camp they belong to before paying.

The Midnight Problem

One App Store reviewer reports that schedules can’t cross midnight, so a window such as 23:00 to 07:00 isn’t possible. If that holds, it is a meaningful gap. Night-shift workers, people with irregular sleep and anyone whose problem hours straddle midnight can’t model their day accurately. A tool built around habits is constrained by calendar-day logic, and the habits it targets don’t respect the calendar.

Progress and the Paywall

Day and week views are free; month and year views require the Full Version. That is a fair line. A week is enough to judge whether the hour-based method changes anything for you, and month and year views are where long-term trends become worth paying for. Keeping CSV export on the free tier is the more important decision: your history is never held hostage behind the subscription, which matches the app’s privacy pitch.

Privacy as Architecture

An app that knows which apps you open, and when, holds sensitive behavioral data. Keeping it on the device with no account, server or analytics is the correct architecture for this category, not a bonus feature. The trade-off follows from the design: on-device storage suggests an iPhone and an iPad keep separate records, so users who split distraction across both shouldn’t expect a unified history.

The hourly grid is the interface’s strongest decision. A day rendered as kept and lost squares reads at a glance, compresses naturally into widget sizes and works on the lock screen, where a quick look at the record can interrupt the impulse to unlock. It replaces charts and minute counts with a single legible pattern, and that legibility is the product.

The hand-drawn icon sets give the app warmth that clinical wellbeing dashboards lack. That matters more than it sounds: a self-accountability tool only works if you keep looking at it, and personality helps. The shareable images extend accountability outward, letting users post their record to friends or a group, although that pressure only works for people who want an audience.

On performance, the data model is small: a handful of states per hour, across a day. An app with no server dependency avoids network latency and outage risk entirely. By design, it should be light on storage and quick to load.

oh my hours is an Apple-only product for iPhone and iPad. That leaves out Android, Mac and web users, so distraction on a laptop goes unrecorded. There is no cross-platform version, which narrows the audience for an app whose concept would suit almost any smartphone user.

Interaction is touch-first, and the widget system carries much of the experience: lock screen widgets suit the iPhone’s role as the primary distraction device, while home screen widgets cover both iPhone and iPad. The iPad version addresses a different kind of distraction, the couch-and-tablet evening session rather than the reflexive pocket check, and the grid logic applies equally to both.

The free tier covers day and week views, basic widgets, the default icon set and CSV export; the paid tier adds month and year views, their widgets and more icon sets. Because data stays on each device, buyers with both an iPhone and an iPad should expect two separate histories.

The hour-based grid is the app’s best idea, but it arrives with too many caveats for a broad recommendation. Binary cells stop charging once an hour is lost, the day limit can collapse into a write-off, and the honor system offers nothing to users who need enforcement. The reported midnight scheduling gap and Apple-only scope narrow the audience further, and three ratings is too little public data to settle any of it.

The free tier and on-device privacy are real strengths, and self-motivated users who work mostly in daylight hours may find the week view useful. For most people, though, the app is a niche experiment rather than a dependable screen-time tool. We rate it Mixed, and we recommend the free week view as the only sensible starting point; most others can skip it.