0
I already understand that the best practice is to use one field per line, unless it has a direct relationship, such as: Address and number. Reference.
However work in a system that in many fields, they may be mandatory or not depending on the company that uses it, this will be customizable.
An internal resistance is usually to complain of using this model, the form gets very long, needing to scroll, and putting several fields one side of the other, impairs the reading and looks like old system, and some apps that use here internally have this face, IE, for the company are good interfaces example, which I do not agree.
In a query screen, this would also be bad, because the query screen, usually is the same registration screen, with the input filled, so the user can edit information (For this case I’m thinking of changing the appearance of the query screen to something less expensive form.
I’m researching about but I haven’t found anything. Someone has references of systems that use many fields, but that can use these good practices?
PS: I have also thought about step-to-step screens, but there is also this resistance.
"Best practices" stop being "better" when it doesn’t solve your problem - and you’re never required to follow them. A stranger on the internet says he needs to do X, but his user wants Y. Who will you answer? For me it is somewhat obvious that it would be Y. In fact, if there is so much resistance, I did not understand what the purpose of the question was. Your users seem to have a very well defined taste, but expect other strangers to say otherwise?
– Woss
resistance is not from users, but from the development team. I just contextualized the situation so I could ask for references and I want them.
– Alex Machado
I disagree with almost everything written in the reference, even if I agree by default, I disagree because it depends on the scenario. Generally the scroll is terrible, and even though the other things are problematic, and I’m not saying it is, they’re small near the scroll or use of tabs. But it depends on each case. The reference is only the opinion of the person without any concrete basis. I do not know nor if it serves the person who wrote. If the customer understands that something is good, probably (not always, but usually is). This is usability, not what the programmer thinks. The programmer follows the client or...
– Maniero
...proof that the way it is better, even if it is doing the 2 ways and putting for the customer to test (maybe doing an A/B). Almost all systems are bad at UX, people don’t care about it and do as they please.
– Maniero
There are many forms with multiple columns of fields that are extremely common. See a example | example. Just know how to work with the user’s need and data to be displayed. "Best practices" should never give development rule.
– Woss
@Andersoncarloswoss did not find these examples very good :) Especially the second. There are many questions that make the form be + friendly, being all in one column earn very little and usually lose a lot, but if not associate well the fields in the lines coherently gets worse, then it is complicated, it is not a decision between x and y, is about all possible Excel columns :)
– Maniero
The example Anderson gave is good, it keeps keeping the form in a single column, like side blocks. When I referred to multiple columns, I referred to another situation, where the fields are side by side, like this form from here to worse
– Alex Machado
the question of the single column is to make it easier to read, in the example, you go through column A, and then column B. I still don’t see how the best way, but it’s already much better than punching several inputs on one side of the other.
– Alex Machado