As others have said it's basically marketing departments appropriation of developer words. Getting to play an Alpha makes it seems like you're in an exclusive club, that you're seeing it raw before it's finished. It also allows them to say "But that's only an alpha build" when people speak negatively about it. Then, as others have said, there is the "Alpha male" and "Alpha being the best" idea that adds to the marketing. But I'll tell you one thing; If your maps have all of the models positioned correctly, complete with bounding boxes and full HD textures. If you have a full UI without some development art. If the software isn't crashing a lot and If it's feature complete then it's not really an alpha. The alpha build for a game being released this month would have been at least 12-18 months ago.
They Just mean Demo or server stress test, but no one wants to play a demo. They want to play an APLHA, because fuck yeah. Exclusive. ALPHA!!!!!!
If you actually want to know what Pre-Alpha, Beta, Open Beta and RC are, from the development side of things actually are, and not what marketting deparments want to you to believe they are, take a look at the Stages of release page on Wikipedia. I'll summarise here.
- Pre-alpha: Pre-alpha refers to all activities performed during the software project before testing. These activities can include requirements analysis, software design, software development, and unit testing.
- Alpha: The alpha phase of the release life cycle is the first phase to begin software testing. In this phase, developers generally test the software. Alpha software can be unstable and could cause crashes or data loss. Alpha software may not contain all of the features that are planned for the final version. The alpha phase usually ends with a feature freeze, indicating that no more features will be added to the software.
- Beta: Beta phase generally begins when the software is feature complete but likely to contain a number of known or unknown bugs. Software in the beta phase will generally have many more bugs in it than completed software, as well as speed/performance issues and may still cause crashes or data loss. The focus of beta testing is reducing impacts to users, often incorporating usability testing.
- Release candidate: A release candidate (RC) is a beta version with potential to be a final product, which is ready to release unless significant bugs emerge. In this stage of product stabilization, all product features have been designed, coded and tested through one or more beta cycles with no known showstopper-class bugs. A release is called code complete when the development team agrees that no entirely new source code will be added to this release.
What they mean in the case of something Like Titanfall 2 is:
- Pre-Alpha: Small demo, maybe a server stress tests, maybe a bit of monitoring for exploits.
- Alpha: larger demo, a larger server stress test.
- Beta: Demo
It irrationally annoys me, being from a development background when they misappropriate or reappropriate the terms as it can be used as a shield from criticism, and also gives an unrealistic expectation of what an actual Alpha build of a game looks like. (hint: It's MS Paint made UI by people who can't draw, crashes a lot and probably has placeholder textures and models and at least 1 penis drawing)
EDIT: I found a better description of the stages of development, more specific to game software, here but essentially it's the same.
Log in to comment