Jeff Long
Google I/O “…showed just how big Google is, and how it doesn’t have one party line when it comes to the web…” adactio.com/journal/10708
There were plenty of talks about building for the web at this year’s Google I/O event. That makes a nice change from previous years when the web barely got a look in and you’d be forgiven for thinking that Google I/O was an event for Android app developers.
This year’s event showed just how big Google is, and how it doesn’t have one party line when it comes to the web and native. At the same time as there were talks on Service Workers and performance for the web, there was also an unveiling of Android Instant Apps—a full-frontal assault on the web. If you thought it was annoying when websites door-slammed you with intrusive prompts to install their app, just wait until they don’t need to ask you anymore.
I've been "Maybe I'll go Android" for awhile but today's announcement of http:// links getting hijacked into apps got me all like Nope.
— Dave Rupert (@davatron5000) May 18, 2016
Peter has looked a bit closer at Android Instant Apps and I think he’s as puzzled as I am. Either they are sandboxed to have similar permission models to the web (in which case, why not just use the web?) or they allow more access to native APIs in which case they’re a security nightmare waiting to happen. I’m guessing it’s probably the former.
Meanwhile, a different part of Google is fighting the web’s corner. The buzzword du jour is Progressive Web Apps, originally defined by Alex as:
A lot of those points are shared by good native apps, but the first and last points in that list are key features of the web: being responsive and linkable.
Alas many of the current examples of so-called Progressive Web Apps are anything but. Flipkart and The Washington Post have made Progressive Web Apps that are getting lots of good press from Google, but are mobile-only.
Looking at most of the examples of Progressive Web Apps, there’s an even more worrying trend than the return to m-dot subdomains. It looks like most of them are concentrating so hard on the “app” part that they’re forgetting about the “web” bit. That means they’re assuming that modern JavaScript is available everywhere.
Alex pointed to shop.polymer-project.org as an example of a Progressive Web App that is responsive as well as being performant and resilient to network failures. It also requires JavaScript (specifically the Polymer polyfill for web components) to render some text and images in a browser. If you’re using the “wrong” browser—like, say, Opera Mini—you get nothing. That’s not progressive. That’s the opposite of progressive. The end result may feel very “app-like” if you’re using an approved browser, but throwing the users of other web browsers under the bus is the very antithesis of what makes the web great. What does it profit a website to gain app-like features if it loses its soul?
I’m getting very concerned that the success criterion for Progressive Web Apps is changing from “best practices on the web” to “feels like native.” That certainly seems to be how many of the current crop of Progressive Web Apps are approaching the architecture of their sites. I think that’s why the app-shell model is the one that so many people are settling on.
Personally, I’m not a fan of the app-shell model. I feel that it prioritises exactly the wrong stuff—the interface is rendered quickly while the content has to wait. It feels weirdly like a hangover from Appcache. I also notice it being used as a get-out-of-jail-free card, much like the ol’ “Single Page App” descriptor; “Ah, I can’t do progressive enhancement because I’m building an app shell/SPA, you see.”
But whatever. That’s just, like, my opinion, man. Other people can build their app-shelled SPAs and meanwhile I’m free to build websites that work everywhere, and still get to use all the great technologies that power Progressive Web Apps. That’s one of the reasons why I’ve been quite excited about them—all the technologies and methodologies they promote match perfectly with my progressive enhancement approach: responsive design, Service Workers, good performance, and all that good stuff.
I hope we’ll see more examples of Progressive Web Apps that don’t require JavaScript to render content, and don’t throw away responsiveness in favour of a return to device-specific silos. But I’m not holding my breath. People seem to be so caught up in the attempt to get native-like functionality that they’re willing to give up the very things that make the web great.
For example, I’ve seen people use a meta viewport declaration to disable pinch-zooming on their sites. As justification they point to the fact that you can’t pinch-zoom in most native apps, therefore this web-based app should also prohibit that action. The inability to pinch-zoom in native apps is a bug. By also removing that functionality from web products, people are reproducing unnecessary bugs. It feels like a cargo-cult approach to building for the web: slavishly copy whatever native is doing …because everyone knows that native apps are superior to websites, right?
Here’s another example of the cargo-cult imitation of native. In your manifest JSON file, you can declare a display property. You can set it to browser, standalone, or fullscreen. If you set it to standalone or fullscreen then, when the site is launched from the home screen, it won’t display the address bar. If you set the display property to browser, the address bar will be visible on launch. Now, personally I like to expose those kind of seams:
The idea of “seamlessness” as a desirable trait in what we design is one that bothers me. Technology has seams. By hiding those seams, we may think we are helping the end user, but we are also making a conscience choice to deceive them (or at least restrict what they can do).
Other people disagree. They think it makes more sense to hide the URL. They have a genuine concern that users will be confused by launching a website from the home screen in a browser (presumably because the user’s particular form of amnesia caused them to forget how that icon ended up on their home screen in the first place).
Fair enough. We’ll agree to differ. They can set their display property how they want, and I can set my display property how I want. It’s a big web after all. There’s no one right or wrong way to do this. That’s why there are multiple options for the values.
Or, at least, that was the situation until recently…
Remember when I wrote about how Chrome on Android will show an “add to home screen” prompt if your Progressive Web App fulfils a few criteria?
Well, those goalposts have moved. There is now a new criterion:
display value of browser.Chrome developers have decided that displaying URLs is not “best practice”. It was filed as a bug.
A bug.
Displaying URLs.
A bug.
I’m somewhat flabbergasted by this. The killer feature of the web—URLs—are being treated as something undesirable because they aren’t part of native apps. That’s not a failure of the web; that’s a failure of native apps.
Now, don’t get me wrong. I’m not saying that everyone should be setting their display property to browser. That would be far too prescriptive. I’m saying that it should be a choice. It should depend on the website. It should depend on the expectations of the users of that particular website. To declare that all users of all websites will be confused by seeing a URL is so presumptuous and arrogant that it beggars belief.
I wouldn’t even have noticed this change of policy if it weren’t for the newly-released Lighthouse tool for testing Progressive Web Apps. The Session gets a good score but under “Best Practices” there was a red mark against the site for having display: browser. Turns out that’s the official party line from Chrome.
Just to clarify: you can have a site that has literally no HTML or turns away entire classes of devices, yet officially follows “best practices” and gets rewarded with an “add to home screen” prompt. But if you have a blazingly fast responsive site that works offline, you get nothing simply because you don’t want to hide URLs from your users:
I want people to be able to copy URLs. I want people to be able to hack URLs. I’m not ashamed of my URLs …I’m downright proud.
Stuart argues that this is a paternal decision:
The app manifest declares properties of the app, but the
displayproperty isn’t about the app; it’s about how the app’s developer wants it to be shown. Do they want to proudly declare that this app is on the web and of the web? Then they’ll add the URL bar. Do they want to conceal that this is actually a web app in order to look more like “native” apps? Then they’ll hide the URL bar.
I think there’s something to that, but digging deeper, developers and designers don’t make decisions like that in isolation. They’re generally thinking about what’s best for users. So, yes, absolutely, different apps will have different display properties, but that shouldn’t be down to the belief system of the developer; it should be down to the needs of the users …the specific needs of the specific users of that specific app. For the Chrome team to come down on one side or the other and arbitrarily declare that one decision is “correct” for every single Progressive Web App that is ever going to be built …that’s a political decision. It kinda feels like an abuse of power to me. Withholding the “add to home screen” prompt like that has a whiff of blackmail about it.
The other factors that contribute to the “add to home screen” prompt are pretty uncontroversial:
This isn’t the first time that Chrome developers have made a move against the address bar. It’s starting to grind me down.
Up until now I’ve been a big fan of Progressive Web Apps. I understood them to be combining the best of the web (responsiveness, linkability) with the best of native (installable, connectivity independent). Now I see that balance shifting towards the native end of the scale at the expense of the web’s best features. I’d love to see that balance restored with a little less emphasis on the “Apps” and a little more emphasis on the “Web.” Now that would be progressive.
Google I/O “…showed just how big Google is, and how it doesn’t have one party line when it comes to the web…” adactio.com/journal/10708
Regressive Web Apps adactio.com/journal/10708 - Jeremy going full out again.
Regressive Web Apps adactio.com/journal/10708
html_entities: Regressive Web Apps adactio.com/journal/10708
“concentrating so hard on the app part that they’re forgetting about the web bit” —@adactio, on most prog web appsadactio.com/journal/10708
Progressive Web Apps is basically an attempt to incentivise best practice but it risks doing the opposite twitter.com/adactiojournal…
Regressive Web Apps adactio.com/journal/10708
Regressive Web Apps by @adactio: adactio.com/journal/10708
Regressive Web Apps. @adactio is the Jedi Knight of the web universe. And we should fight with him on the light side twitter.com/adactiojournal…
Agree: »[…]that balance restored with a little less emphasis on the “Apps” and a little more emphasis on the “Web.”« adactio.com/journal/10708
liked adactio.com/journal/10708 because: this @adactio guy always seems to be on point. (kartikprabhu.com/notes/like-reg…)
[…] Looking at most of the examples of Progressive Web Apps, there’s an even more worrying trend than the return to m-dot subdomains. It looks like most of them are concentrating so hard on the “app” part that they’re forgetting about the “web” bit. That means they’re assuming that modern JavaScript is available everywhere.
I’m again with Jeremy Keith here. I’m team web. Links and Urls (and being responsive) are the web’s superpower. Don’t cripple that by trying to emulate ‘native’.
(and I want to add a second like for the usage of the word ‘flabbergasted’)
Interesting Read… adactio.com/journal/10708
Another great thought piece by @adactio - Regressive Web Apps adactio.com/journal/10708 - Please support what he says! @ChromiumDev
I support +Jeremy Keithhttps://adactio.com/journal/10708
Regressive Web Apps adactio.com/journal/10708
Here’s @adactio on Progressive Web Apps & some (frankly bad) decisions made by the Chrome team… Hope this gets fixed twitter.com/adactioJournal…
Killing the web to save it. adactio.com/journal/10708
“Regressive Web Apps” via @digg adactio.com/journal/10708
adactio.com/journal/10708 Opinion on the direction taken by PWA by @adactio
Regressive Web Apps adactio.com/journal/10708 cc @padupuy
Very much agree with @adactio’s sentiment: adactio.com/journal/10708. I love the underlying APIs, but question the PWA “validator” choice.
Very good read by @adactio on Google’s Progressive Web Apps, and he calls them “regressive” rightfully so! adactio.com/journal/10708
Once again, @adactio is killing it. Sans-JS rendering can’t be forgotten. twitter.com/adactioJournal…
“…the success criterion for Progressive Web Apps is changing from ‘best [web] practices’ to ‘feels like native.’” adactio.com/journal/10708
Superb post by @adactio, neatly articulating many worries about Google’s approach to PWAs - “Regressive Web Apps”, adactio.com/journal/10708
He’s right, ya know. adactio.com/journal/10708
>app-shell model prioritises the wrong stuff: interface is rendered quickly while the content has to wait —@adactio adactio.com/journal/10708
Progressive web apps are for websites. Extra points for the Big Lebowski reference. adactio.com/journal/10708
“What does it profit a website to gain app-like features if it loses its soul?” - @adadtio on Progressive Web Apps adactio.com/journal/10708
“Other ppl can build their app-shelled SPAs and meanwhile I’m free to build websites that work everywhere” —@adactio adactio.com/journal/10708
“concentrating so hard on the “app” part that they’re forgetting about the “web” bit” adactio.com/journal/10708 @adactio via @RWD
Concerning… “Chrome developers have decided that displaying URLs is not “best practice”. It was filed as a bug.” 😳adactio.com/journal/10708
Regressive Web Apps: adactio.com/journal/10708 /by @adactio
“The killer feature of the web—URLs—are being treated as undesirable because they aren’t part of native apps.”adactio.com/journal/10708
“That’s not progressive. That’s the opposite of progressive.”adactio.com/journal/10708
“I’ve seen people use a meta viewport declaration to disable pinch-zooming on their sites.” grr! adactio.com/journal/10708
Embracing native by throwing web’s best practices twitter.com/adactiojournal…
“The inability to pinch-zoom in native apps is a bug.”adactio.com/journal/10708
“Regressive Web Apps” — adactio.com/journal/10708 Important read. Progressive Web Apps should be more than just “native-like”.
Adactio: Journal—Regressive Web Apps adactio.com/journal/10708
Regressive Web Apps adactio.com/journal/10708 <- @adactio sets off the alarm bells before it’s too late
Regressive Web Apps adactio.com/journal/10708
adactio.com/journal/10708 fully agree to this :(
Hell yeah. “The inability to pinch-zoom in native apps is a bug.”—@adactioadactio.com/journal/10708
A fair—and important, I think—critique of the current state of progressive web apps from @adactio. adactio.com/journal/10708
Ultimately the web is the web and apps are apps. People need to stop trying to make native apps out of the web adactio.com/journal/10708
Once again @adactio breaks it down. Regressive Web Apps adactio.com/journal/10708 via @instapaper
Chrome, do not kill the links. Please twitter.com/adactioJournal…
Great piece by @adactio on Responsive Web Apps. I’ve always felt the URL is one of the best pieces of design ever. adactio.com/journal/10708
Adactio: Journal—Regressive Web Apps adactio.com/journal/10708
From @adactio, Regressive Web Apps “…examples of so-called Progressive Web Apps are anything but…” adactio.com/journal/10708 HT @silentworks
Everybody should ready this by @adactio adactio.com/journal/10708
Free the URL! “Withholding the “add to home screen” prompt like that has a whiff of blackmail about it.” adactio.com/journal/10708
Regressive Web Apps: adactio.com/journal/10708 I agree with @adactio. Showing the web app URL isn’t a bug - it’s a user choice.
@adactioJournal Great post! My biggest regret with Pokedex.org is not making it work without JS. Not setting a great example.
Check out “Regressive Web Apps” (adactio.com/journal/10708) by @adactio. I was pessimistic based on the title, but it has good stuff inside!
@adactioJournal …still trying to work out how I comment on the site - I’m missing something.
I still use URLs to orientate myself - here’s @adactio on why we need to keep them adactio.com/journal/10708
brb making a “Hell no! URLs won’t go!” protest sign adactio.com/journal/10708
“What does it profit a website to gain app-like features if it loses its soul?” twitter.com/adactioJournal…
Regressive web apps - adactio.com/journal/10708
.@adactio about »progressive web apps shifting towards the native end at the expense of the web’s best features« adactio.com/journal/10708
For those building webapps: how Google is trying to destroy what’s good about the web in mobile webapps: adactio.com/journal/10708
I agree with @adactio. Disabling the “add to home screen” prompt for sites with “display: browser” is wrong. bit.ly/1ONeDxQ
A nice point of view about #PWA that will got me thinking for a while adactio.com/journal/10708 by @adactio
I am grateful to have @adactio fighting for the web: adactio.com/journal/10708
Dear Google, please let me keep using URLs in my internet. It’s kind of a big deal. Thanks. adactio.com/journal/10708
Feels like developers using dark patterns to remove the URL and keep you on @google products #capitalisimBleh ~adactio.com/journal/10708
👁 Reading: “Adactio: Journal—Regressive Web Apps” adactio.com/journal/10708
Agree with most of adactio.com/journal/10708 about current crop of PWAs. Yet I remain bullish. Looking forward to the Boston Globe of PWAs.
Here is @adactio writing thoughtful things about “responsive” web apps. adactio.com/journal/10708.… just drop swears, myself.
Excellent post by @adactio about how on our way to make the Web more like native, we’re losing what makes it great: adactio.com/journal/10708
once a designer asked to remove the address bar from a web app. Felt strange. @adactio captures those feelings well adactio.com/journal/10708
.@adactio is the Dark Knight of web development. He’s the hero the web deserves. adactio.com/journal/10708
Regressive Web Apps - Killing the web to save it adactio.com/journal/10708 @adactio
Recommended read: @adactio’s Regressive Web Apps adactio.com/journal/10708
‘I hope we’ll see more examples of Progressive Web Apps that don’t require JavaScript to render content’ 👏🏼👏🏼adactio.com/journal/10708
Regressive Web Apps via @adactio adactio.com/journal/10708
Brilliant article by @adactio on how progressive web apps should not neglect the “web” aspectadactio.com/journal/10708 #pwa
Retweeted Lea Verou (@LeaVerou): Excellent post by @adactio about how on our way to make the Web more like… fb.me/7vjwetgGW
Regressive Web Apps adactio.com/journal/10708 /via @CleverMarks
Regressive apps (do kill the web with native-like bullshit) — A great, opiniated read by @adactio adactio.com/journal/10708 #javascript
adactio.com/journal/10708 Adactio: Journal—Regressive Web Apps
Good thing I was able to copy this URL and share it: adactio.com/journal/10708 Well said @adactio
@aperfect I think you might enjoy this one: adactio.com/journal/10708
Part of me feels that if you’re required to hide the URL, you shouldn’t be allowed to call it a web app. adactio.com/journal/10708
Regressive Web Apps L: adactio.com/journal/10708 C: news.ycombinator.com/item?id=117707…
Regressive Web Apps adactio.com/journal/10708 (cmts news.ycombinator.com/item?id=117707…)
Regressive Web Apps: adactio.com/journal/10708 Comments: news.ycombinator.com/item?id=117707…
Regressive Web Apps : adactio.com/journal/10708 Comments: news.ycombinator.com/item?id=117707…
IT news: Regressive Web Apps adactio.com/journal/10708
IT news: Regressive Web Apps adactio.com/journal/10708
Regressive Web Apps adactio.com/journal/10708
I love this. I love @adactio adactio.com/journal/10708
Regressive Web Apps adactio.com/journal/10708
“What does it profit a website to gain app-like features if it loses its soul?”adactio.com/journal/10708 Read this if u haven’t. Now.
@gruber Thoughts on adactio.com/journal/10708 ?
Progressive Web Apps is a Google brand and only they get to decide what it means and how it’s rewarded. adactio.com/journal/10708
Regressive Web Apps adactio.com/journal/10708?…
“Regressive Web Apps” by @adactio adactio.com/journal/10708
Regressive Web Apps adactio.com/journal/10708
If you will read only 1 webdev article today:adactio.com/journal/10708 I didn’t promote PE 10 years for the cool kids to spit on it.
Ember has been leaning into the Progressive Web Apps strategy, some of the moves from Google re: adactio.com/journal/10708 are unfortunate.
“Alas many of the current examples of so-called Progressive Web Apps are anything but.” @adactio Regressive Web Apps adactio.com/journal/10708
The reaction to Progressive Web Apps - “Regressive Web Apps” adactio.com/journal/10708
From adactio.com/journal/10708 “What does it profit a website to gain app-like features if it loses its soul?” jesus, save the poor websites
Interesting point of view on Android Instant Apps. Have to re-evaluate my own thoughts on the matter. twitter.com/adactiojournal…
Regressive Web Apps adactio.com/journal/10708
I’m starting to become a believer in Progressive Enhancement again. It’s been a long time. adactio.com/journal/10708
I agree. We’re about to replace the open web with something closed, neutered and ultimately detrimental to humanity. adactio.com/journal/10708
Regressive Web Apps adactio.com/journal/10708 #webapps #progressive
Adactio: Journal—Regressive Web Apps adactio.com/journal/10708
Regressive Web Apps — interesting take on a UX pattern that drives me crazy on Android/mobile platform: adactio.com/journal/10708 @adactio
“[URLs are] not a failure of the web; that’s a failure of native apps.” adactio.com/journal/10708
Regressive Web Apps (Jeremy Keith - @adactio) redef.com/item/5745e9d6d…
Have you read this piece by @adactio yet? Regressive Web Apps.adactio.com/journal/10708 Do. important!
Adactio: Journal—Regressive Web Apps adactio.com/journal/10708
Really great article about Progressive Web Apps trend.adactio.com/journal/10708
This, by @adactio on an alarming decision by Chrome re: Progressive Web Apps is worth reading adactio.com/journal/10708 (via @SaraSoueidan)
Regressive Web Apps,by Jeremy Keith @adactio /Adactio adactio.com/journal/10708
RT [at]tkadlec: 公正な-と思うことが重要と -[at]adactio から進歩的な web アプリケーションの現在の状態の批判。adactio.com/journal/10708
Le Web se fait bouffer par les apps natives mais non tout va bien on ne devrait pas imiter les apps natives… twitter.com/adactioJournal…
What are people’s feelings on Progressive Web Apps? I was leaning yes, but now I’m leaning no. adactio.com/journal/10708
I have to say… yeah, what He said: adactio.com/journal/10708
Adactio: Journal: Regressive Web Apps adactio.com/journal/10708
The buzzword du jour pour les nerds is Progressive Web Apps, adactio.com/journal/10708
So it turns out that “progressive” is an (increasingly) optional feature for progressive web apps. adactio.com/journal/10708
Whoa.. this is spot on by @adactio adactio.com/journal/10708 #savetheweb I feel like a schmuck doing JS only SPA of late. Hard to get balance.
Adactio: Journal—Regressive Web Apps adactio.com/journal/10708
Currently Reading: adactio.com/journal/10708
見てる: “Adactio: Journal—Regressive Web Apps” adactio.com/journal/10708
Are “Progressive Web Apps” becoming Regressive Web Apps? adactio.com/journal/10708
“It feels like a cargo-cult approach to building for the web: slavishly copy whatever native is doing“ adactio.com/journal/10708
“Chrome developers have decided that displaying URLs is not “best practice,” by @adactio.adactio.com/journal/10708
Regressive Web Apps adactio.com/journal/10708
“What does it profit a website to gain app-like features if it loses its soul?” adactio.com/journal/10708
Regressive Web Apps adactio.com/journal/10708
adactio.com/journal/10708 Regressive web apps. Very nice read, and I agree to most points made in the writeup.
Bijzonder goed artikel over pro-/tegressive Web Apps en de idioterie dat native per definitie beter is. #webofappadactio.com/journal/10708
Regressive Web Apps adactio.com/journal/10708
Regressive Web Apps adactio.com/journal/10708
Regressive Web Apps and hiding URLs adactio.com/journal/10708
Regressive Web Apps: @adactio on Progressive Web Apps #pwa adactio.com/journal/10708
Opinion sur les “progressive web app” qui perdent doucement les avantages du Web adactio.com/journal/10708 (URL, compatibilité …)
Top story:web design Adactio: Journal—Regressive Web Apps adactio.com/journal/10708, see more tweetedtimes.com/helikopterdsgn…
Top story: Adactio: Journal—Regressive Web Apps adactio.com/journal/10708, see more tweetedtimes.com/helikopterdsgn…
Gotta admit, I was enamoured with progressive web apps at Google IO, but @adactio raises good point regarding urls adactio.com/journal/10708
Agree wholeheartedly with the points by @adactio here adactio.com/journal/10708 “Don’t slavishly copy native“
Regressive Web Apps, @adactio warning about the issues of Progressive Web Apps, mostly the URL not being shown adactio.com/journal/10708
@therealkimblim Noget om Progressive web apps: adactio.com/journal/10708
“throwing the users of other web browsers under the bus is the very antithesis of what makes the web great” adactio.com/journal/10708
Must-read: “Regressive Web Apps” — adactio.com/journal/10708
Regressive Web Apps adactio.com/journal/10708 (via @adactio)
A must read article for every web developer. Regressive Web Apps by @adactio 👉 adactio.com/journal/10708
Ha! It! Really! Works!
I have to admit I was a bit sceptical of the outcome after I tweaked and added things and bits of my website at the Indiewebcamp in Nuremberg, setting up a service worker and offline caching things, adding a manifest file … while in theory I understand what all of this was supposed to do, I felt a bit dumb for not completly grasping how to control the stuff.
So as so often when learning new tricks on the web, it started with copy/pasting a working solution and trying to adapt this to my ideas.
But the one (visible) ‘ahaa!’ outcome — getting the Chrome browser to display the ‘add to home screen’ prompt — it hasn’t happened yet. Even during my tests at the Open Device Lab Frankfurt, nothing happened. There is this thing; the Chrome browser kind of decides*) if you as a visitor have interacted and shown enough interest in the web site before it’ll show this prompt. Apparently my one-time visits during the tests were not enough.
Until now.
So yes, technically I now have my web site as a “progressive web app”: In case you have visited some of my contents while being online, you then can browse and read the stuff while being offline. Other than that, I haven’t dug deeper, so there’s currently no storage of user input or interaction for use when being online again — but all this is possible, though maybe not really useful for my website. I highly recomment Jake Archibald’s talk on this year’s Google I/O event, if you are interested in this PWA stuff. (*)But also take good note of Jeremy Keith’s article.)
For the moment I am excited that I got this to work, just for the sake of getting it to work. :-)
“Chrome developers have decided that displaying URLs is not “best practice” :-/ adactio.com/journal/10708
Are web apps progressing to the right direction? adactio.com/journal/10708
regressive web apps — @adactio‘s take on Google’s new forced buzzword adactio.com/journal/10708
Pretty sure you already read @adactio’s point of vue on Progressive Web Apps, but if not, go:adactio.com/journal/10708
Google says showing URLs is a bug? Really? Interesting article about #regressivewebapps by @adactio adactio.com/journal/10708
Treating the URL bar as a bug is very sad. Mozilla, too, was in that antipattern mode in the FxOS days. adactio.com/journal/10708
“What does it profit a website to gain app-like features if it loses its soul?” – a must-read by @adactio. ☞ adactio.com/journal/10708
Regressive Web Apps bit.ly/1OXMMAj Important words by @adactio The web is in danger. We can kill it or save it. Choose wisely.
excellent post from @adactio on PWAs and the hiding of URLs adactio.com/journal/10708
Adactio: Journal—Regressive Web Apps adactio.com/journal/10708
@m_ott @adactio totally agreed - Responsibility for huge media company chickens because zetafleet.com/blog/2015/11/p… - thankyou.
Regressive Web Appsadactio.com/journal/10708 Comments URL: news.ycombinator.com/item?id=117707…
Regressive Web Apps adactio.com/journal/10708
Regressive Web Apps - adactio.com/journal/10708
Adactio digs into the “dark side” of the google (badly) opinionated universe. URL are not a shame! adactio.com/journal/10708
2/2 “… that’s a political decision. It kinda feels like an abuse of power to me.” adactio.com/journal/10708
Regressive Web Apps adactio.com/journal/10708
Regressive Web Apps ~ adactio.com/journal/10708
On regressive web apps: adactio.com/journal/10708
Displaying URLs is NOT a bug adactio.com/journal/10708 #urlsnotbug
If you haven’t read @adactio’s post on Progressive Web Apps please do: adactio.com/journal/10708 The web’s only the web if we keep it that way
This post by @adactio should be mandatory reading for every web developer adactio.com/journal/10708
I was waiting for this article@adactio adactio.com/journal/10708
“slavishly copy whatever native is doing …because everyone knows that native apps are superior to websites, right?” adactio.com/journal/10708
“slavishly copy whatever native is doing …because everyone knows that native apps are superior to websites, right?” adactio.com/journal/10708
Regressive Web Apps adactio.com/journal/10708 Apps moving into the wrong direction?
Regressive web apps: too much native, not enough web?!? Interesting read by @adactio #web #progressive #regressiveadactio.com/journal/10708
Regressive Web Apps by @adactio adactio.com/journal/10708
Excellent use of the word flabbergastedadactio.com/journal/10708
Progressive Web Apps: why not “like native” AND responsive and cross device? adactio.com/journal/10708 #RWD #pwa
“many of the current examples of so-called Progressive Web Apps are anything but” adactio.com/journal/10708
Developers that love the web: worth a read on some unsettling ideas coming from Google/Chrome: adactio.com/journal/10708 @adactio
Displaying URLs a bug????@Adactio—Regressive Web Apps adactio.com/journal/10708
Regressive Web Apps by @adactio j.mp/27TZfva #webdev #javascript #responsive #progressive
Adactio: Journal—Regressive Web Apps adactio.com/journal/10708
If you love the web - you stay away from Google. adactio.com/journal/10708
Regressive Web Apps by @adactio - adactio.com/journal/10708
Regressive Web Apps. adactio.com/journal/10708
Is Google helping or harming the web? Great insight from @adactio adactio.com/journal/10708
Regressive Web Apps | Adactio by Jeremy Keith 2016-05-24adactio.com/journal/10708#f2etw 不 progressive 的 Progressive twitter.com/LeaVerou/statu…
Regressive Web Apps — the cargo-cult of so-called Progressive Web Apps by @adactio. adactio.com/journal/10708
Regressive #Web #Apps adactio.com/journal/10708
Regressive #Web #Apps adactio.com/journal/10708
Oh look, it’s more awful anti-web bullshit from Google. adactio.com/journal/10708
Websites becoming more like native apps is good…until it hurts core elements of the Internet: ow.ly/txQw300BGHj via @adactio #webdev
I love my URLs, everyone who works on the web should. adactio.com/journal/10708
Adactio: Journal—Regressive Web Apps adactio.com/journal/10708
Regressive Web Apps adactio.com/journal/10708 #webdev via @adactio
Thoughts on progressive web apps from @adactio:adactio.com/journal/10708
Great article on Google I/O and progressive (or not) web apps adactio.com/journal/10708 By Jeremy Keith.
Worth a read -> ‘Regressive Web Apps’ by @adactio adactio.com/journal/10708
Web vs native development battle. Make web perform like a native or native perform like web? adactio.com/journal/10708
More annoying than “Want to use the app instead?”: Android Instant Apps—a full-frontal assault on the Web adactio.com/journal/10708 #WebWeWant
“The killer feature of the #Web—#URLs—are treated as something undesirable because they aren’t part of native apps.” adactio.com/journal/10708
Regressive Web Apps adactio.com/journal/10708
Google relies on URLs to power web search but wants to hide them from users… 🤔 Regressive Web Apps by @adactio adactio.com/journal/10708
As usual, @adactio is killing it over at adactio.com/journal/10708.
adactio.com/journal/10708 yep yep yep!
Good thoughts on how much Web is preserved in Progressive Web Apps: adactio.com/journal/10708 (via twitter.com/RubenVerborgh/…)
Progressive Web Apps (or, throwing users of other web browsers under the bus) adactio.com/journal/10708
Good article about #PWA. Interesting to see some arguing opinion adactio.com/journal/10708 cc @kePennar
@h4emtfr Du som älskar allt Google gör, läst adactio.com/journal/10708 ?
“URLs are being treated as undesirable because they aren’t part of native apps” #PWA adactio.com/journal/10708
“Regressive Web Apps” — re: #Google’s proposed “cargo-cult approach to building for the web”.#UX to be avoided.adactio.com/journal/10708
Spot on! adactio.com/journal/10708
Great article about “Regressive Web Apps” by @adactio adactio.com/journal/10708
Regressive Web Apps adactio.com/journal/10708 by @adactio Some very good points in here. #webdev #apps
Jeremy Keith fights for the URL. twitter.com/adactioJournal…
Thoughts and concerns about Progressive Web apps. adactio.com/journal/10708 #ild
Regressive Web Apps: Killing the web to save it (less Apps, more Web)adactio.com/journal/10708 #WebDevelopment
💯 @adactio. “What does it profit a website to gain app-like features if it loses its soul?” adactio.com/journal/10708
Adactio: Journal—Regressive Web Apps adactio.com/journal/10708
Was a big fan off Progressive Web Apps. Now I don’t know. Seems like Google want to make them Regressive Web Apps :( adactio.com/journal/10708
Regressive Web Apps adactio.com/journal/10708 #博客 #feedly
There are good things in the web industry’s future, this does not seems like one of those adactio.com/journal/10708 #AndroidInstantApps
“..so caught up in getting native-like func that they’re willing to give up the very things that make the web great” adactio.com/journal/10708
Regressive web apps. adactio.com/journal/10708
Adactio: Journal—Regressive Web Apps adactio.com/journal/10708
Chrome developers have decided that displaying URLs is not “best practice”.adactio.com/journal/10708
@adactio gets the web. Apparently, some folks at Google don’t. Who would say that about Google some years ago? adactio.com/journal/10708
Regressive Web Apps by @adactio is required reading on native apps, the web and URLs: adactio.com/journal/10708
“Chrome developers have decided that displaying URLs is not ‘best practice’”–adactio.com/journal/10708 I’m flabbergasted to @adactio.
“balance shifting towards the native end of the scale at the expense of the web’s best features” adactio.com/journal/10708 #webapp #Chrome
Regressive Web Apps adactio.com/journal/10708
Regressive Web Appsadactio.com/journal/10708
Regressive Web Apps adactio.com/journal/10708
Regressive Web Apps adactio.com/journal/10708 vai @adactio
見てる: “Adactio: Journal—Regressive Web Apps” adactio.com/journal/10708
It is so good to know that we have people like @adactio fighting for the web. It gives me hope Regressive Web Apps-adactio.com/journal/10708
Don’t know how I’m only just seeing this, but web people, you should definitely read Regressive Web Apps by @adactio adactio.com/journal/10708
»Progressive Web Apps […] changing from “best practices on the web” to “feels like native.”« adactio.com/journal/10708
“Throwing the users of other web browsers under the bus is the very antithesis of what makes the web great” @adactio adactio.com/journal/10708
“Regressive Web Apps” by @adactio ow.ly/UDVZ300GKyw
“concentrating so hard on the app part that they’re forgetting about the web bit”adactio.com/journal/10708
Adactio: Journal—Regressive Web Apps - adactio.com/journal/10708?… via @adactio
Some important thoughts from @adactio about Google’s new requirements for Progressive Web Apps adactio.com/journal/10708 @googledevs
Still much up for grabs in evolution of Progressive Web Apps - an important piece by @adactio on some concerns: adactio.com/journal/10708
Some worrying trend w/ PWA concentrating so hard on the “app” part, that they’re forgetting about the “web” adactio.com/journal/10708
I submit that this is about Progressive(ly Enhanced) Web Resources, rather than Progressive Web Apps adactio.com/journal/10708
Regressive Web Appsadactio.com/journal/10708
Regressive Web Apps pocket.co/sMMWF6 via @adactio
There’s already a lot of criticism around Google’s Progressive Web Apps plan adactio.com/journal/10708 not to mention AMPs
Interesting take on Progressive Web Apps by @adactio. I, too, am a fan of the URL. adactio.com/journal/10708
Very good read about Progressive Web App #pwa #progressivewebadactio.com/journal/10708
即使是 Google 也在开放的 Web 和封闭 App 的天平上偏向着封闭。或许我们所熟知的开放 Web 真的只是昙花一现?// Regressive Web Apps adactio.com/journal/10708
Google force us to code regressive web apps #webdeveloper @adactio adactio.com/journal/10708
Chrome developers have decided that displaying URLs is not “best practice”. It was filed as a bug. A bug. @adactio ow.ly/qWKY3010IGf
adactio.com/journal/10708 @adactio my biggest concern is with “works only in Chrome” scenario. I am old enough to remember the Browser Wars…
Les Progressive Web Apps, le meilleur des sites et des apps natives? Ouais, ou pas en fait : goo.gl/y1Vz0H via @adactio
This is a great read: adactio.com/journal/10708
Regressive Web Appsl - adactio.com/journal/10708 @adactio
Regressive Web Apps adactio.com/journal/10708 via @Instapaper