1848437 - Decide on deep link schema we'll use for running custom onboarding experiences

Status: NEW

(Firefox for Android :: Onboarding, task)

Description

[Joe M [:jmahon]]

Experimentation, Marketing, Product, and Android Eng teams should come together to figure out what rubric we will follow with deep links to make sure marketing campaigns can be executed without a hitch.

If we can get the deferred deep link mechanism to work, we need to figure out:

• What will the deep links look like when marketing adds them to a campaign?
• How will we parse them? How will we handle errors if the deep link is malformed?
• (Technically-speaking) How will we maintain a variety of onboarding experiences that might coexist at the same time?
• (Process-speaking) How will we manage co-running a variety of onboarding experiments in such a way that they don't compete or conflict?

Comment 1

[Roger Yang [:royang]]

From investigation we should be using the deeplink scheme we're currently using for each branch.
We can use the scheme with a host name that we know is from deferred deeplink and a string after the host name to let us know which campaign it is. Something like this Fenix://<hostname>/<campaign ID>.

For example: fenix-dev://testing/1234. We get get the 1234 part by calling deepLink.lastPathSegment.toString().

Comment 2

[Roger Yang [:royang]]

For malformed deeplink, If we get a deeplink that have a path segment that we're not expecting, we can log it.