Add a profile setup step after email-based registration

With the new email-based registration flow, a new user enters their email address, receives a verification code and enters that code. The account is then immediately created and the user is logged in. The user is never asked to choose a username or display name during this process. Instead, Fluxer automatically derives a name from the email address and assigns a tag. For example, registering with an address starting with info@... can result in a new account appearing as something like info#1689. The username and display name can be changed afterwards in the profile settings, but a completely new user has no indication that they should do this or where to find these settings. This has already caused confusion for new users on my instance who did not know how they were supposed to set up their name after registering. The same issue occurs when using an admin-issued registration URL that automatically joins a community: the community invite itself works correctly, but the user arrives in the community before having set up their identity.

Add a short profile setup step after email verification for newly created accounts, before taking the user into Fluxer. For example: Enter email → Verify code → Set up profile → Enter Fluxer At minimum, this step could ask the user to choose their display name and username. If the account was created through a registration URL that joins a community, the user could complete the profile setup first and then be taken directly into that community as they are today. This does not need to change the new email-code authentication flow or bring back password-based registration. The goal is simply to make sure a new user has an opportunity to set up a meaningful identity before they start using Fluxer. Even a simple first-login screen such as “Welcome! Let's set up your profile” would make the onboarding much clearer.

Both the username and display name can already be changed afterwards in the profile settings, so the functionality itself exists. The main problem is discoverability. A new user currently has to know that their automatically assigned name can be changed and has to find the relevant profile settings themselves. This was also discussed on web.fluxer.app in the official Fluxer Developers community. Other users there also pointed out that the current flow is confusing and could be improved, especially because a completely new user gets dropped into the app before setting up their profile.