Very good question - I usually develop custom, internal apps that are very data- and option-heavy. A lot of those best practices you read about everywhere are h

Very good question - I usually develop custom, internal apps that are very data- and option-heavy. A lot of those best practices you read about everywhere are hard to apply when your software is much denser than modern "do-one-thing-well"-apps. I'd like to see some showcases on how to approach those problems. One thing I found to work well, is resisting the urge collect all kinds of features in a single screen/page/view - use multiple views instead and keep them clean and simple on their own. Of course this comes at the expense of needing more clicks to reach certain areas, but I prefer that to overwhleming users by putting everything related into one section. Also, I can't emphasize enough how much consistency matters - particularly if you have a lot views, you should make sure that your users feel right at home in any of them as from their first encounter. Keep similar navigation ideas for example: If all your navigation features a hierarchy like Home -> All Items/List -> Single Item/Detail only the context will change and it will be easy to get used to that.