feat(message-system): add ab testing message

[adderpositive]

Description

• Experiments would use a Message System to configure Feature Flags (i.e. there will be no UI to config experiments, deployment of the messaging system will be required - independent from Suite release though).
• Experiment ID (e.g. rename-trade-section)
  • Multiple Variation IDs (e.g. control, buy-swap) - this may be unlimited, but in reality, we won’t use more than 4 for one experiment
  • Each would have an experiment distribution percentage between 0 - 100%

Example of experiments

experiments property is placed in the top level of config.v[version].json

  "experiments": [
      {
          "conditions": [
              {
                  "environment": {
                      "desktop": ">=24.5.1",
                      "mobile": "!",
                      "web": ">=24.5.1"
                  }
              }
          ],
          "experiment": {
              "id": "3bed56a4-ecd8-4e0f-2910-014b484c2aff",
              "groups": [
                  {
                      "variant": "A",
                      "percentage": 30
                  },
                  {
                      "variant": "B",
                      "percentage": 70
                  }
              ]
          }
      }
  ]

• conditions are the same property as for the action - https://github.com/trezor/trezor-suite/blob/develop/docs/features/message-system.md
• experiment has required parameters id and groups
  • id must be unique, but can also be used for nice naming (e.g. "button-testing")
  • groups as an array of testing groups - minimum length of items is two
    • percentage is a number between 0 and 100, a sum of all percentages has to be 100
    • variant can be any string - name of the group
• updated documentation - https://github.com/trezor/trezor-suite/blob/feat/ab-testing-on-message-system/docs/features/message-system.md

TODO

• update config.v1.json on the develop and stable - add experiments property

Related Issue

Resolve #15279
Resolve #15067

Testing

This PR was tested separately. More information you can find here - #16145 and https://www.notion.so/satoshilabs/A-B-testing-170dc526060680ab9d5af4e5c9d87876

[MiroslavProchazka]

Hello @adderpositive , please let's wait for @tomasklim and let's discuss this in more broader context. Personally I do not like the idea to mix it with message system, so lets discuss.

[adderpositive]

Hello @adderpositive , please let's wait for @tomasklim and let's discuss this in more broader context. Personally I do not like the idea to mix it with message system, so lets discuss.

Yes, of course. We have been already discussing the extension of the system. I will go ahead and briefly describe it here.

1. The first solution was implemented directly into the message-system messages. After brainstorming, I have refactored it to the solution in the PR.
2. The next solution is to rename the system - message-system can be confusing if it manages more functionality than messages only. Examples of some names toggle-system, push-system, ...
3. But @matejkriz had an excellent point of view the message system should provide a solution how to safely and unforgettably deliver a message to the Suite at runtime - the message can be distinguished as banner, feature or experiment, etc. It is different than it should display only some messages.

I hope it is understandable a little bit. :)

[adderpositive]

Tests are failing because the property experiments doesn't exist in the config.v1.json. It should also be updated on the develop and stable.

Fixed

[tomasklim]

Tests are failing because the property experiments doesn't exist in the config.v1.json. It should also be updated on the develop and stable.

Please make it optional. So that the app does not crash when experiments are not available at all. We will maybe separate AB testing, feature flags, and message system into 3 systems in the future

[adderpositive]

Tests are failing because the property experiments doesn't exist in the config.v1.json. It should also be updated on the develop and stable.

Please make it optional. So that the app does not crash when experiments are not available at all. We will maybe separate AB testing, feature flags, and message system into 3 systems in the future

Ok. In my opinion, it’s a good approach to separate messages, features, experiments, etc., but only on the application layer. On the data layer (config.vx.jsw), splitting the config into more parts would make maintenance difficult and confusing.

[github-actions]

🚀 Expo preview is ready!

• Project → trezor-suite-preview
• Platforms → android, ios
• Scheme → trezorsuitelite
• Runtime Version → 21
• More info

Learn more about 𝝠 Expo Github Action

[adderpositive]

@matejkriz After our discussion, I removed strict validation. Additionally, you can see a description below if the sum does not equal 100. I hope this helps with your review. 🙃 Changes here c83ddc5

If an array of groups is empty the defaultComponent (first in components) will be displayed.
If the sum of the items in the group is more than 100, the percentage created from instanceId will assigned to the matching group.
If the sum of the items in the group is less than 100 and the percentage created from instanceId does not match any group (e.g. A - 30%, B - 30%, user percentage - 69), it will return defaultComponent (first in components).

[tomasklim]

/rebase

[github-actions]

Start rebasing: https://github.com/trezor/trezor-suite/actions/runs/12651874595