Learn how to avoid common mistakes when designing forms.

18 cards with practical examples 👇
Try to avoid multi column layouts.

It's easier for your eyes to go through the form if it's a one-column layout.
This layout is also acceptable.

But the labels should be placed next to inputs to avoid Z-pattern.
You can put related inputs in the same row.

It not multiple-columns. It's like having one input that we break into separate.

So it's not bad, on the contrary, it's considered a good practice.
If you have a large form, make input sections.

Also, check out a very nice pattern from @steveschoger

There is no rule that you should always take all the available space on the screen.

Use reasonable width for inputs. This will help users understand what kind of data you ask from them.
Developers tend to hide hints under question marks.

Sometimes it's alright. But if possible, show the hints right away.

Don't ask users to make additional clicks/hovers to see what you've hidden under the icons.
Password inputs often have a lot of rules.

Show them right away and tell users how well they do.

A nice example of this is @Mailchimp sign up form login.mailchimp.com/signup/
Don't use placeholders as labels 🙅‍♂️

As soon as users start typing they disappear. And users should remember what the field is.

Plus after they've completed the form, they cannot check if they've filled it correctly.

Minimize cognitive load!

nngroup.com/articles/minim…
Show validation errors near the inputs they belong to.

Don't put it somewhere at the bottom, or at the top.

Otherwise, users will have to match an error with its corresponding input.

Also, check out WHEN to show validation errors in this tweet:
If you have a dropdown with up to 5-7 options, it'd be better to show them right away.

Pros:

🔸Reduce the number of clicks
🔸Users will see all available options right away
Don't use default file inputs.

They're ugly 🤮
Make your labels clear and succinct. Avoid unnecessary redundancy.
Validation is cool, but you can help users avoid making mistakes.

Related thread:
Consider positive feedback as well as negative. Especially for complex forms.
If you have a show/hid password icon, use a separate space for it.

Otherwise, it might interfere with password managers.
Don't ask users to repeat their passwords.

🔸Provide show/hide password button
🔸If they made a mistake, you should have the reset password by email feature
It's a good practice if you explain to users why do you ask them all that information.

This will increase the chance they'll provide the info.
If your form is complex, don't be afraid to make a wizard out of it.

It'd better have the form divided into separate pages, rather than showing all the inputs at once.

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Victor

Victor Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @vponamariov

25 May
Want to make your UI flawless?

Here are some ideas for you 👇
Consistency

🔸Make a color palette in advance, or use a ready one

🔸Ideally, make a UI kit of every element you need

🔸Make sure your icons have the same styling

🔸Don't use too many layouts

🔸Make sure UI elements behave the same way across your app
Typography

🔸The text should have good contrast (AA+ WCAG)

🔸Don't use more than 2 fonts

🔸Provide text hierarchy (headings/sub-heading/paragraphs)

🔸Use proper line-height

🔸font-size should be at least 16px

🔸Do not justify text
Read 7 tweets
24 May
A curated list of 68 free resources for designers 🤩

👇
Read 14 tweets
24 May
Do you know how to make a dotted background with CSS?

Once I found the code but didn't understand the magic.

Here is a detailed explanation 👇
As a container, I'll use the body tag.

To make a dotted background we will use a combination of linear gradients.

Let's make something illustrated below.

The red background takes 20px.
Then goes green which takes 1-100%, in other words - the rest space.
Now, if we set background-size we can repeat the pattern which will look like on the image below.

The first value doesn't matter in this case since it's repeated horizontally.

But the second value is important - it's the space between the lines.
Read 6 tweets
24 May
Today I turned 32.

Sharing with you some life lessons that I learned by this time.

I do not claim I necessary follow them.

It's not a planned thread. Just some sincere thoughts about life.

In no particular order. 👇
Your personal experience is more important than any advice.

This thing I've read in "The happiness trap". It is a book dedicated to the ACT therapy method.

Any advice is good. But nothing can replace your own experience.
People affected by survivorship bias too much

We see cool photos of people who drink smoothies on the beach and code startups.

The bias is that those who suffer depression, burnouts, anxiety, who has debts, and so on - they don't tell you that.

indiehackers.com/post/holy-heck…
Read 17 tweets
18 May
I found HUGE analytics of the current state of mobile UX by @Baymard

18 Common Pitfalls 👇
1. 95% of Mobile Sites Place Ads in Primary Areas of the Mobile Homepage

2. 57% of Mobile Sites Fail to Provide the Full Scope in the Link Text of Suggested Paths

3. 69% of Mobile Sites Dont Offer Relevant Autocomplete Suggestions for Closely Misspelled Search Terms and Queries
4. 79% of Mobile Sites Don’t Include the Search Scope in the Autocomplete Suggestions

5. 40% of Mobile Sites Don’t Visually Distinguish Autocomplete Product Suggestions from Query Suggestions

6. 42% of Mobile Sites Don’t Persist Users’ Search Queries on the Results Page
Read 8 tweets
17 May
How popular sites evolved for the past ~20 years ✨

👇
Google.

1998 -> 2005 -> 2015 -> 2021
Facebook.

2004 -> 2008 -> 2016 -> 2021
Read 6 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!

:(