DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
  1. DZone
  2. Testing, Deployment, and Maintenance
  3. Testing, Tools, and Frameworks
  4. How Often Should You Update Your Mobile App?

How Often Should You Update Your Mobile App?

The author recommends that most mobile app providers release every one or two weeks — read on to see the research!

Tim Ryan user avatar by
Tim Ryan
·
Dec. 20, 19 · Analysis
Like (2)
Save
Tweet
Share
20.64K Views

Join the DZone community and get the full member experience.

Join For Free

people looking at their phones

Do you know?


For Android, iOS, and other apps, release frequencies vary. Managed app testing leader Testlio recently queried more than 75K client release records, covering a diverse range of industries (including Commerce, Education, Entertainment, Finance, Productivity, Sports, and Travel). Collectively, these Testlio clients have a user base of more than 1.5 billion people.

You may also like: Introduction to the World of Mobile Application Testing

Based on a comprehensive analysis, client conversations and other considerations, Testlio recommends that most mobile app providers release every one or two weeks. Specific Testlio's findings on their clients' mobile app release frequencies are:

  • 65% of providers release at least once per month.
  • 26% of providers release every two weeks.
  • 15% of providers release every week.

The Testlio findings are consistent with other research and observations. For example, noted that the top 100 grossing apps release about every 14 days. found that the top 200 free apps have a median update window of 18 days. Many companies run one or two-week sprints in their engineering organizations.

Multiple companies who today release monthly indicate that they want to release more often.

"We're seeing a trend towards releasing mobile apps every 1 or 2 weeks. I believe several forces are at play: increasingly agile teams, a 'shift-left' QA mindset, on-demand app testing services, and a balanced approach to user needs. Providers are achieving predictable rhythms while delivering great customer experiences."
— Steve Semelsberger, CEO, Testlio

Of course, there are many reasons to provide an app update: operating system and/or hardware changes, critical fixes, marketing events, new functionality, seasonal initiatives, and more. Apps are integral tools in users' daily lives. Accordingly, providers feel pressured to deliver high-quality apps with flawless end-to-end customer experiences. Maintaining a fresh and bug-free experience is the lifeblood for many apps.

Smart providers also are thinking about not releasing too frequently, considering distribution point requirements and potential user burdens (including battery, network, login, and learning).

Note that 18% of Testlio clients don't follow a set release schedule, updating their apps on an ad hoc basis. Many of them test and release more often in some periods and less frequently in others.

Overall, providers must consider a multitude of considerations when designing a mobile app release cadence. It's critical that testing be flexible, burstable, and scalable-enabling release candidates to quickly move from engineering to points of distribution (Google Play, Apple App Store, etc.).


Further Reading

5 Steps to Making Mobile App Testing More Efficient

Mobile Testing 101: What You Need to Know





mobile app Release (agency) Mobile application testing

Published at DZone with permission of Tim Ryan. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • How To Generate Code Coverage Report Using JaCoCo-Maven Plugin
  • Architectural Miscalculation and Hibernate Problem "Type UUID but Expression Is of Type Bytea"
  • Data Engineering Trends for 2023
  • Kubernetes vs Docker: Differences Explained

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: