v1.5.1

Fixes

• Camera apps can no longer be blocked. The safety list (dialer, SMS, settings, system UI, launcher) now also covers stock camera apps across major OEMs — AOSP, Pixel, Samsung, OnePlus/Oppo, Xiaomi, Huawei, Motorola, Snapdragon, Sony, and Asus. The website always promised this; now the code delivers it.

No other changes from v1.5.0.

v1.5.0

Strict Mode

New in Settings → Strict Mode (off by default):

• A running session can only be stopped by scanning your tag or QR code while TapBlok is open. Background scans leave the session running and post a notification telling you to open the app first.
• Scanning on a block screen no longer ends the session — it unlocks just that one app for a limited time (1 / 5 / 10 / 30 minutes, your choice), then drops you back into the app. The block screen also has a "Scan QR to Unlock" button for QR users.
• Combine with zero breaks and a disabled emergency override for maximum friction.

Your QR code is now unique

Every install now generates its own QR code instead of the shared one from older versions.

Action needed if you printed a QR code before v1.5.0: print a new one from "Show QR Code". Old printed codes no longer work (the app will tell you if it sees one). NFC tags are unaffected and keep working as-is.

Also

• "Write NFC Tag" and "Show QR Code" are disabled during a session, so a new unlock credential can't be created mid-session.
• The block screen closes itself when it leaves the screen instead of lingering in the back stack.

Strict mode is brand new — if a tag scan behaves unexpectedly on your device, please open an issue with your phone model.

v1.4.0

New

• Settings screen — new entry on the main menu. All settings lock while a session is active, so limits can't be loosened mid-session.
• Configurable emergency override — set the hold time to 30s, 90s, 5m, or 15m, or disable the override entirely. With it disabled, only your NFC tag or QR code can stop a session.
• Configurable breaks — choose 0, 1, 3, or 5 breaks per session. Zero removes the "Take a Break" button.
• Scheduled blocking — sessions start automatically at a chosen time on chosen days, with an optional auto-stop time. Overnight windows (e.g. 22:00-07:00) work, and schedules survive reboots. Uses exact alarms so it fires on time even in battery saver.
• Automation support — enable "Allow automation apps" in Settings and Tasker, MacroDroid, or Samsung Routines can start/stop sessions by broadcasting com.cj.tapblok.SCHEDULE_START / com.cj.tapblok.SCHEDULE_STOP. Off by default. See the README for setup examples.

Scheduling is brand new, so if an alarm fires late or not at all on your device, please open an issue with your phone model and battery settings.

v1.3.0

Fixes

• Manage Blocked Apps crash (#11, #12, #14, #16): apps with more than one launcher entry (Tasker, some MIUI/OnePlus/Samsung system apps) created duplicate rows in the list, which crashes Compose the moment the duplicate scrolls into view. The list is now deduped by package name. The special-character theory was a coincidence, the duplicate just happened to sit near those apps in the sorted list. Thanks to @bbendes for the exact diagnosis.
• Blocking dying mid-session (#20), four fixes here:
  • Foreground detection now uses usage events instead of usage stats, so apps that were already open before a session started get caught.
  • The service restarts itself if you swipe TapBlok away in recents.
  • Reopening TapBlok resumes a session the OS killed.
  • "Take a Break" no longer silently disabled the service restart protection for the rest of the session.
• Notifications: Android 13+ now asks for notification permission, so the "TapBlok is Active" notification actually shows.
• App icons in the blocked apps list load more smoothly, and an app being uninstalled while the list is open can no longer crash it.

New

• Search field in Manage Blocked Apps (#21).

v1.2.1

Bug fixes

Fixes crash on MIUI devices when opening "Manage Blocked Apps" (#10)

Two bugs caused the activity to crash back to the home screen on MIUI:

1. activityInfo null crash — MIUI's queryIntentActivities can return results with a null activityInfo. The package name was read from it outside the existing try-catch, so the resulting NullPointerException propagated to the main thread and crashed the activity.

2. Eager icon loading — all app icons were loaded into memory at once before the list rendered. On devices with many apps installed this could trigger an OutOfMemoryError that also escaped the try-catch.

Icons are now loaded lazily per row via Coil so only visible icons are held in memory at any time.

v1.2.0

What's changed

• Stop button removed during active sessions — the only ways to end a session are now NFC tag, QR code scan, or the 90-second emergency hold. The stop button was too easy to tap on impulse, defeating the purpose of physical friction. (Closes #9)
• Redesigned landing page at tapblok.com with cleaner typography and an expanded FAQ covering Android-version-specific permission setup (MIUI, EMUI, Samsung One UI, OnePlus, Android 12+)

Download

Install TapBlok-v1.2.0.apk directly on your Android device (Android 7.0+). You may need to allow installation from unknown sources in your device settings.

v1.1.0 — UI Modernisation

What's new in v1.1.0

UI Modernisation

• Brand colour scheme — replaced the default Material 3 purple palette with TapBlok's green/teal brand colours across both dark and light themes
• Typography — expanded type scale with SemiBold headlines and a consistent weight hierarchy throughout
• Main screen — redesigned with a status card, full-width Start/Stop button with icon, and a grouped actions card (Manage Apps, Write NFC, Show/Scan QR) with icons and chevrons
• Blocking screen — app icon with a lock badge overlay, calm dark surface background, full-width action buttons
• NFC write screen — large NFC icon in a branded circle, clear instructional copy
• Permissions screen — security icon with descriptive copy replacing plain text

TapBlok v1.0.0

Download

Tap the TapBlok-v1.0.0.apk file below to download and install directly on your Android device.

Note: Android will ask you to allow installation from unknown sources the first time. This is normal for apps installed outside the Play Store.

What's in this release

Initial stable release of TapBlok — a digital wellbeing app that puts your distracting apps behind an NFC tag or QR code.

Features

• Block any app on your device behind an NFC tag or QR code
• 5-minute break system (3 breaks per session)
• Emergency 90-second hold to force stop
• Launcher shortcut to start a session without opening the app
• Auto-resumes monitoring after device reboot if a session was active

Requirements

• Android 7.0 (API 24) or higher
• NFC-capable device (for NFC features)
• Usage access permission
• Overlay permission