Spike: Assess confidence in ability for Lockwise to capture new and update existing accounts created within Fenix

[changecourse]

We need to ensure that we have confidence about capture for new and updating existing credentials within Fenix via Lockwise

Specifically, that a Lockwise modal will show up in each and every instance where someone creates a new account (in parity, or better than Fenix) as well as instances where an account needs to be updated (new password)

This ensures that the work the Fenix team is doing enables Lockwise to handle login management, rather than a reduced experience with our app.

Definition of done

see comments below

@eliserichards yes, likely we'll need to create a spreadsheet of top sites, with use cases for both creating new and updating existing accounts, and compare the reliability of capture between Fenix and Lockwise.

[eliserichards]

Is this meant to be an engineering task? Not sure what the definition of "done" here would be 🤔

[sandysage]

@eliserichards I think this is intended to be a follow up to a discussion had with @jhugman about leveraging Firefox's fill/capture heuristics in toolkit in Lockwise. I think the idea here is to determine if that really is feasible, and if so, scope out the work to augment our fill/capture abilities with the Firefox heuristics.

[changecourse]

@eliserichards yes, likely we'll need to create a spreadsheet of top sites, with use cases for both creating new and updating existing accounts, and compare the reliability of capture between Fenix and Lockwise.

[eliserichards]

Spreadsheet: https://docs.google.com/spreadsheets/d/1cOHLE9-GxppEQ0jLURa945WBnryMDA7a6yBn3ogMe8c/edit#gid=0

[eliserichards]

Autofill in fenix is available in nightly currently (hoping to land in the next release).