Twilock is built by Hussain Taheri, a University of Florida computer science student who wanted a screen time blocker focused on the moments when his own rules were easiest to renegotiate.
Why night and morning?
General productivity apps tend to grow toward more rules, more modes, and more analytics. Those tools can be useful, but they also ask you to design a whole system.
Twilock begins with a narrower observation: for many people, unwanted scrolling is not evenly distributed across the day. It clusters before sleep, when “one minute” expands, and after waking, when the first app sets the tone for the next hour.
That led to two named windows, each capped at two hours, and a product that gets out of the way outside them.
Why Strict Mode?
A block is not very useful if the same tired version of you who wants to scroll can remove it in seconds. Strict Mode gives more weight to the decision made earlier, while retaining a recovery path for genuine need.
The goal is not punishment. It is commitment: a little distance between impulse and action, applied only where you asked for it.
What Twilock values
Focus over feature count
Twilock is not trying to become a task manager, calendar, timer, and wellness platform at once.
Privacy in the core loop
Your selected apps and raw Screen Time usage stay on your device.
Honest trade offs
A two hour cap and iPhone only scope are constraints, not hidden weaknesses. Broader blockers fit broader needs.
Calm commitment
The product should protect a choice without shaming the person who needed help keeping it.
Built in Gainesville, used wherever the night scroll begins
Hussain studies computer science at the University of Florida and builds Twilock independently. Product questions, bug reports, and honest feedback are welcome at twilockapp@gmail.com.
If Twilock is too narrow for your needs, our comparison guides say so. The point is to help you choose a boundary you can live with not to turn every screen time problem into a Twilock shaped one.