I've been thinking a lot about this thread in the context of Ari's talk at the All Hands meeting yesterday. We're working on an OS that has to run on smartphones, smart tv's and other form factors tbd. Ari asked us to focus on portability, and that obviously will be key to our ability to run on different form factors.
I had something of an epiphany today: In the future, teams inside and outside of Mozilla will build devices that run FirefoxOS and will create products that provide true user value and delight. At this moment we don't know what those products will be. So for core FirefoxOS developers, our users are these future product development teams. We need to be building an OS that is so fast and flexible, so portable and performant that product developers will feel delight using our platform. With that in mind, I'd like to suggest that we'd be better served by focusing on web components than by working on NGA. Converting our building blocks to web components and then refactoring our apps to use those components and to be based on higher-level web components will give us much of the modularity and portability that we're seeking from NGA, but at the same time, it will also create a high-quality library of reusable UI components that third party app authors (including those who are embedding FirefoxOS in new products) can use to more easily create apps. David On Fri, Nov 13, 2015 at 9:40 AM, Wilfred Mathanaraj <[email protected]> wrote: > Hi all, > > Given the Music app splitting we have done in time for 2.5 we want to move > ahead - I think it makes sense to be executed in a “train model” fashion. > We should start from the top of the list and work through the list. > > When I say splitting of the apps, we are looking for the following > activities to be done: > 1. FE/BE split > 2. Split views > 3. Page transition > > Why did I choose the priority below? - for now we have 2 products that we > work on: smartphone and TV, but moving forward we need to investigate what > are the products that make sense for us and when we enter the connected > devices market 3rd party developers need to be able to develop differing > views for our core apps. > > With this is mind we went through some exercise to define a priority for > the apps to be ported to the updated architecture. > > Priority list: > > - *Settings* - this is a key app for any product mozilla may be > planning to release; different apps will have different needs to display > information to the user in the settings > - *Camera *- again a key app for a lot of the modern devices > - *Contacts* - everyone wants to have contacts on their devices - but > they need different level of information - creating differing views is > going to key here > - *Calendar* - as with contacts its critical to have differing views > but not as high priority as contacts > - *Gallery* - another core app that every connected device may need > to have > - *E-mail* - typing emails on smaller devices will be a problem and > therefore creating readable email view may be needed for some connected > deviceds > - *Calculator *- table stake app > - *Clock *- table stake app > - *Browser *- one of core mozilla apps but a table stake app for some > of the connected devices > > > Some of the engineering teams, who have already worked on this split, will > be reaching out in smaller teams to discuss best practices and quick wins > for this activity. > > BR > Wilfred > > --- > FxOS Product Management > Mozilla Corp., UK > > > > > > _______________________________________________ > 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
