Über
Hi,
We are exploring the development of a mobile focus application that works together with a physical NFC device. The app falls in the same category as Brick, Unpluq and TapOut, but with our own concept, positioning and long-term vision.
The core idea is simple but technically ambitious:
A mobile app that uses a physical NFC device to activate and deactivate OS-native app blocking via predefined focus modes, with emergency unlocks and basic session tracking.
We are currently in an exploratory phase. Our main goal at this stage is to assess technical feasibility, architecture, approach and cost. We are looking for a technically strong developer who understands system-level mobile functionality and long-term maintainability.
⸻
Concept Overview
The app creates intentional friction by requiring a physical NFC tap to activate and deactivate focus mode.
It must rely strictly on OS-native solutions:
• iOS: Screen Time / Family Controls
• Android: Digital Wellbeing or official system-level mechanisms
• No hacks
• No accessibility workarounds
• No fake blocking overlays
The product must be technically correct and maintainable, not a quick workaround.
⸻
High-Level Workflow
1. Onboarding & Setup
1. User downloads and opens the app.
2. App shows onboarding explaining:
• Selected apps (and optionally websites) will be blocked.
• A physical NFC device is required to activate and deactivate focus mode.
3. App guides user through required system permissions:
• iOS: Screen Time configuration
• Android: Digital Wellbeing style permissions and system access
4. App validates setup:
• Confirms blocking permissions are active.
• Confirms NFC availability.
5. User pairs the physical NFC device:
• User taps phone on NFC device.
• App stores NFC identifier locally.
6. App confirms successful pairing.
Result: The system is ready to block and unblock.
⸻
2. Focus Modes / Profiles
Users can create one or more focus modes (e.g. Work, Study, Sleep).
For each mode, the user can configure:
• Blocked apps (select specific apps to block), or
• Allowed apps (everything blocked except selected essentials).
The app remembers the last active mode as default.
Result: Predefined focus configurations exist.
⸻
3. Activating Focus Mode (Lock ON)
1. User selects a mode (or uses previously selected one).
2. User taps phone on the physical NFC device.
3. App verifies NFC identifier.
4. App immediately applies system-level restrictions:
• iOS Screen Time, or
• Android Digital Wellbeing mechanisms.
5. App switches to "Focus Active" state.
6. App displays:
• Current mode name
• Lock status
• Elapsed focus time (automatic timer)
Result: Selected apps (and optionally websites) are blocked at OS level.
⸻
4. Behavior During Focus Mode
1. User attempts to open a blocked app.
2. Access is prevented via OS-native blocking.
3. Where possible, a block screen displays:
• Lock status
• Active mode
• Elapsed time
• Instruction to unlock via NFC device.
4. Allowed apps remain accessible.
5. Notifications from blocked apps are suppressed where supported by the OS.
Result: Real friction and reduced distraction.
⸻
5. Deactivating Focus Mode (Unlock)
1. User taps phone on the NFC device again.
2. App verifies NFC identifier.
3. Optional short confirmation.
4. App removes system-level restrictions.
5. Focus timer stops.
6. Completed focus session is logged.
Result: Device returns to normal usage state.
⸻
6. Emergency Unlock (Failsafe)
While focus mode is active, the user can access an "Emergency Unlock" option in settings.
• Limited number of emergency unlocks.
• Must remove system-level restrictions correctly.
• Session logged accordingly.
⸻
Technical Expectations
• iOS and Android app (Flutter or React Native preferred, with native modules where required)
• Strictly OS-native blocking only
• NFC integration for activation/deactivation
• Clean, structured and well-documented code
• Clear separation between:
• UI layer
• Business logic
• OS-level permission and blocking layer
• Maintainable and transferable codebase
• GitHub repository owned by us from day one
• Architecture that allows future expansion without technical debt
We care more about correctness, structure and long-term maintainability than speed or shortcuts.
⸻
Current Phase
This is an early-stage product exploration.
Next steps depend on:
• Technical feasibility
• Proposed architecture
• Cost alignment
• Realistic timeline
We are looking to collaborate with the right technical partner who understands system-level mobile features and can think beyond surface-level app development.
⸻
What We'd Like From You
Please share:
• Relevant experience (especially with:
• iOS Screen Time / FamilyControls
• Android Digital Wellbeing or system-level APIs
• NFC integration
• OS-level permissions)
• Preferred tech stack and why
• Rough timeline
• Rough price range estimate
• Any technical considerations or risks you foresee
• Any questions from your side
We are currently evaluating approaches and want to build this in a realistic, scalable and technically sound way.
Thanks in advance.
Contract duration of 1 to 3 months.
Mandatory skills: Android, Mobile App Development, Android App Development, iOS Development, Smartphone, Native App Development, Swift, Kotlin, Dart
Sprachkenntnisse
- English
Hinweis für Nutzer
Dieses Stellenangebot stammt von einer Partnerplattform von TieTalent. Klicken Sie auf „Jetzt Bewerben“, um Ihre Bewerbung direkt auf deren Website einzureichen.