On 2013-09-06, at 1:48 PM, Julien Wajsberg <[email protected]> wrote:
> Le 05/09/2013 19:46, Fabrice Desre a écrit : >> 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. >> >> > > I was going to say this, thanks Fabrice. > > On the Open Web we always do graceful degradation (or progressive > enhancement), and using our Web API should not be different, except for > very specific apps. It might even make sense to implement/facilitate the creation of polyfills for those platforms where some of those calls aren't ready yet (e.g. getUserMedia for webcam input, etc.) --da _______________________________________________ dev-webapps mailing list [email protected] https://lists.mozilla.org/listinfo/dev-webapps
