| type | Documentation |
|---|
A minimal iPhone utility that blocks shieldable apps except a user-selected allowlist using Apple's Screen Time APIs.
Choose up to 50 individual apps that stay available. Enable or disable the restrictions, either in the app or through two Shortcuts actions. Changes to the allowlist also apply while the mode is enabled. Calm Down itself is exempt from its all-category shield.
One screen, one allowlist, on and off. No timers, schedules, reports, accounts, advertising, subscriptions or backend. No runtime dependencies. English and German interface.
- iPhone with iOS 17 or later.
- Xcode 26 or later (the iOS 26 SDK is required to compile the availability-gated modern App Intents declaration).
- An Apple Developer Program team supporting Family Controls for installation on a physical iPhone. A free Personal Team cannot provision this capability.
Open CalmDown.xcodeproj. The project is included; XcodeGen is not required to build it.
Unsigned device compilation:
xcodebuild -project CalmDown.xcodeproj -scheme CalmDown \
-destination 'generic/platform=iOS' \
-derivedDataPath build/device CODE_SIGNING_ALLOWED=NO buildList installed simulators, choose an available iPhone UDID, then test:
xcrun simctl list devices available
xcodebuild -project CalmDown.xcodeproj -scheme CalmDown \
-destination 'platform=iOS Simulator,id=YOUR_SIMULATOR_UDID' \
-derivedDataPath build/simulator CODE_SIGNING_ALLOWED=NO testThe GitHub Actions workflow compiles for iPhone and runs the unit tests on an available iPhone simulator. It uses no signing credentials. Simulator tests do not establish real-device Screen Time or notification behavior.
Only when changing project structure: install XcodeGen and run xcodegen generate from project.yml.
- In Xcode Settings → Accounts, sign in with the Apple Account belonging to the intended developer team.
- In the CalmDown target's Signing & Capabilities, select that team. Automatic signing is enabled; no team ID is committed. Intended publisher: LABISO GmbH.
- Verify Family Controls is present. The bundle identifier is
de.labiso.calmdown; change it if your team cannot register it. - Connect and trust your iPhone. Enable Settings → Privacy & Security → Developer Mode if requested, restart and confirm.
- Select the iPhone as destination and run. Approve individual Screen Time access on the phone.
- Select individual apps, tap Save, then explicitly enable Calm Down. Setup never enables restrictions automatically.
Development signing is not permanent distribution; profiles expire and may require rebuilding. To release through TestFlight or the App Store, obtain the separate Family Controls distribution entitlement and complete Apple's applicable review. No App Store submission is part of this repository's initial setup.
In Apple's Shortcuts app, add Calm Down → Enable Calm Down or Calm Down → Disable Calm Down. In German: Calm Down einschalten and Calm Down ausschalten. Assign your resulting shortcuts to an Action Button or automation as desired.
Both actions use the same manager as the interface. They are intended to run without opening the app. iOS 26+ explicitly declares background mode; earlier systems use AppIntent's default background behavior. Actual discovery and execution, including from the lock screen, require device testing.
Enable refuses missing authorization, missing/corrupt configuration, empty selections, category/website selections and more than 50 apps. Disable always attempts to clear Calm Down's own store, even if setup is missing or permission was revoked.
CalmDownSettings: native Codable selection persisted in this app's UserDefaults; validation before writes.CalmDownManager: one main-actor manager and one namedManagedSettingsStore("CalmDown"); individual authorization and.all(except:)policy.ContentView: native FamilyActivityPicker with an editable draft; Cancel preserves the previous selection.CalmDownIntents: the two actions and their App Shortcuts.
The status comes from the app's configured store policy and current authorization, not a separately persisted Boolean. It is not an independent proof that iOS is enforcing every restriction. Revoked authorization invalidates the stored selection. No extensions, App Groups or DeviceActivity are needed for this version.
Selections stay in the app's local storage. Family Controls provides opaque tokens; Calm Down does not request usage history or resolve application identifiers. There is no account, server, telemetry, advertising or application network code. System services and device backups remain governed by your Apple settings.
PrivacyInfo.xcprivacy declares UserDefaults access for this app's own settings (CA92.1), no tracking and no collected data.
- Only apps that iOS permits shielding can be restricted. This is voluntary self-management, not tamper-proof parental control.
- Apple's picker also exposes categories and websites. Choose individual apps only; unsupported selections are rejected explicitly.
- The allowlist is limited to 50 application tokens by Apple.
- This version does not implement website filtering. Websites accessible through an allowed browser are outside its scope.
- Disabling clears only Calm Down's named store. Restrictions from other apps or system Screen Time settings may remain.
- Notification behavior has not yet been verified on a physical iPhone. Suppression of notifications from blocked apps is a release acceptance requirement. Do not infer it from a successful build or claim universal suppression.
- Blocking can hide important communications or prevent access to critical apps. Keep medical, security and other critical apps available. Test the selection before relying on it.
- No uninterrupted, error-free or complete operation is guaranteed. This is not a medical, emergency or safety product. Use at your own risk to the extent permitted by applicable law. Mandatory liability and statutory consumer rights remain unaffected.
The proposed German listing and notices are in STORE_DESCRIPTION.md. They require legal review before a public App Store release; neither an MIT license nor a listing disclaimer eliminates mandatory liability.
See MANUAL_TESTING.md. The release remains unverified until the physical-device checks are recorded there. No screenshots are included until actual app screenshots are available.
MIT.