There's a huge difference between consumer vs. B2B apps: in enterprise software, the person using the software is often not the person who's paying for the license. They are both stakeholders, but with very different requirements.
Managers usually want this software to be implemented company wide, because everyone using their own tool would turn into a big mess. They just want their business process covered by the software and have some reporting workflows to send status updates up the chain. That's what matters to them: staying in control of their teams so they can meet their commitments.
This means the actual end user has no choice which software is used at their company. The supported business processes are often complex, which leads to the software/UI itself being complex. As a result, end users need training or even certification to work with the software. How insane would it be if your average smartphone app would require days of training before you can use it? The lack of feedback loops doesn't help either. You're lucky if there is a (functional) feedback mechanism or community forum for the software.
That said, I think smartphone apps did raise the bar for UI/UX quality a bit. People are now used to simple touch interfaces and expect the same quality/ease of use from the software that they work with.
From a developer side of things... it really depends if the management cares about building a maintainable product or are just shipping to meet deadlines. No matter how much developers raise issues about unresolved technical debt and how it turns the software into a monolithic ball of mud, the house always wins.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
There's a huge difference between consumer vs. B2B apps: in enterprise software, the person using the software is often not the person who's paying for the license. They are both stakeholders, but with very different requirements.
Managers usually want this software to be implemented company wide, because everyone using their own tool would turn into a big mess. They just want their business process covered by the software and have some reporting workflows to send status updates up the chain. That's what matters to them: staying in control of their teams so they can meet their commitments.
This means the actual end user has no choice which software is used at their company. The supported business processes are often complex, which leads to the software/UI itself being complex. As a result, end users need training or even certification to work with the software. How insane would it be if your average smartphone app would require days of training before you can use it? The lack of feedback loops doesn't help either. You're lucky if there is a (functional) feedback mechanism or community forum for the software.
That said, I think smartphone apps did raise the bar for UI/UX quality a bit. People are now used to simple touch interfaces and expect the same quality/ease of use from the software that they work with.
From a developer side of things... it really depends if the management cares about building a maintainable product or are just shipping to meet deadlines. No matter how much developers raise issues about unresolved technical debt and how it turns the software into a monolithic ball of mud, the house always wins.