Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror
×
Apple

'Apple's Refusal To Support Progressive Web Apps is a Detriment To Future of the Web' (medium.com) 302

From a blog post: Progressive Web Applications (PWAs) are one of the most exciting and innovative things happening in web development right now. PWAs enable you to use JavaScript to create a "Service Worker", which gives you all sorts of great features that you'd normally associate with native apps, like push notifications, offline support, and app loading screens -- but on the web! Awesome. Except for is one major problem -- While Google has embraced the technology and added support for it in Chrome for Android, Apple has abstained from adding support to mobile Safari. All they've done is say that it is "Under Consideration." Seemingly no discussion about it whatsoever.
This discussion has been archived. No new comments can be posted.

'Apple's Refusal To Support Progressive Web Apps is a Detriment To Future of the Web'

Comments Filter:
  • DO NOT WANT!!!! (Score:4, Insightful)

    by Anonymous Coward on Thursday July 27, 2017 @02:09PM (#54893001)

    who the shit would want this?

    • by Anonymous Coward on Thursday July 27, 2017 @02:18PM (#54893083)

      Nobody. Nobody wants anything "push". Everybody hates loading screens. If sw even have a splash screen, it is TOO SLOW.

      Ad people may want push, that drives this. Too bad for them, I turn js off.

    • Indeed. If I want notifications and whatthefucknot, I can install the app. If I am browsing your service in web browser, just take the fucking hint already.

  • Loading screens. (Score:5, Interesting)

    by tietokone-olmi ( 26595 ) on Thursday July 27, 2017 @02:10PM (#54893005)

    It's 2017 and programs still have a "loading screen".

    Idiots, all of you.

    • by Anonymous Coward on Thursday July 27, 2017 @02:15PM (#54893055)

      Dude, apple needs to support this kick ass new technology so that websites can have splash screens. It's the least they can do after they killed off flash, the previous kick ass technology enabling the awesomeness of splash pages!

    • Re: (Score:3, Insightful)

      by Anonymous Coward

      Compare: modern application startup time on windows 10 (or 7 if you prefer) 4Ghz processor with SSD and DDR4 memory, vs similar application on windows 95 era pentium 133 with SDRAM and an IDE hard drive.

      How the fuck did we get here 2017?

      • The correct answer is probably a mix of "high level languages", "OOP", "libraries" and "frameworks".

        • by xanthos ( 73578 )
          Add to that "Web/App/Content Developers" instead of Programmers.

          Programmers program computers. The other group circle jerks.
          • correct, if by "circle jerks", you mean "makes money hand-over-fist giving people what they want".

      • by Anonymous Coward on Thursday July 27, 2017 @03:18PM (#54893589)

        Bad or lazy developers and designers adding more "features", relying on frameworks on top of frameworks, ignoring critical thinking and not culling what is not needed.

        That is how we got here.

        You can witness it firsthand year by year on the internet archive by looking at popular web pages. They start with handcrafted html that is byte-level sensitive. Then automated generators and css that add no functionality, on to plugins, php where it isn't needed, endless javascript. Now even the most basic websites need to load scripts from half a dozen domains and relies on layered frameworks. Not to mention the endless threat vectors this brings.

        Web pages that were once less that 1KB sans media are now over 10MB and have dozens of single points of failure with no discernible increase in usability or features. Even slashdot became this way.

        Go to slashdot.org, it tries to load from:
        fsdn.com
        pro-market.net
        slashdotmedia.com
        stacksocial.com
        janrain.com
        taboola.com
        truste.com
        multiple subdomains of cloudfront.net
        ml314.com
        rpxnow.com
        google-analytics.com
        crsspxl.com

        There are one or more scripts running from each, I don't know how many, I block them. Just to get slashdot to render properly 2,524 CSS rules must be loaded. Why is there a 123KB "app.css" file of 1204 rules that must load?

        What a mess. We ought to be following best-practices, saying "No" more often to marketing, vendors, pr, sales, and the army of people in IT that don't have the talent need to get the boot.

        • Of all that crap, fsdn.com is the only one that's not strictly harmful. These days, "deny by default" is not only a security measure, it also means less work telling ads from non-ads.

        • that's not laziness. that's how "free" services get funded nowadays. most of that has nothing to do with rendering the actual content; it's to farm statistics and show ads, which is where the vast majority of the money comes from.

        • by Rakarra ( 112805 )

          We ought to be following best-practices, saying "No" more often to marketing, vendors, pr, sales

          They're the ones who get to say 'no' and show you the door, because they're the ones who pony up the money that it takes to do anything.

      • Re:Loading screens. (Score:5, Informative)

        by UnknownSoldier ( 67820 ) on Thursday July 27, 2017 @03:27PM (#54893683)

        Jon Blow talks about this -- Why does it take Photoshop about 7 seconds to display your image on a modern computer???

        Jonathan Blow "Making Game Programming Less Terrible" Talk at Reboot Develop 2017 [youtu.be]

        > How the fuck did we get here 2017?

        Lazy programmers who don't giving a fuck about the user experience. i.e. Bloated C++ and OOP as opposed to DOD (Data Orientated Design.)

        • sure, user experience is great, as long as it doesn't add even 1% overhead to the timetable or budget. it's provably more efficient (i.e. more short-term profit) to just shovel shit faster than the other guy.

      • My hypothesis is that the so-called Java Generation was taught from their individual beginnings to always go further from "low-level" code. Subsequently the definition of "low level" has changed so that e.g. setting parameters in a template engine to generate HTML on server side is considered "low level" and beneath the programmer (or, more likely, too scary to get into).

        They fear the computer. So they resort to bloat in order to make it less frightening. In truth we've had MMUs in every computer since the

    • the truly l337 and browser-tech agnostic way of having app loading screens is to implement them as animated GIFS.

    • by Kkloe ( 2751395 )
      sounds like flashpages\java applets all over again
  • by QuietLagoon ( 813062 ) on Thursday July 27, 2017 @02:14PM (#54893049)
    I'm more in favor of Conservative Web Applications.
  • Not a detriment (Score:5, Insightful)

    by dogvomit ( 979755 ) on Thursday July 27, 2017 @02:17PM (#54893067)

    which gives you all sorts of great features that you'd normally associate with native apps, like push notifications

    There you have it. Push notifications are not great features. They are evil, distracting, manipulating, crud that leads to more and more advertising.

    Let's hope Apple at least has the sense to contain this disaster.

    --
    Happy happy oh my friend

    • What I have noticed is that if someone primarily uses their phone for "fun", i.e. a teenager, or an older person without a job, etc. then they want more push notifications. People that are really busy and use it primary for work don't want push notifications. Personally, I think push notifications should only be used for things that require an immediate time sensitive response. I.e. incoming phone call or teleconference, and different forms of instant messaging where people are expecting a real-time back a
      • by tepples ( 727027 )

        Personally, I think push notifications should only be used for things that require an immediate time sensitive response. I.e. incoming phone call or teleconference

        Fortunately, the specification lets users set up their notifications as you describe. When a domain asks to push notifications, the user checks whether it's a domain associated with real-time messaging, such as discordapp.com or skype.com, and chooses whether to allow or block notifications based on that.

    • I think that's just one potential problem, as an example of a larger issue: It's not clear that we all want web browsers to enable web apps to be more like native applications.

      I wouldn't say that web developers have earned enough trust that I want them to have more power over how my computer behaves. Aside from all the malware, there are ongoing issues with advertising and pop-ups. I don't want websites to be able to access my location. I don't want websites to be able to decide to store things on my co

      • It's not clear that we all want web browsers to enable web apps to be more like native applications.

        I think it's clear that plenty of people don't have a desire for this. And plenty of people (or at least me), actively want for this not to happen.

        • by tepples ( 727027 )

          It's not clear that we all want web browsers to enable web apps to be more like native applications.

          plenty of people (or at least me), actively want for this not to happen.

          Would you prefer not to have access to most applications at all because they are made for the desktop computing platform other than the one you use daily?

    • by fermion ( 181285 )
      Right now web sites are too intrusive, even dangerous. Many of the things that are good for desktop, such a drop downs or rollovers that are huge ware of real estate, are not god for mobile.

      I don't know what are the implications of mobile. I do know that google will adopt any technology that allows it to monotize end users because it is an ad agency and that is what ad agencies do. OTOH, Apple charges for services, so the end users matter so things like wasting time and security matter.

      We j ow in the w

  • by Anonymous Coward on Thursday July 27, 2017 @02:17PM (#54893073)

    Google's test bed for developers might be ok to put this to play around with. But the real world USES are very little if any. These things are beyond fucking annoying. I've blocked every single request for a page or site to send me updates. It's not needed or wanted.

    I view this functionality as a gaping security hole and a resource hog. It's not needed. Who the fuck wants this other than the site owner to push more ads?

    • by QuietLagoon ( 813062 ) on Thursday July 27, 2017 @02:32PM (#54893203)

      ... I've blocked every single request for a page or site to send me updates. It's not needed or wanted....

      It is wanted by someone --- the advertisers whose ads will ride piggy-back on every push notification you see.

  • by account_deleted ( 4530225 ) on Thursday July 27, 2017 @02:20PM (#54893095)
    Comment removed based on user account deletion
    • by tepples ( 727027 )

      How many people are willing to buy and carry two phones and pay two phone bills just to run the odd native application that isn't yet ported to iOS or web application that relies on features that Apple has refused to add to Safari?

  • by Anonymous Coward on Thursday July 27, 2017 @02:22PM (#54893109)

    Why the fuck would I want a website to have push notifications? Or worker threads on my machine? Or use this shit to have even more ads? Or let it access more of my information?

    Sorry, but the web is insecure in large part because every asshole web developer thinks the default should be for us to enable everything so their crappy site can work -- which makes us vulnerable to malicious ads, viruses, and all sorts of shit.

    I will never trust a fucking web application the way I would a native application, because we have seen time and time again, the web isn't something you can trust.

    Boo goddamned fucking hoo ... your new web technology may not be something we want anyway.

    I let javascript run on a whitelist basis only. I'm sure as hell not letting arbitrary websites have even more access to my machine.

    Fuck you, fuck off.

    • You're right, of course. I basically disable push notifications for almost every application I use, web or mobile. All of the noise that those messages generate are distracting, and slow down my ability to get to important alerts like an e-mail from my boss or a text message from my wife.

    • by doconnor ( 134648 ) on Thursday July 27, 2017 @03:11PM (#54893531) Homepage

      My website [transsee.ca] does bus arrival predictions, so it would be useful to have notifications so I could tell the user when their bus is about to arrive.

      I block a lot of my apps from doing notifications, but there are still lots of situations where notifications are useful.

      • It's a cost/benefit thing. There are certain thing for which push notifications can have some value. But I have yet to see that value exceed the cost of push notifications.

    • I will never trust a fucking web application the way I would a native application, because we have seen time and time again, the web isn't something you can trust.

      While there are plenty of native application developers who can't be trusted, I think you're right. The web seems to have a MUCH larger number of them. Like you, I have a much lower trust of anything web (or cloud) based by default.

      Experience has taught me that this is entirely justified.

  • by Anonymous Coward on Thursday July 27, 2017 @02:22PM (#54893113)

    You can tell that the entire concept is bullshit just on how they are marketing it ... "Progressive Web App" -- who are you trying to fool? HTML5 was progressive, they didn't need to call it "PHTML" to sell us on it because it proved its own merrit.

    If you're trying to do something complicated that requires native binaries, but you're using Javascript instead, you're doing it wrong. Period.

    (And regular old javascript can run offline already ... PWA is utter nonsense.)

    • by smartr ( 1035324 )
      As far as I can tell, they a note from Google's reasonably good advice on building Progressive Web Apps, and somehow feel their take on service workers and push notifications. Here's the browser support, and status of the "draft" w3c for the functionality: https://developer.mozilla.org/... [mozilla.org] ... But I guess the complaint is that startups can't get this functionality, with just a webpage: * Create an app loading screen * Use push notifications * Add offline support * Create an initial app UI to load instantly
      • So that sounds pretty cool that android will let me completely bypass their store to get those features and even distribute say, an enterprise "app" without needing Google Play or any other marketplace.

        You have that right now. Android allows you to install apps without a marketplace being involved in any way.

  • by clovis ( 4684 ) on Thursday July 27, 2017 @02:23PM (#54893121)

    Is this a way to bring back the features of IE6 and ActiveX controls, only now they can install themselves more easily?
    Who would not want this?

  • by account_deleted ( 4530225 ) on Thursday July 27, 2017 @02:25PM (#54893139)
    Comment removed based on user account deletion
  • by iggymanz ( 596061 ) on Thursday July 27, 2017 @02:26PM (#54893143)

    Translation: Their way of making money is a detriment to the way you make your living, or wish you could make a living? There are many ways to do each of the things you list without doing PWAs; no one has to share your infatuation with PWA

  • And lose 30%? (Score:2, Insightful)

    by ArhcAngel ( 247594 )
    Apple charges a 30% fee for apps to do business on their app store. This would allow web sites to dilute the need for those apps. Apple isn't about to give away that kind of control.
  • Nice (Score:5, Insightful)

    by BlueStrat ( 756137 ) on Thursday July 27, 2017 @02:28PM (#54893171)

    A slashvertisement for push-marketing software that's also a marketing attack piece aimed at an industry holdout.

    Who voted for this dreck while in the firehose, or did it simply get "inserted"?

    Strat

    • by Tailhook ( 98486 )

      Who

      Same shit birds that saluted when this crap appeared earlier; "With the current administration's attitude toward transparency and catering only to the largest corporate donors herp derp."

  • by martinX ( 672498 ) on Thursday July 27, 2017 @02:29PM (#54893179)

    Apple is having discussions. You're not invited.

  • If you boil a PWS down it's just a website/webpage that has a manifest and icon in its root folder. Just about everything else is preexisting technology. The only real advantage is that you wrap a browser window around the site and make it work more like a desktop app... like what Chrome Apps use to be. Ever wonder why Google / Alphabet abandoned that technology?

    • by e r ( 2847683 )

      The only real advantage is that you wrap a browser window around the site and make it work more like a desktop app... like what Chrome Apps use to be.

      That's basically what Electron is, isn't it?

      Ever wonder why Google / Alphabet abandoned that technology?

      I'm actually curious about this, yes. Could you please give me your take on it?

      • Of course, here are my thoughts:

        That's basically what Electron is, isn't it?

        No Electron and it's parent project Node Webkit (aka NW.JS) are complete stacks for building desktop applications with a NodeJS engine integrated in. Chrome Apps had a much more restrictive sandbox and ask for permission to do things.

        I'm actually curious about this, yes. Could you please give me your take on it?

        Sure my take comes down two main reasons for no continuing support for Chrome Apps:

        1. Maintaining Chrome App's sandb

      • by acroyear ( 5882 )

        The problem with Electron, and PhoneGap/Cordova, is adding all that weight. Yeah, I can package my app in those two services and get it to work and be deployed in web stores and app stores...but then I'm bundling in it a bunch of stuff that the browser already has done for me.

        The problem with Chrome apps is that we had all these nice HTML5 standard features (local storage, history which is html-*3*) and threw them away and made you use proprietary APIs. That made for UNportable code (the hackery I had to d

  • Don't need it (Score:5, Insightful)

    by Zontar_Thing_From_Ve ( 949321 ) on Thursday July 27, 2017 @02:49PM (#54893347)
    like push notifications, offline support, and app loading screens

    Push notifications are evil. I have one iphone app that I turned them on for, then turned them off, and they still come through any way from time to time. Now I'm starting to see more and more websites that want to send them. I don't need offline support. Who does? And what are "app loading screens" and why do I supposedly need them? All this post has done is make me very grateful to Apple.

  • You lost me at "push notifications". "App loading screens" sounds like "Ads I don't want".

    Pass.

  • They used to innovate, but as they have grown larger, they are becoming less likely to innovate (think large cellphone screens). they prefer their users in a walled garden and not free to make too many choices. For many people, that's just fine.

    • In this case two of the three "features" of progressive web apps are what most people do not want. How is it innovative to offer them if people don't want them?
  • Real Applications (Score:5, Insightful)

    by Nethemas the Great ( 909900 ) on Thursday July 27, 2017 @03:04PM (#54893481)

    ...which gives you all sorts of great features that you'd normally associate with native apps, like push notifications, offline support, and app loading screens -- but on the web! Awesome.

    Here we go again. Web devs trying to pretend they're making native apps. Folks, there are so many reasons why you would not want that. Native and web are two separate disciplines with two very different roles. You're screwdrivers not hammers. Quite trying to turn nails.

  • by blindseer ( 891256 ) <blindseer.earthlink@net> on Thursday July 27, 2017 @03:11PM (#54893539)

    In college as an intern I remember talking to the experienced engineers about this interesting video I saw about a guy talking about the concept of a "paradigm shift". The response was something like, "Oh, you mean that guy that couldn't sell his funny looking bicycle seat?" Apparently this guy had already developed a reputation.

    The video was about a funny looking bicycle seat, and it was interesting from an engineering perspective. What was wrong though was the product he was trying to sell was crap. I remembered the video and as someone that then rode a bicycle regularly I'd see people start to use bicycle seats with features he mentioned in his video, but the idea he was trying to sell was not a great idea.

    Progressive web apps sounds like just another funny looking bicycle seat. There's some good ideas there but the product they want to sell as a "paradigm shift" is crap. The article even spells out the problems, like needing a constant internet connection to work. Data still costs money even if it's real cheap, and people might not be fond of constantly getting charged for using "too much" data on their cell plan.

    Progressive web apps are stupid. Apple is smart to be reluctant to support them. Maybe they have some good ideas here that will find their way into future products and services but this just sounds stupid.

  • by TheFakeTimCook ( 4641057 ) on Thursday July 27, 2017 @03:16PM (#54893581)

    This sounds to me like the latest exploit-vector.

    I DO NOT WANT "worker processes" being shoved onto my computer, regardless of Sandboxing.

    Just wait. There WILL be an exploit or hundred that use this.

    And I will sit back and laugh.

    • It doesn't need an exploit to be bad. The basic concept of allowing websites to use your resources while you're not actually viewing the website is troublesome. Seems sure to result in memory leaks and degraded performance which will be very hard for most people to track down the source of.

  • that there STILL is a web that doesn't care for Google.

    I mean, take a web server, and a database and a couple billion of browers and you have something. Add Google and you have what? More ads! What if you don't need them? THIS is the thought that Google can't stand.

  • Like BLOAT! ...Even SLOWER webpages that further frustrate the end user's experience... I disabled JavaScript last year on my phone/tablets and have been whitelisting sites because it's gotten so bad. It's bothersome that desktop sites are still a faster and in general a better experience than these bloated web-aps from HELL!
  • As someone who blocks Javascript by default, the fewer sites doing the PWA thing, the better.

  • A LOT more.

    The heart of is that people want an "app" experience on a phone/tablet. You could say it is just a browser page, but it isn't. They don't like running shit in browsers. Browsers are for reading crap that apps redirect them to. They aren't for, say, music players, video players, or games.

    Yet html5/javascript can do all that.

    PWA, through the manifest, is a way to package the html5 application so that it doesn't need the heavyweight crap that a Cordova/PhoneGap packaged app carries. You like this a

  • I would think, given the typical Apple user profile, that they would demand Progressive web apps! Except Apple, by nature, is non-PC, so there is already a problem.

  • Push notifications on web pages? No way in hell would I trust that, are you crazy? Kudos to Apple for avoiding it. Just like Apple helped kill Flash, I hope they help kill this new invader.

Solutions are obvious if one only has the optical power to observe them over the horizon. -- K.A. Arsdall

Working...