Improved SpacetimeAuth Web UX

Improved SpacetimeAuth Web UX

Summary

I’d like to request improvements to the SpacetimeAuth web login experience, especially for apps using third-party providers like Google and Discord.

Issues

1. Extra authorization step

The current identity-provider flow appears to require these steps:

1. Click login button on app
2. Click “Login with Google/Discord/etc.”
3. Click authorize with the provider
4. Click “Authorize Application”

That fourth step is confusing for new users because they feel they already authorized the login provider. Ideally, third-party auth would only require selecting the provider and approving the provider login.

If the extra step is required for technical reasons, the page should more clearly explain what is being authorized and why.

2. Login screen polish

Play testers said the SpacetimeAuth login page looked somewhat “sketchy,” especially when only Google and Discord providers are available and email login is not enabled.

A few CSS/layout improvements would help it feel more trustworthy and consistent with the polish of the main SpacetimeDB website.

3. Embedded login option

It would be super helpful to support embedding the provider selection directly inside an app, similar to Firebase Auth, instead of requiring a redirect away from the page.

4. Role management

Role management would still be useful, but it is lower priority for me because I already implemented a custom solution.

Impact

These changes would reduce login friction and improve trust for users trying apps built on SpacetimeDB, and prevent losing new players in the onboarding process.

Requested by @doodlechaos via the SpacetimeDB site.

Start by reviewing the current SpacetimeAuth web login flow, including the Google and Discord provider authorization steps and the login page layout. Define a narrower scope and acceptance criteria before implementation; the issue currently combines authorization UX, visual polish, embedded login, and role management without naming files or tests.