40 lines
1.3 KiB
Markdown
40 lines
1.3 KiB
Markdown
# Product brief
|
|
|
|
## Purpose
|
|
|
|
UBGitea gives employees a focused Android experience for the company Gitea instance without attempting to reproduce every web feature.
|
|
|
|
## MVP outcomes
|
|
|
|
1. Sign in through Gitea OAuth 2.0 with PKCE.
|
|
2. View the signed-in user and organizations.
|
|
3. Browse accessible repositories, branches, directories, and files.
|
|
4. View issues, pull requests, and notifications.
|
|
5. Sign out and remove locally stored credentials.
|
|
|
|
The first release is read-oriented. Creating, merging, deleting, or administering resources is out of scope until explicitly approved.
|
|
|
|
## UX principles
|
|
|
|
- Korean-first copy with a structure that permits localization.
|
|
- Clear loading, empty, offline, authentication-expired, and server-error states.
|
|
- Never obscure which Gitea instance and account are active.
|
|
- Require confirmation before any future destructive or irreversible operation.
|
|
|
|
## Non-goals for MVP
|
|
|
|
- Editing source files
|
|
- Git clone/push over SSH
|
|
- Repository or account administration
|
|
- Gitea Actions runner administration
|
|
- Package publishing
|
|
- Multiple Gitea instances
|
|
|
|
## Open product decisions
|
|
|
|
- Final Android application ID
|
|
- Minimum supported Android version
|
|
- Visual identity, icon, and color palette
|
|
- Whether biometric reauthentication is required
|
|
- Whether repositories must be cached for offline browsing
|