Experimental features and betas

Robin offers experimental features and early preview betas so you can try features before they are complete. Keep these points in mind when you join a beta or an early release preview of the app.

Experimental Features

An experimental feature is how Robin tests an idea that solves a problem. Robin shows it to you as fast as possible, before it is complete or ready for production. Features that are not ready for production can have planned changes. Robin drops some of them or takes them back to the design stage.

Admins can usually turn on experimental features in Organization Settings (Manage > Organization in the web dashboard). Think about these points before you do:

  • Turn on experimental features only if you are ready for some quirks. Do not rely on an experimental feature if you do not want it to affect your Robin members.
  • Some experimental features test the workflow, not the specific implementation.
  • Robin wants feedback, not only bug reports. Send your thoughts and suggestions on experimental features at any time.
  • Robin considers reported issues, but the timeline for them is often different from the timeline for production-ready features.

Early Preview beta

An early preview beta prepares you for a feature that is further along in development. Early preview beta testers see products before every Robin customer can try them. In return, they give important feedback.

Robin chooses carefully who gets early access. If you want to join an early preview, keep these points in mind:

  • Timelines are hard to predict. Robin shares rough outlines of progress, not detailed weekly reports.
  • Some early previews are admin-only. Robin members can see different results, depending on their user level.
  • Feedback is especially helpful to the Robin team during early previews. In return for early access, Robin asks for time to get your feedback to improve the product.

Articles in this section

Was this article helpful?
0 out of 0 found this helpful
Share