Decision: biometric lock default scope #10
Labels
No labels
bug
chore
feature
spike
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Blocks
#21 Biometric lock (configurable scope)
utilities/Logbook
Reference
utilities/Logbook#10
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Decision — what is the default biometric-lock scope out of the box?
Biometric lock is user-configurable (§10). Each family member supplies their own Outline API key stored in Android Keystore; the lock gates access on top of that. The scope options are settled — the open question is only the default before the user changes anything.
Configurable scopes (§10)
Candidate defaults
What to decide
Which of the three is the shipped default.
Blocks: the biometric-lock implementation and the first-run/settings UX.
Recommendation: Stream-only by default. The Stream aggregates everyone's entries and is the surface most worth protecting from a casual glance, while leaving Log/template entry unlocked keeps the app's core "low-friction capture" promise intact. Users who want more can switch to whole-app; users who want less can turn it off.
Source: Solution Design — Family App v1 §10 (doc vpBNbG4TsV).
3 stream only by default.