0

Im designing a x3 step process for the web

Should i have it on one long page 1. 2. 3.

Or move users to the next ] page 1. (Next:Do 2) 2. (Next: Do 3) 3 (Finish)

  • 2
    What is the purpose of the process? Who are the users? How long is each step? What are the steps? – Matt Obee Oct 2 '14 at 12:40
  • 3
    We're going to need a lot more detail here. If the 3 steps are 'Name', 'Email' and 'Phonenumber' then that's clearly better as one page. But if the steps are 'Complete medical history', 'Financial transactions of the last 5 years' and 'Family tree of the past 4 generations' then splitting it over several pages is better. – JonW Oct 2 '14 at 12:47
1

If there's indeed enough content to fill one long page with it, then splitting it into several shorter pages might be beneficial. Users won't feel overwhelmed by the amount of content (or by the amount of data that is asked of them, in case this is a big form) and they'll have a better sense of progress.

In that case just make sure to provide some kind of a progress indicator, so that users have an approximate idea of how long of a process are they committing to.

Some examples:

Also, a good read on the subject: http://ui-patterns.com/patterns/StepsLeft

|improve this answer|||||
  • 1
    I don't think it is worth answering questions that are this poor. There is no way to give a good answer based on the information given. – user31143 Oct 2 '14 at 15:28
  • Agreed, will refrain from doing so in the future ;) – Davor Oct 2 '14 at 15:54
0

I agree on most suggestions for a progress wizard (there is a related post here).

I do not completly agree, that the amount of content is critical if it should be splitted in serveral pages. Think of pinterest for example. They have an endless page to scroll. For sure there are some withdrawals with the automatic appending of new content (perceived size/position of the site).

But users are used to scrolling and the effort is very low (flick with the finger, scrollwheel). Especially when the user wants to have a "look back". Switching to a different page/slide, needs more effort/load time.

So to break it down for you question: If you have separate steps, which probably need some explaination, paging would do a good job. If you have a lot of content, maybe connected together, consider if putting them on a page, with dynamic feedback of progress in the steps would fit in (think of a timeline/stream).

Hope this helps to find the right question ;)

|improve this answer|||||

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.