Implemented targeted and progressive feature rollout process

We have implemented a more rigorous code deployment process as part of a larger plan to reduce if not hopefully entirely eliminate occasional regression errors and avoid unintended surprises pertaining to edge case issues. 

1. Deploy to internal team for a period of several days to several weeks. These deployments take place within one of several designated staging environments.
2. Invite Friends of Adalo to test the new feature. Friends of Adalo is the moniker given to a group of Adalo experts who are actively building and maintaining multiple production apps on the Adalo platform. We will then incorporate any feedback provided by this group.
3. Initiate a progressive rollout, starting with 10% of the user base. Incorporate feedback and bug fixes communicated to the dev team via customer success.
4. Increase rollout to 50% of the user base. Continue incorporating feedback and bug fixes communicated to the dev team via customer success.
5. Bump rollout to 100% of the user base.

While this process does slow down velocity, we are already seeing a dramatic reduction in support requests associated with regression issues found in the legacy app environment.