Mobile application lifecycle management is NOT a re-brand of
application lifecycle management because:
-Mobile app development requires in-depth network (e.g.
bandwidth optimization in codes, bandwidth simulation) and mobile deployment
knowledge, which is very different from traditional application lifecycle
management. Traditional Java/.NET app may not care about these areas
-Build/deployment is very specific to the appstore, e.g.
AppStore has very unique application submission rules, which traditional
application lifecycle management don't care, or don't have such -constraints.
These rules dictate or influence the way you write mobile app, and how you
deploy
-Diagnostic and troubleshooting paradigm is very different for
mobile app. In traditional application lifecycle management, you have JVM
or kernel level troubleshooting on the server side. In mobile app, the
diagnostic approach is very challenging due to the diversity of devices, and
also feasibility (e.g. you won't be able to remote control the mobile device,
or emit diagnostic information remotely).
-Performance monitoring and analysis in traditional
application lifecycle management can rely on JVM or CLR-centric performance
tools (e.g. CA Introscope, dynaTrace). But mobile app performance is not mature
to have end-to-end or front-end monitoring yet. Most performance areas in
mobile app are focused on memory management (due to the footprint).
-User provisioning, mobile component merging, re-use and
upgrade are unique device management issues for build/deployment/support, and
not prominant in application lifecycle management.
No comments:
Post a Comment