Hacker News Reader

Comment by franze | Hacker News Reader

ok, just to get this straight

if a publisher want to do everything right in todays internet, they need

  * a responsive website
  * with views for desktop, mobile and tablet 
  * optimized for search, social and conversion
  * optional: augmented with schema.org
  * an iphone app (one or more)
  * an android app
  * optional: tablet/ipad app 
  * facebook channel 
  * twitter channel 
  * youtube channel
  * pinterest presence 
  * whatsapp presence
  * snapchat presence 
  * one or more newsletter
  * constant A/B testing

now add

  * facebook instant articles
  * google amp pages

did i forget something?

yes page bloat, third party crap and webperformance is a serious issue for users and publishers, but solving it with throwing another half baked technology at the publishers will not work.

it's cHTML all over again https://en.wikipedia.org/wiki/C-HTML

AMP solves the right problem with a non solution.

View on HN

The second point is a restatement of the first:

* a responsive website

* with views for desktop, mobile and tablet

#3 and #4 are similarly redundant

#1 makes all of the apps unnecessary, along with AMP and Facebook Instant. See also the dismal return on the sunk cost for developing apps: http://techcrunch.com/2015/07/23/i-dont-want-your-app/

The real omission, however, should have been #0: “high-quality content”. Sure, you see the NYT, NPR, Guardian, et al. post a lot on Twitter, Facebook, etc. but they were already some of the most popular content on the web and would have been widely shared either way.

franze probably intended "responsive" to have its dictionary meaning - "not sluggish".

It's possible but in the context of web design “responsive” has had a specialized meaning for many years, going back to a very influential article in 2010 which grouped older practices under that term:

http://alistapart.com/article/responsive-web-design

It's somewhat unlikely that anyone working in front-end development in 2016 would assume the generic usage.

Nope. Responsive as in "Resppnsive website". But instead of views I should have written "breakpoints". Said that: breakpoints get misused as device dependent views regularly, implementing complex .hidden CSS mambo jumbo. So yes, for me breakpoints are views (even if the should not be)

You forgot Apple News Format which is simply a convoluted way to turn HTML > JSON. https://developer.apple.com/library/ios/documentation/Genera...

I agree with the first half of your comment: publishers (as well as those who might support publishers, like devs, etc.) have so much to do nowadays. And while i care less about AMP being half-baked or not...I do feel it is a step in the right direction. If this works out, I think publishers (and devs) stand to benefit. Just think: if everyone gets on the bandwagon of improving performance for the sake of a better web experience, then the conventional web platform could win supreme again!

I am far from being an expert front end developer. I have found that a good match for my requirements and the amount of time I am willing to spend developing and maintaining my web sites is to simply use minimal Bootstrap themes and let media queries generate mobile and desktop versions of my sites.

Without too much hassle I can support all device types and as long as I am careful to use small image files and minimized JS and CSS, page load times are pretty good.

Is this the relevant XKCD comic?

https://xkcd.com/927/

I agree. This is why some pages are omitting social shares. And my understanding is amp does not work with Javacrip. That's a problem. Why does this sound like google+ all over again?

Reply on news.ycombinator.com