What does it mean when a feature is in the Beta Phase?
A Beta feature release refers to functionality that is feature-complete and has completed internal quality testing. At this stage, it is ready for real-world use and supports its primary business objective. However, it is not yet considered final or fully polished.
This phase of development allows us to gather feedback from Cleeng users, which in turn helps us to identify and rectify minor issues or bugs. It also allows us to collect feedback on potential improvements that can make the feature more usable or useful.
What you can expect in a feature’s Beta Phase
- Minor bugs: These are non-critical issues common to software releases, such as user interface inconsistencies, usability challenges, or unexpected behavior.
- Feature feedback loop: During this phase, we encourage your feedback on the behavior and the design of the feature. This feedback can be delivered directly in the Cleeng dashboard or through other channels you use to communicate with us. Feedback given at this stage is more quickly reviewed and included in platform updates.
- Communication: If you are actively providing feedback in the Beta phase of a feature we will stay in close contact with you on bug fixes and updates. At this stage, you can also engage directly with our product team in dedicated sessions on the new functionality.
- Support: If you encounter issues with features in the Beta phase you can expect the Cleeng support team to assist you as normal in the resolution of your problem.
How long will a feature be in Beta?
Product features are in Beta for no more than a few months, depending on their complexity. Exit from the Beta phase requires the removal of problematic bugs and the rollout of updates that improve the usability of the feature.
This is different from experimental features or pilot releases that may stay in Beta indefinitely. These features are usually accessible by invitation/request only and are hidden from other users. Experimental features are more exploratory, with much greater scope for change in the future. The primary goal of pilot releases is to evaluate the impact a productized version of the feature may have. Experimental features never relate to critical functionality and never affect the stability of your platform.