1. Enable passcode 2. Kill the app 3. Open the app 4. Type a wrong passcode three times -> brute force protection, user has to wait an incremental amount of time before a new attempt. With a video: https://github.com/user-attachments/assets/210ccde0-ef72-44a7-a06e-b8547ebbd177 That's correct ✅ , but i'd go for a couple of improvements in the UI: - While the time counter is on screen, the soft keyboard is clickable. It shouldn't be clickable or be hidden - The message `Incorrect passcode` should be gone when the time counter finishes and user is able to make a new attempt As example, this is how iOS app does: https://github.com/user-attachments/assets/12864796-4b93-411d-92d3-a54308cbb4dd ### TASKS - [ ] Research (if needed) - [ ] Create branch feature/feature_name - [ ] Development tasks - [ ] Implement whatever - [ ] ... - [ ] Implement unit tests (if needed) - [ ] Code review and apply changes requested - [ ] Design test plan - [ ] QA - [ ] Merge branch feature/feature_name into master
With a video:
Screen_recording_20260528_103635.mp4
That's correct ✅ , but i'd go for a couple of improvements in the UI:
Incorrect passcodeshould be gone when the time counter finishes and user is able to make a new attemptAs example, this is how iOS app does:
ScreenRecording_05-28-2026.10-38-36_1.MP4
TASKS