After the app has been successfully downloaded to the App Store, the next step is to maintain and support that app. The most popular apps on stores often update regularly every week while the life cycle of other apps is usually 1 or 2 times a month.
Some information to note:
- Most successful apps come with 1-4 updates / month
- The level of updates depends on user feedback, data and programming team size
- Most feature updates should be scheduled for up to 2 weeks
- Balance between quick updates related to bug fixes and feature release versions – these versions take a long time
- Plan 2-4 versions of updates beforehand, but also consider market needs
- Why is the update app important?
Update app is one of the best marketing tools of dev. As the number of apps that users install on the device is increasing, regular updates can help the app get more attention than other apps on one device, as it will appear in the counter list. such as App Store or Google Play Store. Apple and Google also like updated apps, especially with the launch of the main OS.
In addition, app updates will be associated with users, as updates include bug fixes and user-requested features. It shows you are serious about the app and the app is still being maintained. At this point, you will spread that connection to offline activities when loyal users introduce apps to acquaintances. This form of commitment will not be achieved based on Marketing alone.
Finally, app updates provide the opportunity to dev "talk" to userbase through the creation of notes. While the number of users who are likely to read release notes is quite low, those who actually read a lot are mostly technical savvy people and use the app the most. The release notes will definitely not be ignored.
2. App updated every month
The app store does not reward the psychology of "just launching it will benefit". If you feel you are not responsible for updating the app at least once a month, you should seriously consider app programming from the beginning. Your app store updates should be driven by feedback on the quality of users, the amount of data and the level of market insights. You should balance these factors and the appropriate update level will take a lot of time. Be cautious about planning the initial release of updates that will ensure these updates reach users sooner.
Of course, if you have a large number of apps in your portfolio, updating them every month is a challenge. There is also a case of app in the "maintenance status" to wait for the next investment.
3. Launch updates about features
The level of app updates mostly depends on the types of features in the app you are trying to solve. The more features or features the greater the more time it takes for the app to update on users' devices.
Suggestions from Savvy Apps are to solve features that take more than 2 weeks to program. If a planned feature takes months, you should outline the strategy, rather than trying to stuff it in 2 weeks. The reason is that the 2-week programming life cycle requires a lot of days to check and refine updates. Including approve app, it took you 3-4 weeks.
The situations in which a feature needs to be more comprehensive require many months of effort, which is best suited for larger teams. More teamlowns have the resources to make many versions come out at the same time: a group will be linked with bug fixes and app maintenance, a feature upgrade team is expected to come out in 1-2 months. If you are an independent dev or don't have many people to work with at the same time, focus on the feature development life cycle that takes up to 2 weeks.
4. Fix bug updates
Normally, bug fix updates will help make the app more stable, like the recent Apple and Google OS release – iOS 9 and Android 6.0 – mainly related to stability and bug fixes rather than features. new.
For older apps, because a large market is available, fix bug updates are quite common. These apps focus on developing and stabilizing the user experience because their features have been greatly modified. These apps often have a longer feature-set programming life, which occurs simultaneously with important updates. In contrast, App Store release notes are simply "We offer regular updates to make the app better for you."
Bug fixes usually occur weekly or every 2 weeks.
5. Large updates compared to small updates
Versions that update the feature for updates to large apps while fixing bugs are usually for small apps. Large versions or feature updates often come with the second version of that version, while small updates are the last number in the 3-letter sequence. For example, a feature can go from v2.1 to v2.2, also fix bugs update from v2.1 to v2.1.1.
Conventions on the number of changes are quite large in the industry and continue to improve. For desktop software, with the speed of common browers, the number of simple and higher versions. In January 2016, Google Chrome is in ver 47 and Mozilla Firefox in ver 43. Similarly, Facebook and Google generally begin to admit the above ink for mobile apps. Facebook's flagship App is in ver 46 and each version will jump a plump number. The approach to these version numbers is not very useful to users, but will represent how the numbers of the updated version work in the future.
6. Sample calendar update and app schedule
After the first version, the next update may focus on the bug. Devs should solve as many common problems as possible and don't worry about adding any features, as long as they don't make v.10 removed. This approach will reduce the total number of support requests, giving you the opportunity to increase your app store rankings and avoid updates for weeks. At Savvy Apps, they tried to release bug fixes to an app store within a few days after app v1.0 was released. And fix the first bug will be numbered v1.0.1.
After that, each release will include some bug fixes and progress. You can then start switching to the feature update life cycle from 1 to 2 weeks. As mentioned, if you don't have a large app team, cultivate a feature until it matches the programming round and design 1-2 weeks. The first major feature update is marked v1.1 and if 2 updates are released in a row, they will be v1.1.1 and v1.1.2.
When users give feedback via support systems, App Store, social networks and other places, devs should keep track of the most requested content and put them on top to start moving them into each his update. Use analysis, reasoning such as reporting crashes and other hard data to optimize objects in updates. Then, continue checking the app store's approval many times as needed. The release of future features will be numbered v1.2, v1.3 … and major repairs will push the version number to v2.0.
Overall, it's best to plan for 2-4 updates as well as a wider view for 6 or more months. Besides continuing to classify them according to market demand.
Normally updates app is about 1-4 times in 1 month. But if you are an independent dev or a small team can produce a version in 1 month. Bigger app groups with more completed apps will fall in 2.3.4 updates. You should continue to balance between adding features and stabilizing your app. Maintain the principle and avoid making the application scope slow. With this strategy, you will definitely help yourself with a good set of updates according to your userbase.