This is a different use case, but could be compelling to support our customization/hackability story: The promise of web components also includes enabling third parties/devs to change the look and feel of the whole OS and offer those changes to others, as well. Traditionally on Android that hasn't been so easy and customizations are often limited to the homescreen only. Ideally the solution enables this use case.
Peter On Wed, Oct 28, 2015 at 2:03 PM, Wilfred Mathanaraj <[email protected]> wrote: > Having some common components it makes life easier for QA to review how > drop downs the usability results are marked as gating or not. but generally > email is here to keep on adding questions and concerns and ideally find a > solution that works for everyone! > > Wilfred > --- > FxOS Product Management > Mozilla Corp., UK > > > > > On 28 Oct 2015, at 10:30, Etienne Segonzac <[email protected]> wrote: > > > On Wed, Oct 28, 2015 at 9:33 AM, Wilfred Mathanaraj <[email protected]> > wrote: > >> In the past we had a proposal to use web-components to bring uniformity >> to the UX on FxOS - we did a partial implementation of this and it has left >> our UX with an “unfinished” look and feel. >> Moving forward we want to have a very uniform UX across all our core >> apps. We also want to make this uniform experience available to >> contributors. >> > > The "uniformity" part is very clear. We want to share more than just > style. Components are a great way to achieve this. > Glad to see this is our top goal. > > >> Having common components to achieve this will also help with the >> following: >> >> 1. UX to easily manage UX changes >> > > Somewhat yes... But I hope we'll be "extra concrete" when discussing this > part, lots of misunderstandings around this. > > WebComponents are a great way to "package". They don't solve the > "deployment" use cases by themselves. > If the goal is "the UX makes only one change and it propagates across Gaia > (and contributors app?)" it's a build system discussion more than a > frontend discussion :) > > >> 2. Engineering to reduce code size by using these common components >> > > To reduce app-specific code size yes. > > >> 3. QA to reduce their testing >> > > How? Not sure how this is related. > > > > _______________________________________________ > dev-fxos mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-fxos > >
_______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
