Minutes from Sept 19 Mobile Tech Leads meeting
rfkelly at mozilla.com
Thu Sep 20 23:30:31 UTC 2018
On Fri, 21 Sep 2018 at 09:09, Stefan Arentz <sarentz at mozilla.com> wrote:
> “The application-services team is trying to plan for a future on iOS;
> immediate next action is to get some iOS build advice from the Firefox for
> iOS team”
> This is really exciting. But I am curious why that is a priority over
> Android (Fenix) work.
> Although Firefox for iOS works now, with some constraints, it would
> definitely benefit from an improved services implementation.
> But right now should we not spend that energy on Android?
There's a lot more nuance in the detailed meeting minutes, but you're
absolutely right that the Android work needs to (and does!) take priority
Basically, we would like to start having some high-level conversations
about what an iOS equivalent to android-components might look like. Not
necessarily to start on it with any urgency, but to ensure that we don't
make short-term decisions that make such an effort harder for ourselves
down the line.
I expect the first concrete work on that front to be porting the logins-api
component to iOS, so that it can be used in Lockbox for iOS, which will
happen sometime in 2019.
Does it seem a little saner when framed in that way? :-)
On Thu, Sep 20, 2018 at 5:39 PM Nicholas Alexander <nalexander at mozilla.com>
>> Hi folks,
>> We held a Mobile Tech Leads meeting on Tuesday (NA/AU timezones). The
>> was quite a bit broader than previous meetings:
>> - The Lockbox team has kicked off work on Lockbox for Android \o/
>> Lots of open questions but some early success consuming the initial Sync
>> 1.5 logins API.
>> - The application-services team is trying to plan for a future on
>> iOS; immediate next action is to get some iOS build advice from the Firefox
>> for iOS team.
>> - The "history" Rust component is top priority for Q4 for
>> application-services. Figuring out the end-to-end integration story is
>> important; consensus is that integration starts in the sample browser Apps
>> but the sooner we can get in front of real users, the happier everybody
>> will be.
>> - Build and deploy pipeline for single unified ("megazorded") native
>> code libraries is a priority for Q4, targeting the Lockbox for Android
>> initial release. nalexander will be driving that work in this meta
>> ticket <https://github.com/mozilla/application-services/issues/263>.
>> android-components mailing list
>> android-components at lists.mozilla.org
> Dev-fxacct mailing list
> Dev-fxacct at mozilla.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Sync-dev