The Nimbus team has welcomed many new team members including:
- Yashika Khurana, Web
- Mike Williams, Web/Data
- Daniel Berry, Data Science
- Barret Rennie, Desktop
We're thrilled to have them all aboard!
Nimbus now supports the ability to send messages to mobile clients through messaging surfaces in each mobile application. This unlocks the ability for Nimbus to run surveys, update users about important new information, or incorporate messages into other experiments/rollouts. More detailed information can be found here.
Mobile devices use a different list of languages than desktop Firefox does, and so the locale field on the Audience page didn't work as expected for mobile experiments. To address this, we've added a new 'Language' field on the Audience page that can be used to target device languages for mobile experiments.
Mobile devices do use the same list of countries that desktop Firefox does, and now country filtering has been implemented in the mobile client and so country targeting for mobile experiments is now available on the Audience page.
There have been several ongoing bugs that affected the automatic analysis of many experiments, which have now been resolved. All experiments should now have access to the full analysis report including all metrics. If any experiment analyses are still missing information, please reach out on #ask-experimenter.
Experimenter now has the ability to export a list of all Nimbus experiments as a CSV spreadsheet using the 'Reporting' button on the landing page. This can help organize large groups of experiments for review and planning.
Nimbus Features are defined using manifest files in the code repositories of each supported Firefox application across desktop and mobile. All features for all supported applications are now automatically imported by Experimenter and automatically updated as new features or changes to existing features occur. Each Feature has a schema that is either specified in the manifest or automatically generated based on the Feature's variables, and is used to validate the JSON that is provided in each branch.
Every experiment or rollout in Nimbus includes a targeting expression that clients use to determine whether to enroll or unenroll. The targeting expressions is frequently re evaluated after enrollment to determine if the client should unenroll early before the experiment ends. If any part of the targeting expression evaluates to False, then the client will unenroll. Sometimes this is the desired behaviour for an experiment, sometimes it is not. For cases where clients should not unenroll even if the targeting no longer matches, we now provide the option for Sticky Targeting, which can be found on the Audience page. If an experiment uses Sticky Targeting, then clients will not be unenrolled, even if the targeting becomes False, until the experiment ends.