Web Design
@simonv3 made a draft thing, here's a screenshot:
There's more of them though, arranged in this PDF
Previous thread
I've taken some first steps to define a create account page using a google drawing:
https://docs.google.com/drawings/d/1JvYXwciNlVxdIB3mItjHUAngOucdCoArhJy5YLDwKX8/edit?usp=sharing
I wasn't sure on whether we need people's e-mail addresses or not when having them sign in without oAuth. Might be good to have a list of things we would like to know about users after sign up?
I've also read some things implying that social log in buttons aren't worth the work for sign up (but it's quite possible that people have gotten much more used to seeing them since 2012) - though I think they'll be important for people's profiles, so might as well include them? Depends on how much work developers see this being, and whether it's considered part of the minimum meaningful service.
I'll probably add a couple of concepts as time goes on.
Definitely change things around to what makes sense. Critique, comment, etc. How do people feel about the wireframes being in a google drawing? It's not super powerful, but it works and is easily share-able.
I also just want to say that I really see myself as a helper here - I'm definitely not as informed as you all, just hoping to be useful.
Sorry I took so long to respond to this. @simonv3, this is absolutely fantastic! I am loving the work you are doing recently. <3
As for authentication: I am definitely not the person to ask about that. I have next to no experience with it. However, we'll want to take into account the issues encountered with people leaving Gittip, and ensure those are addressed in some manner from the start. We need to explicitly avoid the lock-in issues Gittip has, which means a way to broadcast messages to anybody who is giving to you, and we'll probably want to explicitly ask for their email address as part of the initial profile setup flow after signing up.
Also: re wireframes, I vote for 2A, not 2B. The sign up form should be the very minimum required for them to have an account (in our case: username and password), with the rest filled in as the initial profile setup (which would come immediately after signup).
@duckinator What about the content of 2A in the format of 2B? (Next to each other versus above each other. I think 2A is a bit better known, and I'm sure that more well funded companies have done testing on which one is easier and recognizable for people.
I'll have a look at how sign up could lead to more account information.
@simonv3 honestly, the format of 2B bothers me a lot. It feels very cluttered, and you can't fit the most useful parts of 2A (the tiny sections below each field) in the layout used in 2B without it becoming even more cluttered.
2A with the content of 2B would make more sense than the other way around -- what I said above is merely a rule of thumb intended to avoid those hellish sign-up forms that have multiple dozens of form inputs, of which 4 or less are generally ever actually necessary for the sign-up process to begin.
@duckinator - Totally agreed. I'll finalize that a bit more, and then think about next steps.
[...]
Okay, I've taken a look at what could be a next step for the Account creation flow, and wanted to post the progress I made.
Here's the PDF. I've been working in Sketch, cause it's just a lot faster than Google Drawing.
https://docs.google.com/file/d/0B-bWl-XSXODnT1VXQ1h0dXJ4YVU/edit
In the folder I've also uploaded the Sketch file so anyone can tweak that if they want.
There's two versions in this one, Version 1 focuses more on a step by step approach, letting the user decide what they want to do on the site, while Version 2 erases that separation a little bit by giving users a direct call to action.
As always, any feedback is welcome. Let me know what you think.