Splitting out the front and backend of Settings might allow us to re-think the FTE. The first, non-tutorial part of the (phone) FTU app is basically another front-end on settings and I've long wanted to reduce the amount of duplicated code involved.
/Sam On Tue, Nov 17, 2015 at 1:59 AM, Joe Cheng <[email protected]> wrote: > with regard to TV, merging the system app definitely is something we need > to do (being planned) and also the browser. > > some other apps (with obvious front end work) would also need to consider > for TVs are > > - Settings > - Software keyboard > - Media apps > - First time experience > > Will need to figure out the priorities for each of those and tackle them > one by one > > Re, > Joe Cheng > —————————— > Mozilla Corp. > [email protected] > > > On Tue, Nov 17, 2015 at 2:01 AM, Benjamin Francis <[email protected]> > wrote: > >> On 16 November 2015 at 09:17, David Scravaglieri < >> [email protected]> wrote: >> >>> Just to be clear. >>> >>> It’s well understood that Browser is not an app. But there is UI >>> involved when using the Browser. So, what I am asking for, is a status and >>> a specific plan for the Browser to be form factor agnostic and to not >>> duplicate code for every and each type of device. >>> >> >> FWIW on the browser item I'm not sure why we'd single out the browser >> chrome vs. any other part of the system UI like the status bar, task >> manager or notifications tray? As you say, the "browser" in Firefox OS is >> no longer an app, it's just one state of a window in the window manager. >> With the Alopex experience the browser stands to be even less like an app >> (there may not even be a browser icon on the homescreen). >> >> It's possible we could apply the front end/back end split to the search >> "app" as it stands, but it seems quite arbitrary to pick out the browser >> chrome part of the system UI. We need to take a more holistic look at how >> the whole of the system UI can be made more responsive to different form >> factors, and whether the new architecture for built-in apps has the same >> benefits when applied to the system UI (which I'm guessing probably won't >> use the new app format for the foreseeable future). >> >> Note that currently TV uses a completely separate browser app (which >> actually is a separate app from tv-system) and the same had been planned >> for the smart feature phone UI. We should probably address that >> inconsistency first and look at this as part of the wider proposed merger >> of the smartphone and TV system apps. >> >> Ben >> >> _______________________________________________ >> 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 > >
_______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
