An open-source, self-hosted take on the NFC-tag phone brick. Stick a cheap NFC sticker to something you'd have to physically get up for. Tap it: the apps you chose stop opening. Tap it again: they come back.
No account, no subscription, no server. Nothing leaves your phone.
tap tag → App Intent / in-app scan → ManagedSettingsStore.shield = your apps
The lock is not clever, and pretending otherwise would be dishonest. Deleting this app clears every shield it holds — that's how Apple's Family Controls works, and every app in this category has the same hole. What actually does the work is the distance between you and the tag. Put it in a drawer, in the kitchen, in your bag by the door.
If you want the friction to hold against your own worst impulses, do what the commercial ones tell you to do:
Settings → Screen Time → Content & Privacy Restrictions → App Store, Media, Purchases & Shopping → Deleting Apps → Don't Allow, behind a Screen Time passcode you don't memorise.
You're not building a vault. You're building enough friction to interrupt the reflex.
| Brick-style apps | Paperweight | |
|---|---|---|
| Tags | one | as many as you like |
| Modes | one block list | one block list per tag — desk, gym bag, bedside |
| Escape hatch | hidden or absent | explicit weekly allowance, written into the ledger |
| Timed sessions | — | brick for N minutes, lifts itself |
| History | basic | every session, streaks, longest hold |
| Price | one-off hardware purchase | ~₹300 for a pack of NTAG215s |
Multiple tags is the real feature. One tag by the desk that kills social apps, one in the gym bag that kills everything except music and the workout tracker, one on the bedside table that kills everything with a feed after 11pm. Each tag is a place and a mode at the same time, which is something a single tag can never be.
Seal breaks are the honest answer to "the lock is soft". Instead of pretending you can't get out, you get a fixed number of emergency exits per week, and every one of them lands in the ledger with a timestamp. Measurement beats theatre.
Two paths, and you can use both:
1. Shortcuts automation (recommended, zero friction).
Shortcuts → Automation → NFC → scan your tag → run Toggle Paperweight and pick a
profile → turn off "Ask Before Running". Works with any blank tag, fires the instant
the phone touches it, doesn't need the phone unlocked or the app open. Paperweight
exposes four intents: Toggle Paperweight, Brick Apps, Unlock Paperweight,
Paperweight Status.
2. In-app scanner. Open the app, hit Hold to tag. Reads the tag's factory UID — nothing is ever written to the tag, so it can't be cloned by copying data off it. Use this to enrol a tag with a profile in the first place.
| Level | Unlock from app | Seal break | For |
|---|---|---|---|
| Soft | yes | n/a | your first week |
| Tag only | no | yes, weekly allowance | the default |
| Sealed | no | no | when you mean it |
- iPhone with iOS 17+ on a real device — Family Controls does not work in the simulator
- A paid Apple Developer account (the
com.apple.developer.family-controlsentitlement is not available to free personal teams) - XcodeGen —
brew install xcodegen - NFC tags: any NTAG213/215/216 sticker. A pack of ten costs about ₹300 / $4.
git clone https://github.com/kshah00/paperweight.git && cd paperweight
cp Config/Local.xcconfig.example Config/Local.xcconfig
$EDITOR Config/Local.xcconfig # your bundle prefix, app group, team ID
make # xcodegen generate && open Paperweight.xcodeprojThen in Xcode: select your device, ⌘R. See SETUP.md for the entitlement details and the things that go wrong.
Everything Paperweight does sits on four Apple frameworks. If you're reading this to
figure out how these apps work, the whole mechanism is about 250 lines in
Sources/Shared/Paperweight.swift.
- FamilyControls —
AuthorizationCenter.shared.requestAuthorization(for: .individual)gets permission;FamilyActivityPickerlets the user choose apps. You never receive bundle IDs, only opaqueApplicationTokens that are meaningless outside your app. - ManagedSettings —
store.shield.applications = tokensis the block. Each profile gets its own namedManagedSettingsStoreso two can be active without clobbering each other. - ManagedSettingsUI — a
ShieldConfigurationDataSourceextension draws the lock screen; aShieldActionDelegateextension handles its buttons. - DeviceActivity — a monitor extension so timed sessions lift themselves while the phone is in a drawer.
- AppIntents — the Shortcuts surface, which is what makes the NFC tap work without a banner to tap.
The app and its three extensions share state through one App Group. That's the only
channel between them, and it's why AppGroup.identifier fails loudly rather than
silently handing each target its own private store.
Sources/
Shared/ compiled into all four targets
Paperweight.swift the engine: profiles, shields, sessions, seal breaks
Profile.swift one tag + one app selection + a strictness level
Session.swift the ledger and the stats over it
App/ SwiftUI app, NFC scanner, App Intents
ShieldConfiguration/ what a bricked app looks like
ShieldAction/ what its buttons do
ActivityMonitor/ lifts timed sessions unattended
Issues and PRs welcome — see CONTRIBUTING.md. Good first things: Live Activity for a running session, a Home Screen widget showing the current hold, Apple Watch complication, sharing a profile as a file.
MIT. See LICENSE.
Not affiliated with, endorsed by, or derived from any commercial NFC-blocker product. Built from Apple's public Screen Time APIs.