Zenith: A Material 3 Expressive Digital Wellbeing App for Android

What Zenith Actually Targets

Zenith is built for one specific problem: the automatic, repetitive opening of apps and websites that eats time without intent. The README describes it as a smart digital wellbeing assistant that uses proactive interventions and real-time monitoring. That means it does not just log your usage; it tries to interrupt the habit loop at the moment you reach for a distracting app. The intended user is someone on Android who wants a local, configurable alternative to the built-in Digital Wellbeing, with more aggressive enforcement options like full-screen lock overlays and delayed reopening. It is not a passive tracker. The design language is Material Design 3 Expressive, which matters for the feel, but the core value is the intervention logic.

The Mechanism: Monitoring and Interruption

The app's architecture, as visible in the permissions and feature list, rests on a foreground service called AppUsageMonitorService. That service continuously tracks app usage, which requires the PACKAGE_USAGE_STATS permission. When a limit is hit, Zenith can display a shield overlay, a timer, or a full-screen lock. The overlay needs SYSTEM_ALERT_WINDOW. For faster detection of app opens, an optional accessibility service can catch the transition instantly. Without it, the app likely polls usage stats, which is slower. The notification listener service is another optional piece that hides distracting notifications during Focus sessions or Bedtime. So the data flow is: usage stats feed the monitor, the monitor checks against user-defined limits and schedules, and then it triggers one of several intervention types. The README lists many intervention modes: Shield Mode with mindful pauses, Delay App with a configurable timer before reopening, and Mindful Gateway which interrupts all non-whitelisted apps. These are distinct mechanisms, not just marketing names.

Getting It Running: Build and Permissions

Installation is not a simple APK drop for most users. The README instructs you to clone the repository, open it in Android Studio Ladybug (2024.2.1) or newer, and ensure Android SDK 33+ is installed. You build and run on a physical device, which is recommended for proper permission handling. The app then asks for a long list of permissions. The required ones include usage stats, system overlay, app list, notifications, Do Not Disturb access, foreground service, full screen intent, wake lock, and boot completed. Optional ones include accessibility service, notification listener, precise alarm scheduling, storage access, internet, and calendar access. The permission list is not just a formality; each one maps to a concrete feature. For example, READ_CALENDAR enables the Show Current Event feature in the intercept overlay. The README also flags a real constraint for Android Go devices: granting SYSTEM_ALERT_WINDOW through settings may not work, and you may need to use ADB with the command adb shell pm grant com.etrisad.zenith android.permission.SYSTEM_ALERT_WINDOW. That is a specific, actionable command, and it shows the app is not plug-and-play on every device.

The Feature Set: More Than Just a Timer

Zenith's feature list goes beyond simple app blocking. It includes Shield Mode, Goal Pursuit for productive apps, Delay App, Mindful Gateway, Bedtime Mode, Focus Sessions with BLOCK and ALLOW modes, website tracking and shielding across 12+ browsers, an alarm system with math challenge mode, Eye Care with the 20-20-20 rule, Grace Period windows, Incentive Lock with five tiers, a floating Session HUD, Early Kick reminders, interactive widgets, a streak system, and notification insights. That is a lot. The breadth suggests the developer has iterated based on user requests. But it also means the app is complex. Each feature likely has its own settings screen and configuration options, which could overwhelm a new user. The README does not provide a quick-start guide beyond the build steps, so you will be exploring the UI to understand how to set up a basic shield. The Incentive Lock is an interesting design: it progressively unlocks shields as you complete goals, which gamifies the restriction. That is a different approach from a simple hard block.

Limitations and Failure Modes

The most obvious limitation is the permission load. This app asks for nearly every sensitive permission Android has, except camera and microphone. That is a privacy red flag for some users, even though the app is open source and GPL-3.0. You have to trust that the code does what it says. Another limitation is the reliance on a foreground service for continuous tracking. That service can be killed by aggressive battery optimization on some devices, which the README acknowledges by listing battery optimization as an optional permission. If the service dies, monitoring stops, and shields may not trigger. The Android Go overlay issue is another concrete failure mode: on those devices, the app may not work as intended without ADB. Also, the accessibility service is optional, which means without it, the app's detection of app opens may be delayed. The README says it makes shields feel much more responsive, implying that without it, there is a lag. That lag could let you slip past a shield if you are quick.

Alternatives and the Difference in Approach

The obvious alternative is Android's built-in Digital Wellbeing, which ships on most devices. It tracks usage and offers app timers, but it does not do proactive interventions like full-screen lock overlays or mindful pauses. It is also not configurable to the level Zenith offers. Another alternative is the open-source app AppBlock, which also uses a usage access service and can block apps, but it typically does not include website tracking across browsers or the same gamified incentive system. The key difference is that Zenith is built around the Material 3 Expressive design and a broader set of intervention types, while Digital Wellbeing is a simple timer and AppBlock focuses on strict blocking. If you just need a daily limit, Digital Wellbeing is lighter. If you want to break the habit at the moment of opening, Zenith's approach is more aggressive. The choice depends on whether you need the extra enforcement or just a nudge.

Maintenance and Licence Implications

The repository is under the GPL-3.0 license, which means if you modify and distribute the app, you must make your source code available under the same license. For personal use, that is not a concern. The project is actively maintained, with releases v1.5.6, v1.5.7, and v1.5.8 pushed between June and July 2026. That suggests a regular release cadence, roughly monthly or more frequent. The README mentions backup and restore with automated periodic backups, which is useful for upgrades. However, the dependency on Android SDK 33+ means you need a recent Android Studio and device. The app is distributed via IzzyOnDroid and OpenAPK, which are third-party repositories, so you are not getting it from the Play Store. That means updates come from those sources or from building yourself. There is no mention of a Play Store listing, so you should expect to sideload. The maintenance cost for a user is low once installed, but you need to keep the app updated to get fixes, and you should verify that each update does not change the permission requirements.

Editorial conclusion

Adopt Zenith if you want a self-hosted, GPL-3.0 digital wellbeing tool with granular app and website blocking, and you are comfortable granting the listed permissions on a personal device. Do not adopt it if you need a lightweight solution or your device is Android Go, where overlay permission may require ADB. Before installing, verify that your Android version supports all required permissions, especially SYSTEM_ALERT_WINDOW and PACKAGE_USAGE_STATS, and check the latest release notes for any changes to permission handling.

Official sources

1. Official README
2. Project repository
3. Release notes