Tag Info

New answers tagged

1

I think you should allow your breadcrumbs to show only the hierarchical view of your site , not how you reached there, which is summarized in the browser's history (at least if you made your site bookmarkable). As usability consultant Jakob Nielsen says here: Offering users a Hansel-and-Gretel-style history trail is basically useless, because it simply ...


0

download bmml source – Wireframes created with Balsamiq Mockups I think you're looking at this the wrong way; It's less about the overall time consumption (because the difference, if done correctly, will be almost not so different). As mentioned by other people, having the social login will allow people to have less accounts to deal with (to ...


0

In case you want the user to sign-up to your service/ feed and fill in details about him/ her self, then using the term sign-up can be used. Rather than using 'sign-in' or 'sign up', many apps 'use continue with' as seen here ux archive The link should give you some inspiration on what works as it contains some of the most widely used apps along with ...


0

I think a simple 'Sign In' gives you many more advantages. When its time for adding a mobile app, authenticating users through Google+ sign-in is easy. For users, its easier to remember that they just 'signed-in' for this app, so there is no confusion about remembering additional usernames etc. Major social sites are advocating a 'sign-in' as well, for ...


2

There are many reasons why you need to signup users. Perhaps one of the most important ones is to collect their data (name, email, etc). You can monetize these data later sending email offers, showing targeted content, enhancing their user experience etc. If you use a social login (Facebook, Google+) you have multiple additional benefits, for instance: ...


3

However it might be done, logging in and signing up are two different things. The sign up path is almost certainly more complex than the login path, regardless of whether social login or a more traditional login are used. These crucial differences are not negated just because the technology allows the process to be done in one click. For example, you may ...


0

Registration is only necessary if there is functionality or data associated with a logged in segment of users. For example, if you want to keep track of and persist a user's preferences or interaction on the site for the purpose of informing them later. You can track both of these for yourself without the need for a particular user registering. 3rd party ...


0

I think it's because there are two different data sources. Your Google information does not automatically show up on SO database, you have to be placed in there. By signing up, you create the instance of the user, and by doing it through Google, you are just moving your data to SO's. Then you sign in through Google, using the connection you established when ...


1

Let's tackle this from two sides: 1: On the perspective of Design: It provides options to the registering user. By having social plugins used for form completion and account registration, the user can expedite the process and the site can drive more turnovers/accounts by doing so. Its an easy solution to a common problem: Driving Usability. 2: On the ...



Top 50 recent answers are included