I dont think its necessarily about removing packaged apps completely, they do have their advantages and building out the ability for web application run in a peer to peer fashion is a good thing to do.
However I think Naoki's questions illustrate the point really well > An example is emergency calling. If the dialer was fully hosted without a wifi connection, how do you make a call? Web applications can and should be able to work fully offline and be able to perform just as well as packaged application, we currently arent doing a lot to make the offline web a better place since we pretty much gave up and used packaged apps, I do hope service workers improves the situation. At every point we are building functionality where people need to do custom firefox packaging for it to be used, we should look at figuring out how we will make it available to web content On 30 January 2015 at 18:54, Naoki Hirata <[email protected]> wrote: > I have to agree with Kevin. My biggest concerns are for performance, > offline cases, and issues with caching with full hosted apps. > > An example is emergency calling. If the dialer was fully hosted without a > wifi connection, how do you make a call? This scenario would require you > to have a SIM w/ a data plan in order to access the app that is needed just > to go through the ril when it should just be able to access the ril > directly without having to have a SIM. > > Even having partial packaged apps could help in this case. > > Regards, > Naoki > > On Jan 30, 2015, at 10:40 AM, Kevin Grandon <[email protected]> wrote: > > Do we really want to fully deprecate packaged apps? I think making hosted > apps and packaged apps equals is a big win, but I'm not sure if fully > deprecating packaged apps is a good idea. > > There are many developers who like the ability to not run and maintain a > server. It's simply less work and overhead for them to throw their code up > on a marketplace, and not have to worry about a monthly server cost, or a > server going down. > > Best, > Kevin > > On Fri, Jan 30, 2015 at 10:28 AM, Benjamin Francis <[email protected]> > wrote: > >> On 30 January 2015 at 18:17, Andrew Overholt <[email protected]> >> wrote: >> >> > >> > Most of the frequently used permissions do not require the use of a >> >> packaged app, but the second most used permission is systemXHR which >> does. >> >> Apparently most developers are only using this because they created a >> >> packaged app purely for its offline properties, then found they needed >> >> systemXHR to talk to their own server. Which is silly. I hope Service >> >> Workers will help with this situation. >> >> >> > >> > Can you elaborate on this a bit? Why do developers need to use >> systemXHR >> > with their packaged app? How do you envision Service Workers helping in >> > this case? >> > >> >> As I understand it... >> >> Developers create a packaged app because it's currently the most effective >> way to make their app work offline. A packaged app has a synthetic origin >> which will always be cross-origin from the developer's own web server. >> They >> use SystemXHR to allow their packaged app to use remote resources from >> their web server, rather than set up CORS because that's more difficult. >> >> If they instead used Service Workers to make their app work offline, they >> wouldn't have a weird synthetic origin and therefore wouldn't need to use >> systemXHR because their app would be same-origin with their web server. >> _______________________________________________ >> dev-webapps mailing list >> [email protected] >> https://lists.mozilla.org/listinfo/dev-webapps >> > > _______________________________________________ > dev-gaia mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-gaia > > > > _______________________________________________ > dev-gaia mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-gaia > > _______________________________________________ dev-webapps mailing list [email protected] https://lists.mozilla.org/listinfo/dev-webapps
