After a preliminary release, the following update should be exclusively bug focused. Squash as numerous common issues as you possibly can and do not even be worried about adding any features that did not result in the v1. cut. This method will decrease your total support demands and provide you with the very best opportunity to enhance your Mobile App Developer store ratings. It will help without getting an update take multiple days. At Savvy Apps, we attempt to push an insect fixing release for an application store within times of a v1. application being launched. The very first bug fixing update version number could be v1..1.
After that, each release will include some bug fixes and refinements. Target a number of each while starting to transfer to the fir-2 week feature building release cycle. As known as out earlier, hone an element until it may fit inside a 1-2 week development and design cycle unless of course you’ve got a bigger application team. The very first major feature release could be called v1.1. If two smaller sized updates were shipped after that, they’d be versioned as v1.1.1 and v1.1.2 correspondingly.
As users provide feedback using your support system, the application store, social networking along with other places, keep an eye on probably the most requested products and bubble them to the peak. Then begin moving these products into all of your releases. Use analytics, diagnostics like crash reports, along with other hard data also to help prioritize products to your releases. Also still take into account Mobile App Developer store approval occasions when needed. Future feature releases could be labeled v1.2, v1.3, and so on. A substantial overhaul would then push the version number to v2..
It’s generally a good idea to possess 2-4 releases prepared in addition to a broader overview for six or even more several weeks. None of the releases ought to be firmly solidified though. Have them fluid and then triage them according to what you are seeing on the market.
While the amount of Mobile App Developer updates will normally maintain the plethora of 1-4 monthly, clearly in which you fall around the spectrum will be different. Individuals or smaller sized teams may be capable of getting out an excellent release monthly. Bigger ones with increased mature apps will often maintain that two, three, or perhaps four updates range. Still balance adding features and stabilizing your application. Stay disciplined and steer clear of application scope creep. With this particular approach, you’ll ultimately place yourself in the very best position to possess a healthy group of updates flowing for your userbase.