> 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
> Where do you think the problem lies here? That developers don't > understand the platform selection? Or that users don't understand why > apps are shown on Desktop they can't install? I think its more about the usage flow design. Once we have Firefox Account and able to install app to device from desktop just like apple or google, the problem might be mitigated. But current flow confuse the desktop user (and tablet and more..). > 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), > I agree its a problem, but what can we do about CSP errors? We should follow CSP rules, but also need to address howto use these popular libraries for FirefoxOS pacakaged app in MDN. Which could align to the `Strong recommendations` section. > 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. > Is it a known bug? What part of the poor experience can we improve? (zero bugs in every 3rd party manufactured device being an impossibility) As a platform, it's our responsibility to make sure the device should fit some compliance rule, or the feature detection is collapsed, which make the impression to user that web is not reliable. > 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. > Marketplace can support apps like keyboards, as long as there is a > feature-bucket to filter out the app from the other 99% of users who > aren't on Nightly FxOS builds, and of course those features are > detectable on the client side. With a consumer orientated Marketplace, > there are always going to be issues for platform developers trying to > use it. We could have a staging marketplace that developer can test their app with more loose rules. Maybe just for devices that enabled the developer settings, so it create the fense to avoid consumers trapping there occasionally. _______________________________________________ dev-webapps mailing list [email protected] https://lists.mozilla.org/listinfo/dev-webapps
