Optional account, for people who want one

Aperta
  • Qualcosa non va?
#175 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
12/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
swift
Ambito
authentication

Direzione di ricerca

This is a design discussion, not a code task: it names no files, tests or entry points. The open questions are which sign-in method to use (GitHub device flow or email links) and where the account service runs. Read the design rules and the linked usage-reports issue #176 first. Done would mean a written decision on those questions, agreed by the maintainer, before any implementation starts.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement priority:P2 roadmap

SpeakType works with no account today, and that stays true: dictation, models, history and settings never require signing in, and the app keeps working offline forever.

An account would be opt-in, and worth having for:

  • Usage reports (#176), so people who want to help can share how the app is doing.
  • Sync between devices, once the phone keyboard exists. That's the only feature that genuinely needs an identity.
  • A way to reach people who ask to be told about releases.

Design rules, or it isn't worth building:

  • Nothing in the app is locked behind an account, now or later.
  • Signing in is a choice made once, never a prompt on launch, and never a wall on first run.
  • Signing out removes the local copy of the account, and deleting the account removes everything held for it.
  • No account, no data leaves the machine. That promise stays exactly as it is for everyone who skips this.

Open questions: which sign-in (GitHub device flow is the least friction for this audience, email links are the most familiar), and where it runs. Whatever we pick should be documented, so people can see what's stored.

Lingua principale
Swift
Stelle
540
Fork
74
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di karansinghgit/speaktype

Tutte le issue di karansinghgit/speaktype

Issue simili

Altre issue su Swift

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.