Tech Lead/Team Lead. Senior WebDev.
Intermediate Grade on Computer Systems-
High Grade on Web Application Development-
MBA (+Marketing+HHRR).
Studied a bit of law, economics and design
Location
Spain
Education
Higher Level Education Certificate on Web Application Development
This is kinda weird. You usually don't want your customers to catch bugs in production so usually and according to Git branches, you'll get:
Develop <- QA tests here
Test - Pre-production <- Client test here (business analysts, client's QA dept....)
Master (Production) <- where the customers interact.
Beta versions are not a stage itself, are releases on a given version with a given stack of new features to test globally.
There are many software applications that simply don't qualify to have a beta version (or alpha), i.e. a banking App. I can imagine customers getting a heart attack if any bug occurs here 😆
That being said you don't need to roll out an alpha nor a beta, it's just optional and depends on your market , the data you manage, the use cases your App has and the marketing strategy you follow.
There are other types of releases such an MP (minimum product), MMP (minimum marketable product), MVP (minimum viable product) and so on that can qualify just as placeholder minimum App, usually used to present to investors with the target of course of getting money from them.
I see in your profile that you are interested in both web and game development, try not to mix things related to one industry with the other because both have code, design and so on but them both can be also very different in terms of management and plan, just depends on the case.
You can make a game that's a MP just to show off the mechanics, sound, gameplay and so on like 7days2die did back those days, then create an alpha version from that and push it step by step till beta (that hopefully will come next year in this case) to finally get your product to final version (Release 1.0) out of beta. In this case, building a community is also important to get engagement and support.
Another way to handle that is to make an MP to get investment, then push it till release directly and releasing a demo (capped version of the game) some months before the oficial release date, like Flowstudio did with Len's Island.
Yes, I agree but I wanted to touch on the bare minimum, and I do agree about the MVP, although I do feel that it's better to have BETA versions to only a few people, such as any play testers for games. Thanks for pointing that out!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This is kinda weird. You usually don't want your customers to catch bugs in production so usually and according to Git branches, you'll get:
Beta versions are not a stage itself, are releases on a given version with a given stack of new features to test globally.
There are many software applications that simply don't qualify to have a beta version (or alpha), i.e. a banking App. I can imagine customers getting a heart attack if any bug occurs here 😆
That being said you don't need to roll out an alpha nor a beta, it's just optional and depends on your market , the data you manage, the use cases your App has and the marketing strategy you follow.
There are other types of releases such an MP (minimum product), MMP (minimum marketable product), MVP (minimum viable product) and so on that can qualify just as placeholder minimum App, usually used to present to investors with the target of course of getting money from them.
I see in your profile that you are interested in both web and game development, try not to mix things related to one industry with the other because both have code, design and so on but them both can be also very different in terms of management and plan, just depends on the case.
You can make a game that's a MP just to show off the mechanics, sound, gameplay and so on like 7days2die did back those days, then create an alpha version from that and push it step by step till beta (that hopefully will come next year in this case) to finally get your product to final version (Release 1.0) out of beta. In this case, building a community is also important to get engagement and support.
Another way to handle that is to make an MP to get investment, then push it till release directly and releasing a demo (capped version of the game) some months before the oficial release date, like Flowstudio did with Len's Island.
Hope it helps somehow :)
Yes, I agree but I wanted to touch on the bare minimum, and I do agree about the MVP, although I do feel that it's better to have BETA versions to only a few people, such as any play testers for games. Thanks for pointing that out!