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.
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.
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.
- Those apps are simple
- Those apps target a wide audience, hence have more budget as a result
- Those apps are made by large, well oiled (you'd hope at least) companies. You don't want my honest opinion on most small software development boxes. This industry grew faster than mentors became available for the newbies, so many devs including seniors still don't know what they are doing.
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.
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.
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.
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
I worked for a big Euro bank for a bit and that was exactly it. JS timeouts were forbidden, so no animation to tell you something was finished, you had to keep clicking a Refresh button to know. In 2022.
And the colleagues who had been there a few years were actually defending this shit. Stockholm Syndrome is what it is. There wasn't a day I didn't complain about their piece of garbage of an intranet.
I'm so glad it's behind me.But our power users!!
Gave me flashbacks to my time working with Philips' Tasy system in 2017.
By now they've surely finished implementing their HTML5 system which was somewhat better, but back then it was still a desktop app made using Delphi and Java, and it was basically as unsightly and unwieldy as the example in the meme lol
Needs more CLI.
The company app is for actual work, the others are for instagram and netflix
I’m sure if this weren’t black and white it’d be some green on black z/OS goodness.
This, but trying to slap all of that into a ‚new‘ react app while not hardcoding every damn input.
Not too far off from my company. However, I work in Healthcare so we've got to do a lot of verification. Also, it's more what we support for our customers rather than what users/patients should see. At least I hope.
This is giving me CICS interface flashbacks. Anyone who worked retail or call centre or adjacent 20+ years ago probably remembers getting really good at using these kind of bespoke CMS front-ends (Bell folks might "fondly" remember ARICS and BCRIS).
Looks like Syteline to me lol.
SOVL.
