Mobile development guide: Testing, requirements and security
A comprehensive collection of articles, videos and more, hand-picked by our editors
What is most effective way to manage updates to mobile applications once they are deployed?
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
Mobile apps development challenges don't end when the apps are deployed. These apps need to be updated with a much faster cadence than their desktop counterparts. The concept of "RevApps" offers a useful way to think about this challenge.
RevApps are the apps that an organization uses to strengthen its market share position, grow revenue and advance ahead of the competition. Simply put, they are "revenue applications."
Research firm Gartner talks about pace-layered applications that comprise "systems of record," "systems of differentiation" and "systems of innovation." Systems of record are those systems that every organization has, such as payroll and HR. Systems of differentiation (SOD) are the systems you need because of the nature of your business: For example, if your business is inventory management, the inventory management system would be considered an SOD. And the systems of innovation are the RevApps -- the apps that separate you from competitors. Examples include loyalty card apps or dividend rewards apps.
QRevApps are the apps that an organization uses to strengthen its market share position, grow revenue and advance ahead of the competition.
These are the apps that need to be revised and deployed with a much faster cadence than other, normal apps. And the RevApps are invariably mobile apps.
For mobile apps development projects, what is the best way make sure that these apps can be revised and deployed effectively and repeatedly? The answer, in short, is automation of the deployment process.
We have come to accept that we need a common infrastructure for our development teams, testing teams and change-and-release teams. But that idea was a response to the chaos created, or inherited, over many cycles of technology and methodology changes. We now realize that the way the Web team works, for example, is completely different from how the back-end team organizes. Yet we still try to standardize the infrastructure.
Mobile apps change that. The need for speed and for reliable and repeatable deployment means that we have to put in place solutions that support and understand the complexity of mobile apps -- while also taking into account Agile development, continuous integration and deployment. These solutions must also integrate with our existing tools for ticketing and testing, as well as those for repository management.
As mobile updates occur with increasing rapidity, the most critical part of modern tools for mobile apps is the ability to directly deploy to the app stores. Direct, automated deployment to the app store is the next logical consequence.
Related Q&A from Kevin Parker
Add controls to the business of delivering software, and teams will scream about delays. However, fast development is often the result.continue reading
Kevin Parker discusses the pros and cons of industry analyst reports and advises when it might be best to trust your own instincts.continue reading
Actually, application development veteran Kevin Parker says ALM is really a part of the APM process when you look at it from a distance.continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.