Open Web Apps are died?

Check that link: http://www.ghacks.net/2016/01/09/mozilla-to-remove-webrt-from-firefox/

The news is very sad for me, i have a talk about that http://mte90.github.io/Talk-FF-OWA and with the remove of that feature we cannot fight the chrome apps and other implementations.
The marketplace have the roles as a marketplace only for Firefox OS.
While for the http://www.w3.org/2008/webapps/manifest/ W3C Manifest there are no news for Firefox support.

1 Like

Support for the W3C Web Manifest specification has been added to Gecko (modulo some bits that are still underway), and thus all products in which Gecko ships, including Firefox Desktop and Fennec, over in bug 997779.

Firefox Desktop will use icons from W3C manifests on the New Tab page per bug 1186134.

Fennec support for progressive apps generally is tracked in meta-bug 1212648, which depends on a variety of manifest-related issues.

What other news about Firefox support for the W3C manifest would you like?

Any news on MDN or in hacks.mozilla.org with example for use it will be not bad.
Actually there are no official news about that support in Firefox.

For the Mozilla marketplace there any info for that?

Web Manifest is documented, with an example, on MDN at /en-US/docs/Web/Manifest. The Browser Compatibility table on that page is out-of-date, however, as it doesn’t list the version of Firefox that supports the feature.

And I don’t think there has been a Hacks blog post about it. That’s a good idea; I’ll suggest it to the WADI team!

I’m not sure what constitutes “official” news in this case, but note that the WADI team is developing a “platform status” website to document platform support for emerging web APIs like Web Manifest. The code for that website is on GitHub at mozilla/platatus, and once it’s released, it’ll be an authoritative source of information like this.

[quote=“Mte90, post:1, topic:6476, full:true”]Check that link: http://www.ghacks.net/2016/01/09/mozilla-to-remove-webrt-from-firefox/
The news is very sad for me, i have a talk about that http://mte90.github.io/Talk-FF-OWA and with the remove of that feature we cannot fight the chrome apps and other implementations.[/quote]
For me it’s very sad too …
That was the way I motivate friends to install Firefox on their Android device, with install Firefox to install an app I developed or an app of the marketplace.
On the tablet of my wife, I can’t install Firefox OS, but there is Firefox and all the apps on the screen of the tablet home are webRT app, so she use only Firefox app on her tablet, and if webRT disappear … I couldn’t blame her if she took android ( CyanogenMod :wink: ) alternatives … and my apps too … Or I’ll need to develop in Cordova … that’s a shame …
I developed some apps for enterprise that they used internally ( without marketplace) and I negotiate with them to developed it with Firefox so with webRT, and then they have Firefox and they use it … Without webRT, they won’t agree launch Firefox to launch their app. So they won’t install Firefox and they won’t use it …
I don’t know what is the worst … maybe that I’ll have to developed with Cordova and the end of a platform for apps on Linux, Windows, Mac, Android/CM, Firefox OS (and I wished iOS) …

Now there is an official news.

Is already online https://platatus.herokuapp.com/

Originally, you asked for “official news” about support for the W3C manifest in Firefox. But here the “official news” you reference is about the disabling of the desktop/Android runtimes, which I’d already posted to the firefox-dev discussion forum.

The mailing list in the past established that is not the best place to find an official news confirmed.

A simple article that show the new standard can be found here: https://medium.com/@franciov/how-to-make-your-web-app-installable-8b71571605e#.pkj1tsm6v

I hope to see the standard in Firefox in the new release soon.

I’m not sure what you mean by this, but I’m the module owner for the desktop runtime module, I’m a relevant peer for the Fennec module, I made the decision to disable both runtimes, and I announced that decision in this message to the firefox-dev mailing list. That is the only “official” announcement about the future of the runtimes.

Fantastic, for the mailing list recently with Firefox OS has not established the best way for official and confirmed news.
In that case now is different, I’ve missed that you are the module owner.

I actually got to know the decision from your mail in the mailing list.
And I guess going forward Progressive web apps are going to take the place of these, if I am not wrong.

Progressive Web Apps do address some of the shortcomings of web apps relative to native apps, especially on mobile platforms. In particular, they provide a more robust API for offlining an app (Service Workers), which provides the reliability benefit of packaging; they introduce push notifications (Web Push), which are one of the most popular native APIs on mobile platforms; and they add high-quality metadata (Web Manifest), which browsers can use to make an app look and feel more native.

But they don’t address other shortcomings. In particular, they don’t get any additional access to powerful (and dangerous) APIs like TCP Socket. So Progressive Web Apps aren’t a complete replacement for Open Web Apps.

Over in dev-webapps, I’ve started a thread to discuss alternatives to Open Web Apps on desktop and Android. Please contribute your insight in that thread!