anchor

# Build a Production-Quality Mobile App: Physical Commitment App Blocker I want you to design and build a polished native mobile application for iOS and Android. This must NOT be a fake prototype or a web app wrapped in a mobile shell. The app is a serious digital wellbeing / anti-distraction product whose core idea is: > The easiest way to unlock distracting apps should be to physically move away from the phone. Working product name: **Anchor** You may propose a stronger premium brand name before finalizing the visual identity. --- # 1. CORE PRODUCT IDEA Users select distracting applications on their phone, such as: * TikTok * Instagram * YouTube * X * Reddit * games * browsers * dating apps * any other supported installed application or app category The user then creates a lock rule. Once the rule activates, those apps become inaccessible. The important difference from normal app blockers is that the user should NOT simply be able to press: "Unlock" Instead they must complete a previously selected physical action. Primary unlock methods: ### NFC Unlock The user pairs a physical NFC card, NFC sticker, NFC keychain, or compatible NFC tag. Example: The user puts an NFC tag in their kitchen. At night they start a Focus Lock. Instagram, TikTok and YouTube become inaccessible. To unlock them again, they must physically get out of bed, walk to the kitchen and scan the NFC tag. ### Location Unlock The user chooses a geographical location on a map. Example: * lock distracting apps when arriving at school * lock apps when entering the gym * lock apps when arriving at the library * only allow unlocking after leaving home * activate automatically when entering a specific location Use proper mobile geofencing rather than continuously polling GPS. Support: * enter location * leave location * dwell at location * configurable radius * map picker * saved locations Do not describe location detection as perfectly exact. Design around realistic mobile geofence accuracy and possible delays. ### Scheduled Lock Users can create rules such as: * every weekday 08:00–14:30 * every evening after 22:30 * every Sunday morning * custom recurring schedules ### Timer Lock Examples: "Block these apps for 90 minutes." "Block them until 17:30." "Block them until I scan my NFC card." --- # 2. THE MOST IMPORTANT FEATURE: COMMITMENT MODE Normal digital wellbeing applications are easy to bypass. I want this product to intentionally introduce friction. Create three levels. ## FLEXIBLE Users can stop a session from inside the app. Useful for beginners. ## FOCUSED Stopping early requires: * confirmation * Face ID / biometric authentication * selecting a reason * waiting through a short cooldown Show the user how much time remains before they quit. ## STRICT This is the main differentiating mode. Once a Strict session begins: * the user cannot simply press an in-app stop button * changing the active rule is blocked * removing the paired NFC unlock method during the session is blocked * deleting a saved unlock location during the session is blocked * changing the clock must not bypass the timer where the operating system allows this to be prevented * restarting the app should restore the lock state * restarting the phone should restore the lock state whenever the OS provides a legitimate supported mechanism * killing the app should not silently cancel the session * backend connectivity must NOT be required to keep a local lock active However: NEVER use exploits, malware-like persistence, deceptive accessibility techniques, hidden services, undocumented security bypasses, or behavior that violates Apple App Store or Google Play rules. Use ONLY legitimate OS APIs. If Android Device Owner / Device Policy Controller capabilities are required for the hardest level of protection, implement this as a clearly explained OPTIONAL Advanced Protection mode with explicit user setup. Do not pretend normal Android permissions can provide Device Owner functionality. On iOS use Apple's official Screen Time frameworks: * FamilyControls * ManagedSettings * DeviceActivity * ManagedSettingsUI where appropriate Support individual self-control authorization where available. Clearly document OS limitations. Do NOT fake an "uninstall-proof" feature on platforms where it is impossible. If parental/family-managed authorization provides stronger deletion protection than individual authorization, keep the architecture capable of supporting a future Family Mode. --- # 3. EMERGENCY SAFETY Strict mode should create commitment, not make the phone unsafe. Never block essential system functionality required for: * emergency calling * emergency services * critical OS dialogs * accessibility * authentication required by the operating system Create an Emergency Escape mechanism. It should intentionally have high friction. Example: Emergency Unlock → explain why → biometric confirmation → 60-second countdown → second confirmation → temporarily restore access Record emergency unlocks locally in user statistics. Allow the user to configure whether Emergency Escape is available, but never circumvent mandatory platform safety behavior. --- # 4. APP SELECTION Make selecting apps extremely easy. The app selection screen should feel similar to native Screen Time interfaces. Features: * installed application list where platform allows it * app categories * search * Select All * social media category * entertainment * games * browsers * shopping * custom groups Allow users to create presets such as: WORK STUDY SLEEP GYM MORNING DEEP FOCUS Example preset: STUDY Blocked: Instagram TikTok YouTube Reddit Games Allowed: Messages Phone Spotify Calculator School apps --- # 5. NFC SYSTEM NFC is a first-class feature, not a gimmick. Create a polished onboarding flow: Settings → Unlock Methods → Add NFC Key → Scan NFC tag → Give it a name → Test NFC key → Save Example names: Kitchen Desk Car Gym locker Backpack Bathroom mirror Support multiple NFC keys for Pro users. Store NFC credentials securely using platform secure storage. Never store sensitive unlock secrets as plaintext. Design the system so NFC validation can work offline. If using ordinary NFC tags that can technically be cloned, do NOT market them as cryptographically uncloneable. Keep the architecture open for future support for secure cryptographic NFC hardware. Provide haptic feedback and a strong successful-scan animation. Successful scan: ANCHOR RELEASED Focus session complete 1h 42m focused --- # 6. LOCATION LOCKING Users can create saved locations. Examples: HOME SCHOOL OFFICE GYM LIBRARY Use: * map * search * current location * draggable pin * radius selector Possible rules: WHEN I ENTER → start lock WHEN I LEAVE → start lock ONLY UNLOCK AFTER I LEAVE UNLOCK WHEN I ARRIVE Use dwell detection where possible to prevent accidentally triggering a rule when briefly passing nearby. Explain background-location permissions clearly during onboarding. Do not continuously collect location history. The backend should not receive precise location unless absolutely required. Prefer on-device geofence evaluation. --- # 7. SMART AUTOMATION RULES Build a flexible rule engine. A rule contains: TRIGGER * APP GROUP * LOCK MODE * UNLOCK CONDITION Examples: Every weekday at 22:30 + Social Media + Strict + Scan "Kitchen NFC" or: Enter School + Games + Social Media + Strict + Leave School or: Start manually + Study preset + Focused + 2 hours The UI for creating this should be extremely visual and simple. Do not expose complicated programming terminology to normal users. --- # 8. HOME SCREEN The home screen should instantly answer: Am I locked? How long? What is blocked? How do I unlock? Suggested layout: Top: ANCHOR Large central focus ring. Inside: 1:34:21 FOCUS ACTIVE Below: 12 apps blocked Unlock: Kitchen NFC Then: TODAY 3h 42m protected 4 successful sessions 0 early escapes Large primary CTA while unlocked: START FOCUS Do not overcrowd the dashboard. --- # 9. LIVE LOCK SCREEN When apps are blocked, show a beautiful custom shield screen wherever the operating system permits it. Example: FOCUS ACTIVE You chose this for a reason. Instagram is unavailable. Unlock method: Scan "Kitchen NFC" 1h 13m remaining Do not display a convenient bypass button. Use motivational text sparingly. Avoid cringe quotes. Allow users to customize the message. Examples: "Go finish what you started." "Not now." "You asked us to stop you." --- # 10. PREMIUM MEMBERSHIP Create a complete subscription system. Use native App Store / Google Play subscriptions. Use a production-ready subscription abstraction such as RevenueCat if appropriate. Do not use Stripe directly to unlock digital mobile-app subscription features if doing so would violate App Store / Play billing requirements. Create: ANCHOR FREE and ANCHOR PRO ## FREE * manual focus sessions * select apps * basic timers * 1 app preset * 1 NFC unlock key * limited statistics * basic lock mode * light + dark themes ## PRO Unlock: * unlimited NFC keys * unlimited saved locations * unlimited presets * automatic schedules * geofence automation * Strict Mode * advanced analytics * weekly/monthly reports * streak history * Focus Score * cross-device account backup where technically meaningful * custom lock-screen messages * custom app groups * advanced rules * widgets * home-screen quick actions * premium themes * session history * data export * future Family / Accountability features Create: MONTHLY YEARLY and make the yearly option visually recommended. Prices must be stored as configurable product identifiers rather than hardcoded throughout the application. Use proper restore-purchases functionality. Provide a development/mock subscription state so the application can be tested without real purchases. Never lock users' own historical data behind a manipulative paywall. --- # 11. TRIAL Offer a tasteful optional free trial. Example: 7 DAYS ANCHOR PRO During onboarding show premium only after the user understands the core feature. Do not immediately hit new users with a paywall before they see the product. Suggested funnel: Welcome → Goal → Select distracting apps → Choose unlock method → Complete first focus session → Introduce Pro --- # 12. GAMIFICATION Keep it sophisticated. Do not make the app feel childish. Track: * Focus Time * Sessions Completed * Strict Sessions * Emergency Escapes * Daily streak * Weekly streak * Apps blocked most often * Saved distraction time * NFC unlock locations * Focus Score Focus Score could consider: successful sessions + focus duration + strict-session completion ------------------------- early escapes Show charts for: Today 7 days 30 days All time Do as much computation locally as practical. --- # 13. STREAKS Create a tasteful streak system. Example: 14 DAY STREAK You protected 27h 18m of focus time this week. Never design streaks to punish users emotionally for missing one day. --- # 14. ONBOARDING Build an exceptional onboarding experience. Screen 1 OWN YOUR ATTENTION. Your phone should open when you decide — not when a notification decides for you. Continue --- Screen 2 WHAT DO YOU WANT TO PROTECT? Study Sleep Work Morning Gym Time with people Custom --- Screen 3 CHOOSE YOUR DISTRACTIONS Select apps / categories. --- Screen 4 HOW HARD SHOULD IT BE TO QUIT? Flexible Focused Strict Explain them clearly. --- Screen 5 MAKE UNLOCKING PHYSICAL Recommended: NFC CARD Other options: Location Timer --- Screen 6 Permissions setup. Explain every permission before displaying the OS permission dialog. Never request every permission immediately at startup. Use progressive permission requests. --- # 15. DESIGN DIRECTION This application must look like a premium 2026 consumer product. It should NOT look like: * a generic AI-generated dashboard * Bootstrap * a corporate admin panel * a crypto application * a cheap productivity template Visual direction: Calm. Minimal. Premium. Focused. Slightly futuristic. Highly tactile. Think: high-end fitness app + premium banking app + digital wellbeing product Use lots of negative space. Strong typography. Large numbers. Subtle gradients only where useful. Rounded cards. Smooth physics-based transitions. Tasteful haptics. Beautiful empty states. Beautiful loading states. Dark mode must be exceptional. Do not overuse glassmorphism. Create a cohesive design system: spacing typography corner radii elevation icon size animation timing haptics light/dark tokens Use proper accessibility contrast. Support Dynamic Type / font scaling where practical. Touch targets must be comfortable for one-handed mobile use. --- # 16. NAVIGATION Use a simple bottom navigation: HOME RULES INSIGHTS SETTINGS Home: current session Rules: automations / presets Insights: statistics Settings: account / NFC / subscription / permissions / security --- # 17. SETTINGS This section should be unusually complete. Categories: ACCOUNT SECURITY LOCKING NFC KEYS LOCATIONS AUTOMATIONS NOTIFICATIONS APPEARANCE DATA & PRIVACY SUBSCRIPTION HELP ABOUT Include settings such as: Default lock level Default unlock method Emergency Unlock Emergency Unlock delay Haptics Sounds Notifications before lock begins Session completed notification Dark / Light / System theme App icon alternatives for Pro if supported Weekly summary Focus reminders First day of week Data export Delete account Delete local data Restore purchases Manage subscription Permission status diagnostics --- # 18. ANTI-BYPASS ARCHITECTURE This is extremely important. Threat-model reasonable bypass attempts: * force-closing the app * phone restart * application process death * changing system time * losing internet * removing NFC key from app configuration * changing active rule * revoking permissions * removing background location * uninstalling the application * clearing application data * operating-system updates For EACH platform create a capability matrix: SUPPORTED PARTIALLY SUPPORTED NOT POSSIBLE THROUGH PUBLIC API Do not hide limitations. Never build fake security. Persist active session state securely. Use monotonic / system-supported timing approaches where applicable rather than trusting a mutable wall clock alone. After process restart, reconstruct the active lock state. If required permission is revoked, show a prominent diagnostics state when the application next becomes aware of it. --- # 19. ANDROID IMPLEMENTATION Investigate and use current official Android APIs. Build native Kotlin modules when React Native / Expo modules are insufficient. Possible technologies may include: * official Android NFC APIs * Android Geofencing APIs * secure storage * foreground/background services only where legitimate * DevicePolicyManager * Device Owner / DPC functionality ONLY for optional Advanced Protection where correctly provisioned * supported app-usage / accessibility APIs only when permitted by platform policies Do NOT use Accessibility Service solely as a deceptive mechanism to make uninstalling difficult. If Android Advanced Protection requires special device provisioning, create an onboarding tutorial and clearly identify it as advanced functionality. Provide two Android modes: STANDARD PROTECTION and, where realistically possible: ADVANCED DEVICE PROTECTION Do not pretend they provide the same guarantees. --- # 20. IOS IMPLEMENTATION Use official Apple frameworks where applicable: FamilyControls ManagedSettings DeviceActivity ManagedSettingsUI CoreNFC CoreLocation Create native Swift modules / Expo Modules where required. Use FamilyActivityPicker or equivalent official APIs for selecting controlled apps. Do not attempt private API usage. Do not claim to physically lock the entire iPhone if Apple APIs only allow shielding/restricting selected applications/categories. Design around platform limitations elegantly. If NFC background behavior cannot provide the exact intended interaction, create the closest policy-compliant UX rather than simulating a capability that doesn't exist. --- # 21. NATIVE BUILD REQUIREMENT Start from a React Native + Expo architecture if appropriate, but this app requires native functionality. Do NOT constrain the project to Expo Go. Use: Expo development builds / EAS and native modules written in: Swift for iOS Kotlin for Android where necessary. The application must be architected for real App Store / Play Store builds. --- # 22. ACCOUNT SYSTEM The core blocking functionality must work locally. Accounts should be optional until required by premium sync functionality. Possible account providers: Apple Google email magic link Avoid password complexity where possible. Store only necessary cloud information. Do not upload the user's app-usage history unless they explicitly enable sync. --- # 23. BACKEND Use a simple production-quality backend for: accounts subscription entitlement mirror if needed user preferences backup premium status optional analytics sync Do NOT make lock enforcement depend on the backend. A lost internet connection must not unlock a Strict session. Use schema migrations. Use server-side authorization. Never trust subscription status supplied directly by the client. --- # 24. PRIVACY This application handles sensitive behavioral and location information. Follow privacy-by-design. Prefer local processing. Never sell user usage data. Never use precise location for advertising. Never store full location history unless a feature explicitly requires it and the user opts in. Provide: Privacy dashboard Export my data Delete my account Delete cloud data Delete local history Analytics opt-out Crash-reporting opt-out where feasible Clearly distinguish necessary telemetry from optional analytics. --- # 25. NOTIFICATIONS Useful notifications only. Examples: "Your Study lock begins in 10 minutes." "Focus active. 8 apps protected." "2 hours complete." "7-day focus streak." Do not spam users. --- # 26. WIDGETS Pro feature. Possible widgets: TODAY'S FOCUS ACTIVE SESSION START STUDY START SLEEP FOCUS STREAK Use native iOS/Android widget technology where required. --- # 27. HOME SCREEN QUICK ACTIONS Long-press the application icon: Start Study Start Sleep Start 1h Focus Open NFC Scanner --- # 28. ACCESSIBILITY Support: screen readers font scaling reduced motion high contrast large touch targets proper semantic labels Do not rely only on color for state. --- # 29. OFFLINE FIRST Core functionality must work without internet: starting a local session active app restrictions timer enforcement NFC validation where technically possible saved rules session completion local statistics Sync later when internet returns. --- # 30. DATA MODEL Design clean data models for at least: User Subscription AppGroup BlockedApplication LockRule Trigger UnlockCondition NFCKey SavedLocation FocusSession EmergencyUnlock UserSettings FocusStatistics Entitlement DeviceCapabilities PermissionState Keep platform-specific details out of generic business logic where possible. --- # 31. SOFTWARE ARCHITECTURE Keep these areas separated: UI navigation domain logic rule engine session state machine native device-control adapters NFC adapter location adapter subscription service analytics local persistence backend sync permissions platform capability detection Do not put everything into giant React components. Build reusable components. Use TypeScript strictly. Avoid `any` unless absolutely unavoidable. --- # 32. SESSION STATE MACHINE Treat focus locking as a real state machine. Possible states: IDLE SCHEDULED STARTING ACTIVE AWAITING_UNLOCK UNLOCKING COMPLETED EMERGENCY_EXIT ERROR The lock state must remain deterministic after an app restart. --- # 33. TESTING Create automated tests for important business logic. Especially test: timers rule activation rule conflicts session persistence restart recovery subscription entitlements NFC key validation logic location-trigger transitions emergency unlock timezone changes daylight saving transitions changing device time offline operation app process restart permission loss Create native integration tests where practical. --- # 34. ERROR STATES Design polished UX for: NFC unavailable NFC disabled wrong NFC card location unavailable background permission denied Screen Time permission removed subscription expired network offline rule conflict device feature unsupported Never leave the user on a blank screen. --- # 35. DEVICE CAPABILITY CHECK During onboarding automatically determine: NFC support platform OS version location support required permissions Screen Time authorization available blocking capability Advanced Protection availability Show: PROTECTION STATUS Example: App blocking ACTIVE NFC ACTIVE Location ACTIVE Restart recovery ACTIVE Advanced lock NOT CONFIGURED Make this screen visually excellent. --- # 36. MONETIZATION UX Subscription should feel premium rather than aggressive. Paywall example: ANCHOR PRO Make distraction physically harder. ✓ Strict Mode ✓ NFC unlock ✓ Location automation ✓ Unlimited rules ✓ Deep focus insights YEARLY Best Value MONTHLY START FREE TRIAL Restore Purchases Clearly show renewal terms as required by stores. --- # 37. FUTURE FEATURES — DESIGN FOR THEM, DO NOT OVERBUILD THEM NOW Keep architecture capable of later supporting: Apple Watch Wear OS Bluetooth physical unlock button NFC rings smart home triggers Shortcuts / App Intents Family Mode Accountability Partner shared focus sessions desktop companion browser extension Mac / Windows blocking Study groups Focus API Do NOT implement all of these in V1. --- # 38. MVP PRIORITY Do not attempt every feature simultaneously. Build in this order: PHASE 1 Design system Navigation Onboarding Local models App selection UI Session state machine Mock blocking adapter PHASE 2 Real iOS application shielding Real Android application restriction where legitimate Permissions Restart recovery PHASE 3 NFC pairing/unlocking Location geofences PHASE 4 Rules Schedules Statistics Streaks PHASE 5 Accounts Subscription Pro entitlements RevenueCat or equivalent production subscription infrastructure PHASE 6 Widgets Advanced Protection Polish Store readiness At the end of every phase, run tests and verify the feature on actual platform capabilities. --- # 39. IMPORTANT DEVELOPMENT RULE Before writing large amounts of code: 1. Inspect current Replit/Expo capabilities. 2. Verify the latest official Apple and Android APIs. 3. Produce a short capability matrix for iOS and Android. 4. Identify which features require custom native Swift/Kotlin modules. 5. Identify what cannot be tested in Expo Go. 6. Create the architecture. 7. Then implement Phase 1. Do not silently replace difficult native functionality with mocks. Mocks are acceptable during Phase 1 only if clearly labeled. When a feature becomes part of a production phase, connect it to the real device API. --- # 40. DEFINITION OF DONE The project is not complete merely because screens render. A production-ready version should allow a real user to: install the app complete onboarding authorize necessary permissions select distracting apps create a lock preset pair an NFC tag start a focus session attempt to open a blocked app and actually be prevented/shielded by the OS scan the correct NFC tag have the selected apps restored create an automatic schedule create a location-triggered rule see focus statistics upgrade to Pro through sandbox subscription testing restart the phone/app without silently losing an active supported lock use the application offline and understand exactly what protection their device supports. The final result should feel like a real startup-quality consumer product that could reasonably be submitted to the Apple App Store and Google Play — not a hackathon prototype. Start by giving me: 1. the final recommended product name, 2. the platform capability matrix, 3. proposed architecture, 4. screen map, 5. Free vs Pro feature table, 6. implementation phases, 7. major technical risks. Then proceed with Phase 1.