1

I'm working on an authentication flow for a product we're creating. When someone signs up for our service there are a few steps someone has to take;

  1. Go to our website
  2. Click 'sign up'
  3. Complete sign up form

After that the user goes straight to the product. There are three pages, one per step. The website (1), the sign up page (2) and the product (3). These three pages are part of two websites, the commercial website (1) and the product website (2 and 3). Because of this, the pages have a different look and feel. The commercial website (1) is designed to inform and for users to sign up. The sign up page (2 and 3) is very clean, focussed on the form and the product.

So the user first sees a website in one style and after that pages in another style.

Question

Is it good practice to let users take big steps in a flow, from one website to another?

I can imagine that users might feel lost or suspicious when the next step in a flow is part of another website.

Note; this question could have some overlap with the graphic design stack exchange, but my question is directed at the ux of taking steps across different styles.

  • Can buyers 'checkout as a guest' or are you forcing them to register? – DarrylGodden Jul 19 '17 at 10:21
  • Users have to register for our platform. – Nick Groeneveld Jul 19 '17 at 10:52
2

Moving users from one site design to another (especially without a new tab) can be a bad practice. Not only are you visually shocking them but you disrupt your brand message, also, analytics tracking can become confusing.

I would suggest one of the following in order of importance.

  1. Move signup to site 1, connect to site 2 DB
  2. Create a separate sign up page in site 2 with the same look and feel as site 1
  3. Explain in site 1 about site 2 and show a screenshot with directions

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.