Skip to content

Instantly share code, notes, and snippets.

@adewale
adewale / gist:6e2baa8fdea65108b257fe9fbdae3b77
Created August 23, 2016 15:10
Common misconceptions about Progressive Web Apps
Common misconceptions about Progressive Web Apps
They have to be SPAs.
They have to live at pwa.*.com
They have to be mobile only.
They're not allowed to be responsive.
They have to use material design.
They only work in chrome.
They don't work in safari or on iOS.
They have to look like your android app.
@marcoscaceres
marcoscaceres / single page apps
Last active March 13, 2017 14:23
This data is for applications that declare "apple-mobile-web-app-capable" (yes). It is an attempt to understand that installable web-app landscape. The data was taken from webdevdata.org. Of that 1097 sites contained the string "apple-mobile-web-app-capable", of which 360 sites where analyzed in this survey.
site,icons,mobile,navigates
10news.com,0,1,0
1x.com,1,1,1
220-volt.ru,1,1,0
22s.com,1,1,0
411.info,1,1,0
538.nl,1,1,0
a4academics.com,0,1,0
actressphoto.org,0,1,0
acuityscheduling.com,1,1,0
@grigs
grigs / gist:5778632
Last active September 24, 2017 08:49
Quick notes on TVs and standards

I need to write this up in more detail soon, but in chatting with Patrick, it is clear that 140 chars isn't cutting it.

The way I've been thinking about the web on TVs and consoles is something like this:

  • What are the design patterns and interaction models that would make for a successful experience?
  • Can we build those experiences now? If not, what would need to change to make it possible?

In my mind, this starts with the basics of designing an interface that works well on a TV and can be interacted with using a remote control. Once we have the basics out of the way, we can proceed to multiscreen interactions.

A basic television layout