What does it mean when a feature is in Early Access?
An Early Access 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 from an Early Access feature
- 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 on an Early Access 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 an Early Access feature, you can expect the Cleeng support team to assist you as usual in resolving your case.
How long will a feature stay in Early Access?
Features typically remain in Early Access for a few months, depending on their complexity. Exit from this 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, which may remain in Early Access for an extended period. These features are usually available by invitation or request only and are hidden from general users. Experimental features are exploratory and may change significantly before becoming part of the product. They never affect critical functionality or platform stability.