No. While it seems to be annoying, I see four problems with not having to enter the login information again:
I will remember my new password better if I have to type it once more. (I keep forgetting my new e-banking password because I don't have to re-enter it, and I of course don't store it in the browser.)
If I want to store the password, the browser PW ...
In my opinion: YES.
The authentication has been done when the password is reset, so the user could be logged in. And it annoys the hell out of me when after password reset I'm not logged in.
I can't think of any case I wouldn't want to be logged in after resetting password, why would I even ask for password reset if I don't want to log in?
You should have the buttons at the bottom right because:
The standard for modals is to have the buttons at the bottom, so it is likely where people will look for action buttons
It is a more natural visual flow reading in a Z pattern, and one that has become entrenched.
A button on the right is typical for a submit button as it has the feeling of moving ...
There isn't really a standard or convention that define these terms, but there's some sense in how these often differ.
First, the term flow denotes a non-linear path, i.e. one that branches.
Then, flow in UX denotes through the system. Meaning that the analysis makes use of the system templates (either existing or those of the design).
A task ...
In your experiences, what has worked well, and what would you make
sure you never done again?
Be a designer who develops AND a developer who designs.
White board concepts and solutions with developers as you either
flesh out features or solve technical solutions. Be willing to bend and
compromise and stand up for your ideas. Expect the ...
As msparer suggested, Stating the main action first and then offering context/side effects is a very good step to take.
The other thing I'd definitely do is to label your buttons descriptively.
It could look something like this:
Are you sure you want to close all transactions on terminal x?
Closing will also print the transactions of 11/20/2014.
Try shopping anything on amazon without logging in first.
Browse -> pickout the item -> add to card -> proceed to check-out -> log-in -> continue with address selection and payment.
Amazon can easily be the top player who needs to worry about user flow and logging in :) So, YES, login should just be a step outside the flow and back in i.e.
Some names could be...
Progress Bar (although it can be confusing in certain contexts, in my opinion)
Step Progress Bar
Segmented Progress Bar
Step by Step Progress Bar
Navigation vs. Indication
If the steps are clickable links I ...
Custom HTTP error pages improve web sites' experience, security
Every web server can display HTTP error pages, but default error pages don't provide useful information to your visitors. Some error pages may even leak sensitive information about your site, such as URL or file paths, database details, and even code. But you can replace the ...
I agree with Igor-G that one conversion type (getting a new signup) is more valuable than the other (an existing user logging back in), but I think the primary reason is slightly more complex, and would still make sense even if the two we're of equal value to the company.
It's a function of how much each user-type's conversion likelihood can be influenced ...
When deciding between a modal and inline entry, consider what is communicated to the user by your choice:
Inline Blank Entry
"You're going to be doing this a lot, so we don't want it to be a big deal."
"Don't worry too much, this is easy to fix if you make a mistake."
"We expect you to enter multiple items."
"Please focus. This is too ...
Rather than trying to display this audit trail in a single, very large and complicated diagram, consider presenting it as a log with a simple diagram for each change.
In my wireframe below, I am showing the history of a single task. For each record, I am showing a brief description of who did what and then illustrating the flow between steps with a basic ...
You can group all tasks that have to run simultaneously. Something like this:
When "Add task" under "When complete..." is clicked a new task is created in a new
group and the button changes to "Add simultaneous task" like the group above.
For the vast majority of situations users should be logged in once they have reset their password. Essentially, once you've authenticated someone enough for them to change a password, you've also authenticated them enough for them to perform the task that they likely wanted to perform.
There are however some relatively rare situations where this isn't ...
Some points for good labeling are:
Short – 'submitted' vs 'uploaded_for_processing'
Distinguishable from each other – bad: 'uploading' and
'uploaded', good: 'uploading' and 'submitted'
Same styling rules – try not to mix verbs and nouns and use same case
Understandable – user should know business process to match labels in UI to business phases
For taking ...
A problem I see there is that the initial action has an implied consequence that might confuse your users. According to your mockup, the transaction day gets closed as soon as the data gets printed.
It seems like "Printing" is the main action and closing the transaction day is the side-effect. It really should be the other way round.
Name the CTA "Close ...
Allow 2 views: Sequential view for displaying orders by sequential steps, and a production floor view to show bottlenecks and throughput.
Since you can't have a strict order across all steps, have two ways to view the world: at the order level, and the production floor. They serve two different purposes.
In either view, you can indicate on the left how many ...
Workflow is a set of steps to reach the goal. It's a general term (Workflow).
In UX field you can see both terms Task flow and User flow are used mostly interchangeable.
For me Task Flow is a good name for the results of Task Analysis technique. At the same time the results of the User Analysis techniques (in narrow sense) are User Models, Persons, but not ...
Why is it wrong?
OpenID has several drawbacks:
You're actually going to a totally different website in order to register or authenticate. This is not how things work ordinary. For years, registration and authentication for a website was done on the same website: the user was moved to a different website either because he wanted to, or because he was ...
I started out doing front-end development, and shifted into specializing in UX so I spent a lot of time doing the Photoshop/Illustrator to Browser routine.
When I joined the team I'm on now, I had to adapt to an Agile environment and have managed to find a balance that works well. Mind you, on the small team I work on I'm one of those 'unicorn' types that ...
The social accounts anyways confirms if the user wants to log in to the service with the current account or not, so I see no issue or security concern with not linking the social accounts if the email address is same as the one the user signed up with.
It is always a great practise to link the account if the emails match and that is what the user mostly ...
I've heard and had this talk too. In my view, people walk away from wireframing and designing in Photoshop or any other tool because with RWD we no longer design for a fixed width. Some people also walk away because they think creating mockups and then designing and then developing seems cumbersome. So then what you do? The answer I hear the most is 'in ...
Breadcrumbs are good for storing information. It will make easier to remember the path of the information, not only navigate around them.
It enables you to cluster the information.If you have not much information, you do not need breadcrumbs but you ll need it when you are dealing with complexity. Breadcrumbs tells a lot about how the information ...
I always go by the rule Chapter is to Tab. Paragraph is to Collapsible Panel.
When you have 2 hierarchies, the broader of the two levels are tabs and the other ought to be for collapsible panels.
For complex applications, there are more than 3 levels. Whatever you do, don't implement the same UI division to the next immediate generation. This means that if ...
I think the main goal you're trying to achieve is to streamline the content creation process.
A possible solution is to split the content creation process to two mini-steps:
First just offering a text box to spill out thoughts, encouraging users to invest in writing (because the required investment is low)
Second, after the user commits (saving the card) ...
Because you want to keep it as simple as possible
Great question! I've had a chance to actually test it with one of my projects. We had a single form which required email and password, and we wanted to make it as easy for our users as possible to sign up. So if you wanted to sign in you just entered your email and password and you were in. On the other hand ...
"Avoid Blank Slates"
Alan Cooper says you should avoid blank slates:
Timid applications are reluctant to carry out any forward motion without someone directing them in advance. But most people would rather see the application take a "good enough" first step and then manually tweak it to what is desired. This way, the application moves the person closer ...
The time when user requests for the email change, send them the confirmation link and till the time the new email ID gets confirmed, treat the earlier email address as the primary email.
Just make sure that you are mentioning this to the user along with the status of the email addresses.
Keep both email address by disabling the earlier email ID after the ...
I feel like you're going about this the wrong way, you should ask the creator of the button, prior to any implementation, the questions if it fundamentally relies on them being in the right country and having registered for Stripe, something like this:
This prevents them from placing a button that potentially would not work, on their site in the first place....