More native apps, better user experiences
Asked about how to make the tradeoffs between native and single mobile app strategies, Gartner’s Wong says, “We advise our clients that where the highest fidelity is desired for flagship apps, typically customer-facing apps, we recommend native development. However, there are many other app use cases [usually non-customer facing] that can be effectively addressed with cross platform mobile app development platforms (MADPs), and increasingly low code or no code rapid mobile app development (RMAD) tools.”
The use cases for MOE differ from a MADP like Apache Cordova. Developers build one WORE app for both iOS and Android with Apache Cordova drawing on widely available programming skills, eliminating the need for redundant Android and iOS platform specialists. But abstracting the native Android and iOS UIs from direct access by developers comes with a price. User interaction with a Cordova apps isn’t as natural, responsive or immersive.
MOE developers expend more programming effort to build native UIs. Compared to Cordova, it’s less efficient, because MOE does not reuse the UI elements but delivers a native UI experience that’s often vitally important to attracting downloads of flagship apps and retaining loyal users that app marketing specialist Fiksu pegs at $2.47 per user in acquisition costs. The potential MOE programming manpower savings would support an increase in the number of native mobile apps produced compared to building redundant iOS and Android apps.
MOE doesn’t offer 100 percent reuse. But compared to a full rewrite for native performance, the 60 percent reuse claimed by McVeigh can’t be overlooked, especially by firms with a big Android development staff. Added advantages might be realized by firms wanting to repurpose enterprise Java developers to mobile as business priorities shift from the web to mobile.
Sign up for CIO Asia eNewsletters.