I played a little with a homescreen built on polymer. https://github.com/Polymer/labs/tree/master/vulcanize (HTML Imports at build time) fixed all certified app CSP errors I encountered. The app isn't very demanding yet, but I haven't encountered any performance issues. Even with the magic shadow DOM polyfills and all.
On Fri, Sep 6, 2013 at 6:24 PM, Frederic Wenzel <[email protected]> wrote: > You got it right, that's exactly what our dev evangelists are saying. They > are some of the fiercest open web (not: Firefox os silo) advocates I know. > Cross-platform considerations are front and center to the story we're > writing for developers, and "use our powerful new apis when you have them, > do something sane otherwise" is a key part of it. > > Fred > > > > -- > Sent from my phone. Excuse my brevity. > > -------- Original message -------- > From: Fabrice Desre <[email protected]> > Date: 09/05/2013 10:48 (GMT-08:00) > To: Stefan Arentz <[email protected]> > Cc: Mark Giffin <[email protected]>,Julien Wajsberg < > [email protected]>,[email protected],Fred Wenzel < > [email protected]>,Bill Maggs <[email protected]>,apps < > [email protected]>,[email protected],Ben Francis > <[email protected]>,dev-gaia > <[email protected]> > Subject: Re: Introducing Brick: Web Components for Apps Development > > On 09/05/2013 10:42 AM, Stefan Arentz wrote: > > > > The problem is that we are sending out mixed messages. > > > > By saying ‘develop for the open web!’ we are basically saying, do not > create packaged apps and use the lowest common denominator when it comes to > cross-browser API availability. In practice that means: do not use Firefox > OS specific WebAPIs because then you are not developing for the open web. > At least not right now in the short term. > > > > On the other hand, we have plenty of presentation material and > documentation that says ‘Use our WebAPIs with which you can make your web > applications do the same awesome things that other (native) platforms > offer’. So that is the opposite. > > > > Personally I don’t think neither proposition is bad, and I think we need > the second to arrive at the open web. It is just not going to happen > overnight. So I think it is really important to not drive people in a > specific way of developing apps at this point. > > I really hope that our dev evangelists are not saying that, but rather > "make use of our new APIs and degrade gracefully when they are not > available". If this is not the message, we have a problem. > > Fabrice > -- > Fabrice Desré > b2g team > Mozilla Corporation > _______________________________________________ > dev-gaia mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-gaia > _______________________________________________ dev-webapps mailing list [email protected] https://lists.mozilla.org/listinfo/dev-webapps
