With the release of the groups and rules (Preview), it is important to consider the developer environments as part of the strategy.
Below is the list of pros and cons(Limitations).
I also added a few things you need to take into consideration.
Pros
Every developer environment comes with a message that indicates the purpose of the environment.
When the user tries to share the apps, it shows the below message to the App owner.
Users can create up to 3 developer environments. If they start developing solutions, you don’t have to manage/provision for them every time.
Newly created developer environments can become managed environments. This is to support the environment routing. This feature is currently in preview.
Developer environments don’t affect tenant database quota.
With routing, you can apply preconfigured settings such as Sharing Limits, Solution Checker, Usage Insights, and Maker welcome message.
New makers don’t need to know which environment they need to work on.
Cons (Limitations)
You will have less control over the naming conventions of the environments.
Flow runs/month (750) and capacity limits up to 2 GB.
Environments created using the Power Apps Developer Plan that have been inactive for the last 90 days will be deleted after the environment owners are notified.
There are a few more things to consider
You must enable Tenant level settings (Developer environment assignments) to leverage the developer environments.
You do not need to make default as a managed environment to enable the routing.
All developer environments created through environment routing are managed environments, as are all environments in a group. These environments require premium licenses to run Microsoft Power Platform assets.
Please create the comms to communicate the consequences with users, which will help you manage it properly.
Developer environments add more values once the environment routing becomes GA.