Does usability suffer if you don’t follow the iOS Human Interface Guidelines?

Does usability suffer if you don't follow the iOS Human Interface Guidelines?

When you don’t use the iOS Human Interface Guidelines, usability will only suffer if your deviation doesn’t work well.

Following established patterns is always a good idea, but if your product would benefit from deviating from the established patterns then it’s worth doing. When you deviate it is not always going to result in a poor user experience, but the chances are higher, so you’ve got to test your new way of doing things on your actual audience to see if they find it to be a problem.

See Questions On Quora

Electronic Health and Medical Records: Which healthcare software has the best (or even good) user-experience?

Electronic Health and Medical Records: Which healthcare software has the best (or even good) user-experience?

None. Repeat: NONE.

There is not a single major healthcare software company that genuinely cares about its end user experience, despite the fact that poor implementations have, amongst other things, been associated with increased patient death. The particular publication I’m thinking of is actually more reminiscent of a frustrated rant than a calm scientific explication[1].

Reasons why no one cares:

  1. No one at the company really understands how to abstract healthcare workflows. The engineers are absorbed in the coding of functionality, the product managers have no idea how their stuff is being used to treat patients, the docs are too busy trying to use this crappy software to treat patients that they tend not to be available to give adequate feedback, and designers who are good are quickly snapped up by Silicon Valley companies who understand how ridiculously valuable they are.
  2. There’s a huge barrier to moving away from a piece of healthcare software once it’s been bought and installed, because they’re all pricey and everyone has to learn a new set of workflows. Patient care almost invariably suffers during this adjustment phase, and the last thing anyone fighting in the trenches wants is to screw up a patient’s life.
  3. Many morons in healthcare administration still have not figured out that “extreme customization available to fit your practice’s needs” is advertising BS for “we were too lazy to figure out this really important part of our software, but we don’t want to admit it, so we’re going to spin it like it’s a good thing and lay all the blame at your feet when the random crap you pick inevitably fails in some major way”.
  4. The backend implementation for many large EMRs would have to change fairly drastically (read: be completely redone from scratch) to modernize it into something that coder-designers of recent generations would even want to touch. To give you some idea, EPIC, the largest EMR vendor, uses Cache[2]. This framework is based on MUMPS, which came out in the 1960s before humankind even knew what good programming methodologies were. Example for you programming types: there is no variable scoping in Cache. Let that sink in for a minute. Yes. All variables are globals. It is an unholy nightmare.

[1] http://www.pediatricsdigest.mobi…
[2] http://en.wikipedia.org/wiki/Int…

See Questions On Quora