Mobile App Update Releases (Major/Minor/Patch)

NOVASOLUTIONS.TECHNOLOGY is engaged in the development, support and maintenance of iOS, Android, PWA mobile applications. We have extensive experience and expertise in publishing mobile applications in popular markets like Google Play, App Store, Amazon, AppGallery and others.
8+Years of work900+Completed projects100+In house employees19+Partners
Development and support of all types of mobile applications:
Information and entertainment mobile applications
News apps, games, reference guides, online catalogs, weather apps, fitness and health apps, travel apps, educational apps, social networks and messengers, quizzes, blogs and podcasts, forums, aggregators
E-commerce mobile applications
Online stores, B2B apps, marketplaces, online exchanges, cashback services, exchanges, dropshipping platforms, loyalty programs, food and goods delivery, payment systems.
Business process management mobile applications
CRM systems, ERP systems, project management, sales team tools, financial management, production management, logistics and delivery management, HR management, data monitoring systems
Electronic services mobile applications
Classified ads platforms, online schools, online cinemas, electronic service platforms, cashback platforms, video hosting, thematic portals, online booking and scheduling platforms, online trading platforms

These are just some of the types of mobile applications we work with, and each of them may have its own specific features and functionality, tailored to the specific needs and goals of the client.

Offered services
Showing 1 of 1 servicesAll 1735 services
Mobile App Update Releases (Major/Minor/Patch)
Medium
ongoing support
FAQ
Our competencies:
Development stages
Latest works
  • image_mobile-applications_feedme_467_0.webp
    Development of a mobile application for FEEDME
    756
  • image_mobile-applications_xoomer_471_0.webp
    Development of a mobile application for XOOMER
    624
  • image_mobile-applications_rhl_428_0.webp
    Development of a mobile application for RHL
    1052
  • image_mobile-applications_zippy_411_0.webp
    Development of a mobile application for ZIPPY
    947
  • image_mobile-applications_affhome_429_0.webp
    Development of a mobile application for Affhome
    862
  • image_mobile-applications_flavors_409_0.webp
    Development of a mobile application for the FLAVORS company
    445
Show more works

Releasing Mobile App Updates (Major/Minor/Patch)

Post-launch app lifecycle is continuous update stream of varying weight. Patch hotfix must ship in hours. Major release with new data architecture requires weeks of preparation and phased rollout. Treating them identically means either slowing critical fixes or shipping big changes without proper safeguards.

Semantic Versioning in Mobile Context

Semver (Major.Minor.Patch) works differently in mobile than server software. versionName is marketing string users see. versionCode (Android) and CFBundleVersion (iOS) are monotonically increasing numbers stores use to determine "newer/older". Desync between them causes real problems.

Patch (x.x.N): Crash hotfix, typo correction, translation fix. Increment versionCode, change versionName minimally. For iOS can use CFBundleVersionString without changing CFBundleShortVersionString — but stores treat as update, review still required.

Minor (x.N.0): New feature, UI change, new screen. No Breaking Changes in data schema, no API contract changes. User updates — nothing breaks.

Major (N.0.0): Local DB schema change (Room migration, CoreData migration), minimum OS version change, data structure refactor in Keychain/SharedPreferences. Needs migration strategy — user's saved data from old version must correctly transfer.

Most Painful Part — Major with Data Migration

Room (Android) and CoreData (iOS) provide migration mechanisms but require careful planning. Common problem: dev adds entity field, increments @Database version, but forgets Migration object — Room throws IllegalStateException: Room cannot verify the data integrity on existing user installs.

CoreData similar — change model without lightweight migration or mapping model. App crashes on launch for existing data devices while clean install works.

Strategy for complex migrations: fallbackToDestructiveMigrationFrom (Room) only if data loss acceptable. Most cases — write explicit Migration with SQL script. Test migration on real previous-version data, not just empty DB.

Release Process

Android: Build AAB, sign, upload to Play Console. Use staged rollout — start at 5-10%, monitor Android Vitals (crash rate, ANR) for 24 hours, then expand. For patches accelerate rollout. For Major — mandatory pause at each stage.

iOS: Build via Xcode Cloud or Fastlane with gym. Upload via Transporter or fastlane deliver. Use Phased Release (7 days, 1-2-5-10-20-50-100%) for minor and major updates. For hotfix — can skip Phased Release but review takes its time.

Automate via Fastlane: lane :release with increment_build_number, tests, build, upload. CI/CD via GitHub Actions or Bitrise — each main merge post-test prepares TestFlight/Internal Testing build.

Pre-Release Checklist

  • Data migrations tested on real upgrade scenarios (not just clean install)
  • versionCode/CFBundleVersion higher than last published
  • Release notes written in all supported languages
  • Backward compatibility with backend API verified (critical for Major)
  • Firebase Crashlytics or Sentry configured and working in release

Timeline depends on update type: patch — one to two days, minor — three to five days, major — one to three weeks with migration testing.