This scenario is happening in our company. More than 15 business-oriented, data-driven applications are getting built, that commonly show charts, lists (with filtering and paging), entry forms, and they're all about CRUD. They are very routing applications, yet highly customized for organizational customers, and also public people. For the sake of productivity, the company decides that:
- Admin panel of all projects should become similar
- User panel of all projects should become similar
- Admin panels are better to look like user panels
- Only one breaking point is considered for responsiveness of web UIs
- Apps (Android & iOS & Windows Phone, etc.) should look like responsive web UI
- Android and iOS should look alike, and they should resemble web panels
- Graphic design should be the same across all UIs we have
These shoulds and musts are ensured through a very smart infrastructure of reusablity and policies. That is, if it's decided that all entry forms should have their actions be present both on the top and on the bottom of the form, it's applied throughout the entire 15 applications. Or if it's decided that navigation menus should change, it's done everywhere. The number of these applications might also increase over time.
Now this means that in iOS, we should have a navigation drawer, which is not something native to iOS's UX, and also we should have paging in all of our apps, which is somehow not intuitive on applications, but is a good UX decision for web portals.
The company argues that productivity matters here, and through this decision we can lower production cost, at the price of lowering UX, but it's acceptable in the market, because the lower production cost, means lower payment from end users which in itself is a very favorable and desired UX.
How much can we really compromise UX for the sake of economics and productivity? Is it acceptable at all?