From install to enforced in five minutes
Here's what setup looks like, and how TymedIn behaves on the device once it's running.
First-run setup
The onboarding flow walks you through the whole thing; here are the five real steps.
Install and grant permissions
TymedIn needs a handful of Android permissions to enforce limits: overlay, usage stats, accessibility, notifications, and a battery exemption. The onboarding flow walks you through each one.
Set a parent password
Pick a password and a recovery question. Both stay on the device.
Create profiles
One per family member who shares the device, or one for weekday vs weekend. Each profile keeps its own apps and limits.
Pick apps to manage
From the Apps tab, bring the apps you want to cap under TymedIn's management. Anything not on the list is unrestricted.
Set the limits
For each managed app, set per-launch and per-day soft and hard caps, plus an optional cooldown. The stricter cap always wins.
What happens on the device
Once limits are set, here's how enforcement plays out in the background.
TymedIn watches the foreground
When one of your managed apps comes to the front, TymedIn starts the timer in the background. No popup, no warning to the kid.
A gentle warning first
As time runs low, the screen dims and the volume fades. Kids get a clear signal before they're cut off.
Then a full block
Once time's up, the app is blocked. Re-launching it just lands on the home screen.
Cooldown keeps it that way
After a hard cap, the app stays blocked for the cooldown you set, even if they quit and try again right away.
Limits reset at midnight
Per-day limits reset at local midnight. Per-launch limits reset when the app closes.
Settings stay locked
Changing limits, switching profiles, or opening sensitive Android settings needs the parent password.
Time changes can't cheat it
Rebooting the phone or changing the system clock can't reset today's usage.
Sound like what you've been looking for?
Get the launch announcement and a setup guide the day TymedIn ships.
Notify me at launch