It's critically important these days to consider mobile access to your healthcare software, since after all, most consumer usage will be through a mobile device. Therefore, it is important to consider how you will deliver your healthcare solution through a mobile device, the starting and end-points in terms of going native, or not.
MOBILE FIRST DESIGN
Meeting your users where they are to change behavior is critically important. However, we often see initial designs instinctively begin from a desktop or laptop display configuration, when the reality is that most individuals today access medical apps through their mobile device. With approximately 61% of all web traffic occurring through mobile (36% desktop, 3% tablet), and people spending on average 5 hours a day on a smart phone device, solution providers must think Mobile first not second when designing behavior change solutions, and strategically plan for mobile device access via native developed mobile apps, vs cross platform development, vs progressive web app or just the native device Internet browser.
Native Apps
Better performance in the native device, with full access to native APIs and slightly enhanced user experience in alignment with native interface guidelines and offer smooth animations and transitions.
IOS
IOS covers 55% of US mobile app users. HealthKit provides a central repository for health and fitness data, apps communicate with the HealthKit store to access and share this data.
Android
Android covers 45% of US mobile app users. Google Fit is a health-tracking platform providing a single set of APIs that blends data from multiple apps and devices.
Non-Native Apps
Cross platform compatibility, and faster development time. Be cautious of limited device-specific functionalities and access to native APIs (this has become less of an issue over time).
React Native
React primitives render to native platform UI, meaning your app uses the same native platform APIs other apps do. Facebook supported and a large developer community.
Progressive App
No need to download and install, and improved SEO to make your app more discoverable. reduced performance on older devices and bad networks.
Comments