Hi friends,
I would like to know when you consider that your app is ready to enter beta.
Should the beta look as much as possible as a final release?
Are all the assets integrated (intro animation, all musics, sfx) or do you leave temporary placeholders, etc?
How do you decide the right time to enter beta?
Thank you!
Comments
But getting feedback takes time, so if you want to do it in a defined time span, you can release minim viable product, what you think is essential and go beta before everything is completed. Sometimes it is better, because from feedback you could prioritize features and maybe even don't waste your time on some features that you wanted to implement, but feedback showed that these features where not needed.
It also depend so on type of beta. If it's provide, it can be minimum viable game, if its open, you would want it as finished as possible.
For example, we decided to use Android market for betas and release stable games on IOS. But still you don't want to publish half finished app to Android, so basically we try to publish completed app and iterate/improve on feedback from android before releasing IOS.
In your case how would this strategy differs when using a service like Testflight or hockeyApp for a private beta period?
That means, one more step between app dev and release to the stores.
We did not know what would happen and if this is a better choice (actually we probably still don't know how it will turn out), but all I can say that we received great feedback on features that should be improved and implemented from players that we don't even know. And we could never collect such large user base of testers/players on testflight ourselves, thus collecting this kind of feedback would not be possible for us using testflight etc.
Now we at least have some confidence in app, in ourselves and we know now that we should invest more time in this app (that project was not a complete fail) and have a feeling that major release (real release) is still ahead of us (on IOS platform).