Google and apple already know who you are, the company at the bottom doesn't
Lol, that's a fun angle. They don't need all those fields coz they just get your information the other way
Wrong, the google product is dead
And the Apple product would probable say "gloat about me to your friends"
People at my company are like "why are we wasting screen real estate with white space?" and I imagine they see the last image is an ideal UX
We're currently trying to convince our client, that 4 different levels "mandatory" fields in a form are about two too many.
The UI they sketched looks like shit, but they think it's absolutely necessary.
But there was this one customer, where it was so helpful to know he's left handed. So now this is a necessary information /s
And then the logging shows that nobody uses half the fields, but the business won't let you remove any.
For the first two you need hoops and tricks for it to do what you want, the last one has bad UX. I choose the later.
The flipside is that all of the stuff you actually use is buried five levels deep.
more checkboxes == more better
I actually kinda like that one.
Those are radio buttons, tho. But nice work with fieldsets 👍
Oh god I know 3rd party encoders like this from from my tape flipping days. They're some sort of dark sorcery you never question. Just press "will try to play or encode" and then make the appropriate sacrifice at your altar.
Honestly, I'd rather have an ugly app with everything right there than the terrible UX trend that's happening of everything being hidden behind 8-10 different menus just to make the home screen "clean"
It would be hilarious if all these apps were secretly just like vim. They all have complex hotkey setups that enable power users to get where they need to be in at most 3 key presses.
And the unititiated has to google to find where their god damn setting is actually located.
Honestly that would be great.
If your company is implementing an app that is basically a toggle switch or power button, it'll probably look like the first one. If your company is implementing an internal search engine, it'll probably look like the second one. If anybody is implementing a data entry system meant to be used by trained individuals at a workstation, its gonna look like option three. You might as well complain about a CNC mill being more complicated than a screwdriver, they're different tools.
That third screenshot, assuming good keyboard navigation, would likely be a godsend for anyone actually using it every day for regular data entry (well, okay, not without fixes--e.g. the SSN and telephone number split apart as separate text boxes is terrible).
This same mindset is what led Tesla to replace all their driver friendly indicators and controls with a giant shiny touchscreen that is an unmitigated disaster for actual usability.
There's a difference between software that's designed to be easy for people that haven't seen it before and software that's meant to be used by someone that's been trained to use it.
Yes and no. I did build several in-house enterprise applications and for this I know about this problem. And yes you're right, a lot of the complicated contexts are more complex than searching on Google.
But! Enterprise software architects have a tendency to make every feature as visible, and also making the apps as feature rich as possible. This comes with high costs.
I always try to establish a strive with exactly what google delivers.
Cage the user in his first decision, Filter or action and then show him or her the application with all the features feasible in the chosen context. It is amazing how complexity reduced most of these applications are when you just ask this first question.
There is a clear difference here: the first software, you pay to use. The last one, you get paid to use it.
100% this. I used to work at a company that sold software that mechanical engineers used all day, every day in a certain field. Our app looked like the last pic but with better alignment.
People who are competent want all the things on their screen all at once all the time. They also want keyboard shortcuts.
An automation API would also be nice please.. ^(i^ ^hope^ ^it^ ^doesn't^ ^require^ ^an^ ^additional^ ^$4000/y^ ^licence)^
The honestly prefer the bottom one than the modern 50 step wizards that take 10 seconds for each page to load, and load an ungodly amount of JS scripts.
A company I worked for was using an ancient bug tracking tool (called Pivotal) that looked like a 90s site. It was so fast and responsive. Later, we moved to something modern. It was 10 times worse, significantly slower and overly complex.
I hate when websites don't have the username and password together. When you have to put in the username click ok then have some JavaScript hide the username prompt and prompt you for your password. Makes it more painful when trying to use a password manager. Especially one that isn't built into the web browser by default.
And you are asked to add more fields and buttons, but the interface was made in a very old version of visual studio and it breaks something every time you open it up in the editor.
Ngl I prefer said company app rather than "new" stuff which runs on Electron and breaks just from looking at it
Fuuuuuuuuck Electron
"We want to look like Apple" while insisting on every bit of whitespace be filled.
But hey, ROUNDED CORNERS! SUPER ULTRA HIGH DEFINITION ICONS! That's what makes apple apps apple, right?
Is this post brought to us by a Service Now developer?
Oh no, my company is going to integrate with Service Now! Should I be scared?
Depends did they hire 2 developers in house to babysit the application after rollout?
Haha, hire developers? No, no, no. Doesn't off-the-shelf software just work? /s
I'm not really sure why both first name and city are required but I hate oversimplified mobile designs. Whenever a web page loads everything into a big rounded edge middle column I do a little angry exhale.
I'm an adult with a mouse and keyboard, I don't need giant baby buttons and you can load more than two rows of something at a time ffs.
This is not true. Literally all of apples computers lack the touch feature on their primary screens.
Good.
You need all that information, but no more. This allows me to efficiently supply it, properly formatted, and to supply no more. Assuming this is using standard widgets instead of reinvented ones, the only better thing would be an API so we can roll our own form or automate.
The FAANG approach relies on an army of people to do the data entry equivalent of mind reading, or invasiveness, or both, and all so that you have to look at a few less boxes for a minute.
At least it doesn't have ads
CEO: "Now theres an idea..."
I am getting flashbacks on dealing with SAP "inspired" software that looked worse than that bottom image. I am glad my new company does not use that garbage. It was especially depressing to see how SAP entirely ruined Concur.
Whoever made this has never used Google Cloud Platform.
Your company's app is SAP
Haha, no, cause then I'd be paid more.
Yay, options.
We have to get permission from Marketing, the CEO, the Pope, and the ghost of Queen Elizabeth 2 to change anything about the layout, so we just jamb in more buttons.
Every few months the layout gets reshuffled as well for no fucking reason.
You forgot the ads on google
Post funny things about programming here! (Or just rant about your favourite programming language.)
