Curbox for Android: App and Website Blocking with Usage Controls

Curbox's Android Blocking Problem

Curbox, formerly called Digipauwse, is designed for Android users trying to reduce the pull of apps and websites that interfere with focused work. Its target is not only total screen time. The README also describes controls for Instagram Reels, YouTube Shorts, application feeds, and selected website paths. That makes it more relevant to a person who wants to keep messaging or searching available while removing a feed that encourages repeated scrolling.

The project is intended for people who want to inspect the implementation of a digital wellbeing utility rather than rely only on a closed source application. The README states that the codebase is public and argues that this allows users to check how the app works. It also makes a narrower privacy claim: open source does not mean that anyone can see how an individual uses the application. The README does not describe a server account, cloud dashboard, or telemetry backend, so it supports an open source assessment, but it does not provide a complete technical privacy audit.

Curbox is an Android application in this repository. The README lists a separate Web Extension Repository and says iOS is coming soon. Those platform notes matter because a user who wants one control system across desktop and mobile should not treat the Android project as a complete multi-platform suite.

What Curbox Can Block and Measure

The documented feature set separates blocking, awareness, and temporary access. App and website blocking can remove access to selected distractions entirely. Curbox can also target short-form content such as Instagram Reels and YouTube Shorts. Its UI hiding controls are more selective than a blanket app block. The README gives examples including blocking a YouTube home feed while allowing searches, or hiding an Instagram feed while leaving posts and messages from friends available.

URL path blocking operates at a finer level than an entire website. The documented example blocks `m.youtube.com/shorts/*` while allowing `m.youtube.com`. This is useful when a site has both distracting and useful sections. The repository description also identifies Reels and Shorts blocking as central topics, so the application is aimed at a specific class of attention problems rather than general productivity management alone.

The usage features include app and website analytics, focus statistics, a live scroll counter, attention span tracking, and a session timer. The live counter is intended to show how many short-form videos have been scrolled through, while the session timer shows elapsed time since an app was opened. These features depend on Android's ability to observe usage and screen activity. The README does not specify the exact Android permission requests, background execution behavior, or accuracy limits for these measurements, so those points need direct verification in the app and its documentation.

Curbox also provides Focus Mode, scheduled Do Not Disturb, app-specific grayscale, scheduled usage limits, and home screen widgets. Scheduled limits can define a group, an active period, and a total allowance. The example permits one hour of WhatsApp use between 7 AM and 9 PM. That model is more useful than a single fixed deadline when several apps must share a controlled allowance.

Unlock Rules and Tamper Protection

Curbox does not leave the post-limit decision to a single behavior. The README documents Strict Blockade, which removes access after a scheduled allowance ends. Timed Unlocks provide a predefined short duration, such as five minutes, for later attempts. Dynamic Selection lets the user choose the temporary access duration at the time of the attempt.

A more demanding option is QR/Barcode Unlock. The user scans a physical QR code or barcode, with the README suggesting codes placed around the home to require physical movement. This creates friction after a limit expires, but the documentation does not describe what happens after a scan, how codes are stored, or whether a replacement code can be created. It also does not specify whether scanning is performed by Curbox or another Android component.

Tamper Protection is intended to make uninstalling Curbox or changing its configuration more difficult. That is a distinct feature from blocking an application, because it changes the failure mode when a user tries to remove the control tool. The README does not explain the Android mechanism used for this protection, whether device-owner privileges are involved, or how a legitimate user recovers access. Those omissions are significant for anyone considering Curbox on a personal device.

Installing Curbox and Making a First Use

The README does not provide installation commands, Gradle instructions, a minimum Android version, or a complete first-use procedure. It directs users to the Curbox documentation for step-by-step instructions and provides two download destinations: F-Droid and the latest GitHub release. The README also includes badges for both destinations, but it does not reproduce the steps required to install an APK or configure permissions.

For that reason, the reliable first step is to open the project's linked documentation and confirm the supported Android requirements before downloading a build. The user should then choose either the F-Droid package or the latest GitHub release and follow the documentation's setup instructions. The README does not state whether F-Droid installation and manual release installation have different permission flows.

After installation, the first useful action would be to configure one app or one website path as a limited test case rather than applying every control at once. The documentation supports choosing an app, setting a schedule, and selecting an unlock rule, but it does not give a precise screen sequence or a complete configuration example. The absence of exact UI steps makes a code example inappropriate here. Users should confirm the resulting block in the app and verify how the chosen unlock mechanism behaves after the allowance expires.

The repository includes `gradlew`, `build.gradle.kts`, and an `app/` directory, which shows an Android Gradle project layout. The README does not document build prerequisites or signing requirements, so building from source should not be treated as a documented installation path.

Curbox Compared with Basic Screen Time Controls

Curbox differs from a basic screen time tool through its granularity. A conventional usage limit may stop an app after a time allowance, while Curbox can block selected interface areas or a website path while leaving other functions available. It can also set different unlock behaviors, including a barcode challenge, rather than presenting only a generic warning or timer.

The trade-off is operational complexity. More controls mean more decisions about what to block, which parts of an app remain accessible, and what happens when a limit expires. Tamper Protection adds another layer that can make recovery harder. A user who wants one simple daily limit may find that Curbox offers more configuration than needed. A user dealing with short-form feeds may find the distinction between blocking the app and hiding only its feed more relevant.

The application is also Android-specific in the documented scope. The Web Extension Repository is listed separately, and iOS is described as coming soon. That makes Curbox different from a unified service that presents the same rules across devices, but the README does not explain synchronization or cross-platform policy management.

Open Source, Maintenance, and Upgrade Cost

Curbox is distributed under the `GPL-3.0` license. That license permits users to study and modify the source, subject to its terms, and it places obligations on redistribution and derivative works. This is a licensing fact, not legal advice. Anyone building a fork, distributing a modified APK, or incorporating Curbox code into another product should review the actual `LICENSE` file and comply with the applicable GPL-3.0 requirements.

The repository is not archived, and the last push was on 2026-10-15. Recent releases listed in the repository information include version 6 on 2026-10-15, version 4 on 2026-08-07, and version 3 on 2026-07-17. These dates indicate recent repository activity, but they do not establish how often future updates will arrive or whether every Android release will remain compatible with current devices.

Upgrade cost depends on the distribution channel and Android behavior. A F-Droid installation may receive updates through that ecosystem, while a GitHub release installation requires checking the release page. The README does not document automatic updates, migration between versions, database backup, or whether existing schedules and unlock configurations survive an upgrade. Those are the first items to verify for an existing user.

Editorial conclusion

Curbox fits Android users who want open source app blocking, website restrictions, and usage limits rather than a simple timer. It does not fit users needing documented cross-platform setup or an iOS release now. Verify the install documentation, permissions, Shizuku requirements if applicable, and the exact behavior of tamper protection before adopting it.

Frequently asked questions

Official sources

1. curbox-app/curbox-android on GitHub
2. License: GPL-3.0
3. Project website
4. README
5. Releases