Go Live gated on auth; scene building stays auth-free; update design docs
This commit is contained in:
@@ -51,9 +51,9 @@ Apply this to every UI decision:
|
||||
- Visual/drag-and-drop scene building over property panels
|
||||
- Every action produces a visible outcome — no dead ends
|
||||
|
||||
## Auth is optional, never a gate
|
||||
## Auth gates Go Live, but not exploration
|
||||
|
||||
YouTube OAuth2 sign-in must NEVER block core usage. Users can go live with a manual stream key,
|
||||
build scenes, and record without authenticating. OAuth is an enhancement — it unlocks live chat,
|
||||
broadcast creation, scheduling, and YouTube-side health — not a prerequisite. Treat the sign-in
|
||||
button as "sign in (optional)", never as a requirement to use the app.
|
||||
The app is fully usable without authentication: users can build scenes, add sources, compose
|
||||
previews, and audition the software with zero commitment. But **going live requires authentication** —
|
||||
it's the one capability gated behind YouTube sign-in. The sign-in button should never pressure the
|
||||
user ("sign in (optional)", not a modal wall), but "Go Live" only appears once connected.
|
||||
|
||||
Reference in New Issue
Block a user