Translating a 30-year-old clinical informatics desktop application to a modern SaaS SPA takes careful research and iterative design
Author: Eric Stoltz
A B2B application worked for SMBs, but as larger companies signed up it faltered.
When I crafted the personas for FastPay, the process uncovered an important unmet need
I streamlined hierarchy and cured a case of chronic modalitis
Discharge instructions are still a computer printout and photocopied pages. What if they were a mobile app?
When you have two apps targeting two ends of a process, how do you break them out of their silos and showcase a formidable AI platform?
The branding section of this software design system will help to recruit cross-disciplinary stewards.
One of the first pages this new software design system is documentation of our adaptation of the Angular Material button.
An acquired company offered an iOS app for point of care with many pain points; translating it to Android allowed me to address those UX problems
A style guide helped move development along when it spoke the developers’ language
A little HTML and CSS can go a long way in helping developers build what you need
How a whiteboard can become a hand-coded prototype in a matter of days
Even if at first you don’t think you need one, a dashboard can evolve over time from research findings, branding changes and acquisitions.
What if a process involving some 30 steps could be reduced to 1 or 2, if it meant giving up a UI?
Living for a bit in the problem space rather than jumping to a solution can yield a superior user experience.
A standard datepicker is not a solution for every use case involving a date to be input.
The user experience doesn’t end when the user leaves the screen.