Hot answers tagged

2

Imagine you have all your question intupts in one form. Do they have any complex relations like mutual enable/disable logics or different ways to go depending on particular answer? If so, your current approach helps to hide form's complexity. Also, if you have device of limited screen size your approach avoid difficulties with scrolling and validation errors ...


2

I don't have any studies but the following thoughts: Dividing questions in multiple screens is not done to increase the felt speed to fill in information. It is done not to overwhelm the user with too much information. Every viewport should host only one question / step. This makes it clear to the user that she has not to scroll down in order to answer ...


2

I haven't found specific research about perceived speed for single-question, but it would be highly contextual and hard to generalize. The simplest way to decide this for your domain would be to create a prototype with both designs and test it on users. In the meantime I would recommend taking a look at Luke Wroblewski's insightful article about onboarding ...


1

The main issue with custom fonts is when pages load slowly because new fonts have to be downloaded. You can check whether fonts have already been downloaded or are otherwise available. If not, you can check the link quality to decide whether you want to download the font. If not, fallback on "sans-serif", or whatever else is already available. The "axioms" ...


1

depends strongly who your user is. We work to GDS guidelines and that is strongly one thing per page because we want users to avoid errors. One thing per page focuses on just one thing for the user, one bit of content to read, one decision to make. If you're designing for expert users who want to do the same thing over and over again, quickly, this ...


Only top voted, non community-wiki answers of a minimum length are eligible