On 19 Feb 2014, at 03:44, Fred Lin <[email protected]> wrote: > It's great to address the burden of develop webapp. > Though gaia developer may not recognize this issue, it's quite different > between gaia and webapp development at this stage. > I'd like to share some of my investigation so we can have more information to > improve webapp development experience. > > > 1. The marketplace that web user will front with: > > Marketplace can't filter the unsupported app to user. > > User have limit knowledge about what Firefox OS cross-platform compatibility > means, and confused when they can see the app but can't use it in desktop(if > develop does not select to support that platform) (It might because we didn't > communicate to community about Firefox Runtime yet?) > . > http://stackoverflow.com/questions/21473666/example-of-firefox-os-cross-platform-compatibility > > > 2. The Marketplace that webapp developer front with: > > My friend has good knowledge about gaia development, and tried to use > requireJS(alameda) and gUM audio for packaged app but encounter CSP issue > while submitting to the marketplace (solution: precompile by r.js to pass the > policy), and then he encounter the issue that the reviewer can't test gUM > audio in certain devices (which is a device specific bug). The poor > experience lead him cancel the app submission to marketplace. As a new mobile > platform, we can see how we lose this kind of capable developer, which is > eager to develop cutting edge webapp that help us differentiate from other > competitors. > > > 3. Marketplace app with cutting edge or platform specific features: > > As a platform developer, we also encounter issues that we can't submit > homescreen or keyboard IME webapp to marketplace for people who can use > nightly version of FirefoxOS device, and find out the problem early. >
thanks for the notes. I’ve added these to my plans. > > 4. The MDN gUM document confuse the webapp developer: > > For webRTC support, most developer will reference to > https://developer.mozilla.org/en-US/docs/Web/API/Navigator.getUserMedia > > but they'll neglect the need of add permissions `"audio-capture": {}` in > manifest.webapp for FirefoxOS device > https://developer.mozilla.org/en-US/Apps/Reference > > It does not provide information by version (FxOS 1.2+ for gUM audio, 1.4+ for > video) as well. > Maybe we should come out a rule to keep these info up-to-date. I’ve updated these locations with the information. For example, see https://developer.mozilla.org/en-US/docs/Web/API/Navigator.getUserMedia#Permissions It is a hard problem to keep all this information up to date, but we are working on it. Your input is appreciated. One thing - shouldn’t “audio-capture” be “media-capture”, given that it handles audio and video? _______________________________________________ dev-webapps mailing list [email protected] https://lists.mozilla.org/listinfo/dev-webapps
