On 19 Feb 2014, at 11:41, Andrew Williamson <[email protected]> wrote:
> On 19/02/2014 03:44, Fred Lin 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 > > 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 am intending to add better documentation covering web runtime very soon, with more information to hopefully clear this up a bit. I agree it’s a problem, form both the web dev and mobile dev side. > >> 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 can’t tone down CSP errors/warnings, but we can educate people on what they mean, and how to work around them. Better CSP docs is also on my to do list. > >> 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) > >> 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. > >> 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. > > agree 100% here. > >> regards >> -- >> Fred Lin >> >> >> >> ----- 原始郵件 ----- >> 寄件人: "Daniel Buchner" <[email protected]> >> 收件人: [email protected] >> 副本: [email protected], "apps" <[email protected]>, >> "engagement-developers" <[email protected]> >> 寄件箱: 2014年2 月19日, 星期三 上午 8:46:23 >> 標題: Re: Strong recommendations to help developers make better apps >> >> Another section of recommendations (which Fred may or may not have >> inferred) are vetted services developers utilize in creating and managing >> their apps. This area of recommendations includes the nobackend solution >> space and targeted services developers consume/integrate to accomplish >> specific tasks (think: YQL, Komodo Labs, social login, comment systems, etc) >> >> We look forward to creating a robust, end-to-end, recommendation playground >> that provides developers with a friendly, trusted place to explore and >> select solutions that work for them. >> >> - Daniel >> >> On Tue, Feb 18, 2014 at 3:52 PM, Fred Wenzel <[email protected]> wrote: >> >>> Hello everyone! >>> >>> For developers, building apps on the Web platform can pose a >>> fragmentation problem: For every development concern, there are often a >>> dozen or more possible options to consider, without clear pros or cons. >>> Web developers can feel intimidated not simply by their choices, but by >>> how _similar_ their choices are. >>> >>> While this openness and community is a virtue, it leads to "choice >>> paralysis" and the wrong impression that the Web is a harder platform to >>> develop for than more restrictive alternatives. >>> >>> However, by making strong, informed recommendations to developers, we >>> can help turn the variety of development tools available on the Web from >>> a daunting proposition into an empowering one. >>> >>> A great example of this is the significant attention[1] tofumatt's >>> localForage[2] project has received. It provides a cross-platform, >>> asynchronous storage library that "just works". With its straightforward >>> API, it _removes_ an entire monotonous development choice for >>> developers. The community honored this drastic simplification with >>> almost 2000(!) "stars" on github in just a few days. >>> >>> Furthermore, we have a responsibility to our developers to ensure that >>> certain frameworks, libraries, etc., have been tested and work well with >>> our own and (eventually) other target platforms. >>> >>> Our developer-facing groups (Apps Engineering, Developer Relations and >>> Developer Tools in particular) are collaborating to expand this effort >>> systematically across the various parts of the development experience. >>> >>> >>> Some projects that are already in flight include: >>> >>> - web-components-based (featuring Brick) app templates that work out of >>> the box >>> - additional such components for hard, yet common problems such as >>> scrolling of large lists >>> - Mozilla-endorsed framework and tool chain for apps >>> - using the Firefox App Manager to start a new project from a template >>> and allow developing on it right then and there, no other tools needed >>> - submitting an app straight to the Marketplace from the App Manager >>> - an updated "MDN Apps Zone" experience focusing on developer concerns >>> and our materials and recommendations for each case >>> >>> >>> If this whetted your appetite, great! 2014 is an exciting year to be an >>> apps developer! All this and more is coming--step by step--to a >>> developer experience near you. >>> >>> If you have any question or comments, speak up, or step by #apps on IRC! >>> >>> Thanks, >>> Fred Wenzel >>> >>> >>> [1] >>> https://hacks.mozilla.org/2014/02/localforage-offline-storage-improved/ >>> [2] https://github.com/mozilla/localForage >>> >> _______________________________________________ >> dev-webapps mailing list >> [email protected] >> https://lists.mozilla.org/listinfo/dev-webapps >> > _______________________________________________ dev-webapps mailing list [email protected] https://lists.mozilla.org/listinfo/dev-webapps
