Not that it's a very high bar to beat, but there will definitely be better support for Flame than ZTE Open. + Asa, who might have details to share.
-----Original Message----- From: "M. Edward (Ed) Borasky" <[email protected]> Date: Wednesday, April 30, 2014 at 5:27 PM To: <[email protected]> Subject: Re: Baseline target platform >Lisa, I hope those of us who choose to buy a "Flame" on the open market, >since we're not eligible for a Mozilla-supplied device, will not suffer >from the same dismal fate as those of us who bought a ZTE Open. I just the >other day managed to get a home-compiled build of 1.4 flashed to my open, >and since I got the device in September of last year it's been nothing but >trouble. If there was a partnership between ZTE and Mozilla to support >developers, I didn't see *any* evidence of it. > >Is there in fact a plan, strategy, web site, whatever for supporting >"Flame" devices for those who plunk down the cash for one? > > >On Tue, Apr 29, 2014 at 2:54 PM, Lisa Brewster ><[email protected]>wrote: > >> Pablo, this is a very articulate outline of our current areas of >> fragmentation. Thanks for writing it up! >> >> I feel some of your same pain, here's what I can add from an app review >> perspective. >> >> By default, today we test apps on v1.1, because that's the latest >> commercially available version. During submission, developers have the >> ability to specify that certain api's are required, in which case the >>app >> will not be shown to users whose devices don't support those api's. Api >> support will vary by hardware capabilities and Firefox OS version. >> >> Feature detection is the right approach here philosophically, but in >> practice it causes edge cases where not all features can be detected >>yet, >> or sometimes there are platform bugs that cause the app to break on >> earlier versions of Firefox OS. When this happens, we ask that the >> developer specify the min version and requirements in the app >>description. >> We'll review on up to v1.3 on a Keon. >> >> Devices running v1.3 will be released in the near future, which puts us >>in >> a complicated spot. Standardizing on the Flame reference device is the >> answer here, but will have tradeoffs ensuring app compatibility for >>users >> who can't update. >> >> -- >> Kind regards, >> Lisa Brewster [:adora] >> Marketplace App Review Manager >> >> >> >> -----Original Message----- >> From: Pablo Brasero Moreno <[email protected]> >> Date: Tuesday, April 29, 2014 at 4:44 PM >> To: <[email protected]> >> Subject: Re: Baseline target platform >> >> >On 29 April 2014 19:02, Fabricio C Zuardi <[email protected]> >>wrote: >> > >> >> FxOS 1.1 is our personal IE6 here in Brazil alreadyŠ >> >> >> > >> >Oh God... >> > >> >What target do people develop for then? 1.1 or 1.0.1? >> > >> >According to MDN both versions are based on Gecko 18, although 1.1 has >> >some >> >additional APIs, which I take are the ones listed in the release >>notes[1]. >> > >> >Assuming I don't need any of these APIs, is there a reason to use >>1.0.1 as >> >my baseline, or can I stay with 1.1? >> > >> >Thank you! >> > >> >[1] https://www.mozilla.org/en-US/firefox/os/notes/1.1#webapis >> >-- >> >Pablo Brasero Moreno >> >[email protected] >> >_______________________________________________ >> >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 >> > > > >-- >Twitter: http://twitter.com/znmeb; Computational Journalism on a Stick >http://j.mp/CompJournoStickOverview > >My poltergeist can beat up your zeitgeist. >_______________________________________________ >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
