Skip to main content
Question

Do you guys implement Form Inputs in Prototypes?


bazoo

Let’s say that we are doing Design Sprint and our objective is to create a new onboarding experience for the user.

How do you implement form inputs when you are testing the prototypes with the users?

Or do you leave the inputs out completely?

Shane
  • May 13, 2021

I usually just implement an “empty” and a “filled” version of the field, with the filled content being what I want for the narrative of the test, and then clicking on the field “fills” it. I’m never testing “can they fill out a text field”, I’m testing the wider flow or whatever, so that works for me 🤷


bazoo
  • May 15, 2021

Yeah, what you say makes total sense. I may have been thinking this too hard!


Andri
  • September 8, 2022

+1

This is a must if Figma wants to be a proper prototyping tool. For web apps form inputs are like half of all interactions. Not being able to create form fields with user input is a huge drawback and limits the usefulness of Figma prototypes big time.


Andri
  • September 8, 2022

My view now is that faking forms interactions for use in something like a usability study/user testing is not going to give you any feedback or insights. So skipping them is what I will be doing. It might be ok to fake one form field if it’s not the main thing being tested. But overall its not going to be useful.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings