I was wondering, as we can create different environments in Launch like development, staging and production and it also exposes the corresponding url like . Why don't we just directly add this to the AEN's page header instead of going through all the cloud settings? Wouldn't this grant the devs and stakeholders more control of what launch config and environment they want to run, instead of getting locked to just using launch-staging and launch-prod?

When we create a new Adobe Launch configuration in AEM, we provide the values of fields like "Associated IMS Configuration", "Company", "Property" etc, and then on the next window, the staging & production fields get populated automatically. I was just wondering in this case, what is the use case of the "development" environment(s) in Adobe Launch. Are they just for developing the properties, but do not serve as an integration point in AEM? And if not, could someone guide me resources on how to ...