As per fligtar, while registering with browserID we should have users provide "username", "display name" and other relevant profile info instead of creating an account using their email address. This is required for the apps preview launch.

Can we just use their email as their username? What's the benefit of having a username anymore? I don't think "so we can use a slug rather than an id for their profile URL" makes it worth asking thousands (millions?) of people to come up with a username. We could also not ask them for a display name until they want to create content (whether it be an add-on or a collection). This might be a bit harder to swing from a UX perspective, though. However, I really love the concept of lazy registration (http://webjackalope.com/lazy-registration/ for examples) Same goes for any other non-essential information -- it makes BrowserID somewhat moot if they still have to fill out a "sign up" form on AMO.

Seeing a "complete your profile" step after logging into a website with BrowserID for the first time is an expected and normal behavior for almost every website integrating BrowserID. The Identity team knows this and until BrowserID decides to store more profile data, it will be the norm and certainly doesn't make it moot. I'd like to give users the option to set a display name and fill in optional profile information the first time they log in. The reason that we *have* to show something is that we need users to accept our Terms of Use now that we're dealing with money and more liability issues. I don't think it's too much of a burden for users to choose a non-unique display name at that time, but if we're willing to write and maintain a lightbox or other good flow that asks users to choose a display name the first time it's needed, I'm ok with that too. (we'll still have to figure out how to get them to accept the TOU, which can possibly be deferred to their first purchase but will need to check on that) We need a public identifier for users who: * have a public collection * write a review * log in to the forums * log in to the builder * submit an add-on or app * engage in any social features that will be coming That public identifier is more the Display Name than the username. The username is only used for slugs and the forums, 2 cases in which it needs to be unique. The other cases don't need to be unique. I'd like to get rid of username or make it an optional slug field, but in order to do that we'd need BrowserID support for phpbb, and move that login system to its own thing. Or write a phpbb extension to allow username creation there too.

Fixed: https://github.com/mozilla/zamboni/commit/200465bafba0bbf4e9185fe6a3857f5aa63c177f Works on the login screen as well as any non-login screen. I have not yet verified it works in mobile though. This works for new browser ID users. Also, if any existing user logs in who had an empty username or empty display name, she will be prompted to complete her profile.

Issues: * We do not require users to set their "username" and "displayname". User can navigate away to the homepage and the account will still be created using their browserID info. This means that - Doesn't solve the duplicate username issue.(we check only when the user tries to set their username) - Doesn't check for restrictions around usernames (we only allow alphabets, numerals, hyphens and underscores) * There are a bunch of UI issues as well which I'll file separately.

Fixed https://github.com/mozilla/zamboni/commit/9a452d7 With this change the popup overlay cannot be closed. However, a user can still reload the page to dismiss the overlay. I don't think it's feasible to prevent that from happening since we'd have to check for incomplete profile state on every page request. Keep in mind that *every* time a user logs in with an incomplete profile, he will be prompted to complete it. So if he dismisses the overlay today, he will be prompted again tomorrow. I think this should address the issues. If not, please re-open or we can discuss some alternatives.

Fligtar, you still haven't addressed why it makes sense to pester the millions of people who will sign into AMO for information that only will be relevant for very few people. Only a small percentage will ever submit content (review, add-on, app, etc), and almost nobody will ever use the forum. I hate to make a big deal out of this, but I believe it's important. Yes, it won't be easy to do this properly. However, I'd be happy to take this bug if nobody else wants to do it. I just hate the idea of asking all those people to fill out information that we don't actually need. We should be doing literally everything we can to cut out any sort of friction. Every little extra thing will cause us to lose people. Some poor person just wants to install Angry Birds on their Firefox, and they're being asked to put in a display name AND a user name? I doubt most Firefox users would know the difference between the display name and user name. Additionally, they're probably already confused why they had to even log in to install an app. They just want the app. Reminds me of the story of the tap counter from Palm: "I actually got to speak to Palm when they were flying high in the '90s, and after the talk, I met one of the employees. He says, "Nice talk." And I said, "Thank you, what do you do here?" He said, "I'm a tap counter." I'm like, "You're a what?" He goes, "Well, Jeff Hawkins, the CEO, says, 'If any task on the Palm Pilot takes more than three taps of the stylus, it's too long, and it has to be redesigned.' So I'm the tap counter."" - http://www.ted.com/talks/david_pogue_says_simplicity_sells.html

Here is a related fix https://github.com/mozilla/zamboni/commit/046a97e (bug 708731) This prevents bad usernames from getting generated when users create an account through browser ID