With https://bugzilla.mozilla.org/show_bug.cgi?id=1672202, Experiment API uses default values for features such as aboutwlecome. Discussed briefly with Kate on how we can leverage Nimbus API to have targeted default JSON to show a pin on-boarding experience to subset of users ( say windows 10 build > 1903) This has advantage of keeping a) multiple targeted default at one place in a manifest/config b) use Nimbus targeting to reach these default JSON c) re-use schema validations and automated tests d) In future if we decide to serve these defaults via remote settings , it should be easily extensible Search feature has similar requirement of targeted defaults to show specific search experience based off targeting such as locale
Bug 1694257 Comment 1 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
With https://bugzilla.mozilla.org/show_bug.cgi?id=1672202, Experiment API uses default values for features such as aboutwelcome. Discussed briefly with Kate on how we can leverage Nimbus API to have targeted default JSON to show a pin on-boarding experience to subset of users ( say windows 10 build > 1903) This has advantage of keeping a) multiple targeted default at one place in a manifest/config b) use Nimbus targeting to reach these default JSON c) re-use schema validations and automated tests d) In future if we decide to serve these defaults via remote settings , it should be easily extensible Search feature has similar requirement of targeted defaults to show specific search experience based off targeting such as locale. @mardak do you think this approach will suffice smarter targeting need for Pin as default experience?
With https://bugzilla.mozilla.org/show_bug.cgi?id=1672202, Experiment API uses default values for features such as aboutwelcome. Discussed briefly with Kate on how we can leverage Nimbus API to have targeted default JSON to show a pin on-boarding default experience to subset of users ( say windows 10 build > 1903) This has advantage of keeping a) multiple targeted default at one place in a manifest/config b) use Nimbus targeting to reach these default JSON c) re-use schema validations and automated tests d) In future if we decide to serve these defaults via remote settings , it should be easily extensible Search feature has similar requirement of targeted defaults to show specific search experience based off targeting such as locale. @mardak do you think this approach will suffice smarter targeting need for Pin as default experience?