Some highlights from yesterday's very meaty Web Coordination meeting. The
first 30 minutes were spent discussing the issues most important to Ryan
Feeley (UX) and Alex Davis (PM), the second general dev.

First - *NO FxA Web Coordination meetings on Thursday!*

*UX/PM*

   - A lot of work continues on the device list, on both front and back
   ends.
      - The device should now be correctly sorted [1].
      - A new option, "duplicate device" [2], is going to be added to the
      list of reasons a user disconnects a device. We have seen a lot of
      duplicate devices through our own testing, and hope this will reduce the
      number of users that click on "rather not say". Phil aks "should
we add an
      `Other...` option too?"
      - The current "reasons for disconnecting" is going to be converted
      from a dropdown list to a list of radio buttons.
      - A lot of backend work is going into displaying the correct device
      type. UA parsing using a generic library has not worked as well
as we want
      it to because Firefox for Android and iOS send custom user-agent strings.
      - We still see a large number of duplicate devices and are trying to
      track down why. Many of these may be due to password changes and resets.
   - Email confirmation flow phase 1 - "Connect another device"
      - The purpose of this phase is to help users who sign up on device A
      and verify on device B get device B connected, either via signing in to
      Firefox if they opened the verification link in Firefox, or installing
      Firefox on Android/iOS.
      - A demo of the front end was given yesterday, most of the UI work is
      in good shape. There are still some rough edges to iron out, and
we need to
      hook up to Able and metrics.
      - Vijay is working on a Firefox for iOS patch to help us with "deep
      linking" so that when a user installs Firefox on iOS after
clicking on the
      iTunes store button in the verification page, Firefox for iOS
automatically
      opens FxA and pre-fills the email. [3]
      - We need to find out who to talk to about similar functionality in
         Android.
      - There is an open question about how to handle users that open the
      verification link in Firefox for iOS. Since users cannot override the
      default browser in iOS (but they CAN in the Outlook app), this isn't the
      highest priority.
   - Email confirmation flow phase 2 - Send an SMS
      - Alex is putting together the feature doc at [4].
      - We need to decide which SMS provider to use, options so far are
      Salesforce, Amazon and Twilio. Salesforce's SMS API does not appear to
      allow for dynamic content so we may not be able to use it. If we
want to go
      through Amazon or Twilio, we will need to loop in legal for approval.

*General Dev*

   - We are seeing database timeouts on fxa-dev which is causing Circle CI
   test failures. [5][6]
   - If a database request times out, the auth server currently returns a
      500 and logs an ugly error that implies something went wrong with l10n. I
      wonder if the auth server should instead return a 503 and log which DB
      request failed.
   - Now that the auth-server takes care of sending emails to unverified
   users on /account/login, Vijay is removing the "sendIfUnverified" logic
   from the content server. It's no longer needed. [7]
   - Phil is working on a PR to drop invalid utm_ params on the ground. [8]
   - We have decided the "show-password" experiment is no longer needed. It
   should be enabled for everyone.
   - We need a way to report AB test decisions to re:dash so that we can
   bucket users appropriately. [9][10]
   - Vlad is adding functional tests to ensure SRI is enabled and that all
   expected resources contain valid SRI attributes. [11]

That's a meeting to be proud of!
Shane

[1] - https://github.com/mozilla/fxa-content-server/pull/4430
[2] - https://github.com/mozilla/fxa-content-server/issues/4429
[3] - https://bugzilla.mozilla.org/show_bug.cgi?id=1317580
[4] -
https://docs.google.com/document/d/133_Cu0TlWQZIw-ihMH1s-U_80I12MXZcvHQEuFhWbPg
[5] - https://github.com/mozilla/fxa-auth-server/issues/1553
[6] - https://github.com/mozilla/fxa-dev/issues/290
[7] - https://github.com/mozilla/fxa-content-server/pull/4424
[8] - https://github.com/mozilla/fxa-content-server/pull/4431
[9] - https://github.com/mozilla/fxa-content-server/issues/4290
[10] - https://waffle.io/mozilla/fxa/cards/5804f8fc7b5d9f6401eeb849
[11] - https://github.com/mozilla/fxa-content-server/pull/4432
_______________________________________________
Dev-fxacct mailing list
[email protected]
https://mail.mozilla.org/listinfo/dev-fxacct

Reply via email to