This is something I constantly go around in circles with:
Scenario: A clinician comes up with an awesome app idea, and tries their hand at some design work. They create some wireframes and maybe some photoshopped layouts using their component library of choice (Bootstrap/Polymer/Material/etc). They then hand off the wireframes to a staff member who is new to Meteor but enthusiastic about the problem domain. The clinician and staff member start their design with a desktop app because that’s what they’re most comfortable with, but their problem domain calls for a mobile app. The staff member isn’t a designer and creates a prototype that looks exactly like the clinician’s designs; but has all sorts of broken functionality, the data model is a disaster; and it doesn’t work on mobile at all. After months of work, the codebase has become a spaghetti mess. Help!
Sometimes I can help pay off the technical debt and get things cleaned up. Sometimes not. Honestly, it’s work just keeping a 50/50 success rate.
After doing this at least a dozen times, I wrote up a whitepaper tutorial for thinking about the design space and ergonomics of Universal apps. People sometimes reach out to me before they start design work, so I’m hoping to help these doctors and nurses think through a bunch of design considerations that they wouldn’t normally consider before they start handing me UI specs or broken prototypes.
I’d be curious for feedback on how it reads; how it could be improved; etc.
Designing Card UI for a Universal App