Help shape Microsurvey specs

[data-sync-user]

Shaping specifications by attending meetings for the Mobile micro surveys as the iOS representative.

Details tracked here: https://docs.google.com/document/d/1C-YxKNh1eOuKmMNm_5gQMWrxNQCRJ73fTf_6qvjzeEA/edit

┆Issue is synchronized with this Jira Spike

[data-sync-user]

➤ Cyndi Chin commented:

Microsurvey Docs: https://docs.google.com/document/d/1C-YxKNh1eOuKmMNm_5gQMWrxNQCRJ73fTf_6qvjzeEA/edit ( https://docs.google.com/document/d/1C-YxKNh1eOuKmMNm_5gQMWrxNQCRJ73fTf_6qvjzeEA/edit|smart-link )

[data-sync-user]

➤ Cyndi Chin commented:

Final hand off from designs have been completed. Created new ticket (linked) to follow up on the target feature and triggers since those are still TBD.

Brainstorming discussions on the target feature / triggers:

Some brainstorming of features for consideration:

• New tab: a good candidate. Simple and also parallels the new tab microsurveys on desktop
• (Form) Autofill: a good candidate as well. Relatively simple to define but also more complex than new tab.

I believe that we have triggers in place already that we can use for these on Mobile.Others that will likely be deprioritized for now:

• Profiles: not built yet so not an option right now
• Search and Suggest: a bit too tricky in terms of defining triggers and targets and we probably need involvement from search engineers

We are thinking that we start with form autofill as a base use case and also have new tab in mind as a second choice for the time being. But let me confirm this with @Rosanne ( https://mozilla.slack.com/team/UC2CPCVUG ) and @kamyar ( https://mozilla.slack.com/team/U4DGU7360 ) first, as we want to align to our OKR 3.3 CSAT plan as well. Exact triggers can be defined once we finalize this choice.