The March 9, 2017 Hangouts announcement is easier to read as two timelines than as one launch. Google placed Meet at general availability, with distribution to G Suite customers over the following weeks. Chat occupied a different position: customers could apply to try it through the Early Adopter Program. Those statements describe distinct access stages on the same date. [hangouts]
A second distinction sits inside Meet itself. The administrator notice said existing Hangouts users would start with Meet off, leaving administrators to coordinate its introduction. Newly created domains, by contrast, would have it on by default. The compact matrix is therefore existing domain: off initially; new domain: on initially. Neither row describes the release status of Chat. [admin]
Putting the two comparisons together prevents a misleading shortcut. General availability named Meet’s product release stage; it did not mean every existing organization had enabled it. Conversely, a new domain’s default did not convert Chat’s application program into general access. A reader checking the announcement should keep the product column separate from the domain-default column rather than compressing both into available. [hangouts][admin]
For a historical status note, record March 9 as the announcement date, the ensuing weeks as Google’s stated Meet rollout period, and Chat as application-based early access without an admission date established here. Add the two Meet defaults beside those entries. Both notices came from Google: together they clarify its launch terms, but they do not independently measure which customers received access when. [hangouts][admin]
Source documents
- Meet the new enterprise-focused Hangoutshttps://blog.google/products-and-platforms/products/workspace/meet-the-new-enterprise-focused-hangouts/
- Hangouts Meet public launch and Hangouts Chat Early Adopter Programhttps://workspaceupdates.googleblog.com/2017/03/hangouts-meet-public-launch-and-hangouts-chat-eap.html