Why The HTML5 Vs. Native Debate Obscures The Real Challenges Of Mobility

The article says the HTML5-versus-native debate hides the real mobility issues. Enterprises should first fix backend architecture and business analytics, because mobile changes data access, scale, and offline behavior in ways Web-era systems do not handle well.

Reading notes

#

• The HTML5 versus native argument is presented as a distraction from deeper mobile problems.
• Legacy Web architecture is described as unable to meet mobile demands for performance, scale, and data access.
• Mobile apps need data from private systems, public clouds, SaaS platforms, and connected devices.
• Mobile usage raises transaction volume, so architectures must scale elastically and keep working offline.
• The author says companies need mobile-optimized APIs backed by scalable cloud architecture.
• Those APIs should orchestrate data from many sources, reduce payload size, and transform data into mobile-friendly formats such as JSON.
• Mobile app portfolios are said to be judged with weak indicators like star ratings, which reveal little about user behavior or business value.
• Good mobile analytics should cover both app behavior and user behavior, including crashes, engagement frequency, timing, location, devices, and feature use.
• The article ends by saying mobile-savvy competitors can disrupt organizations regardless of client-side technology choice.