Excellent advice (as usual) from Jonathan Snook. Although, based on the project—such as a limited-scope site with a tight size limit—you may want to define almost everything as base styles. As with everything on the Web, it depends.
The Best of the Internets
Alex Russell discusses Chrome’s Progressive Web App prompting strategy and discusses what’s next.
An excellent collection of Gulp plugins for optimizing the living heck out your CSS.
Parker looks like an interesting tool for general information about your CSS, but you should take its reporting with a grain of salt.
An excellent post from Ada Rose Edwards on Progressive Web Apps. She’s brings up some very real concerns, many of which I share:
- The basis for what Chrome defines as a Web App is based upon a set of technology rather than a set of features.
- We need to consider carefully before we throw away URLs or the entire browser chrome in an effort to look like and behave like the cool kids of native.
- The install banner is the browser manufacturers’ choice; it’s not a spec.
Moving in this direction poses a lot of problems for terrestrial data. It could also increase the digital divide.
Ratcheting prices up further will only increase the digital divide, but the difference won’t just be between those who have Internet access and those who don’t. The cost of data limits could also divide the population between those who can take full advantage of high-bandwidth applications like streaming and video conferencing, and those who have to curb their usage for fear of incurring overage charges.
Another brilliant CommitStrip. My transcription follows.
A developer and his project lead are sitting next to one another.
It sucks Uncharted 4 is only available on PS4
…releasing AAAs on just one platform is unfair
- Project Lead (excitedly)
Yeah I guess, but it must be awesome for Naughty Dog
- Project Lead (smugly)
They only have to develop, test and maintain their software on one single platform
- Programmer (looking confused)
- Project Lead (emphatically)
Everyone has the same processor, the same amount of memory, the same resolution…
Just think about it…
- Programmer (shrinking)
…I don’t want to think about it
Pan out to reveal the large table they are sitting at. It is littered with mobile devices.
- Programmer (getting up and turning to leave the room)
Does anyone have a phone with Android 4.0.4?
- Project Lead (muttering to himself)
The benefits of single platform development are easily reaped by developers, but they come at a cost to the consumer who doesn’t have the right device or specs and (moreover) it limits a project’s potential reach.
This is huge! Many thanks to Steve Faulkner and Léonie Watson for compiling this information!
An excellent post from Dion Almaer on the importance of choosing the appropriate approach for the critical tasks of your web property. He dubs it “time to first meaningful interaction”. This is where progressive enhancement shines.
No, they don’t. Progressive enhancement, baby!
Images will be blocked. Styles will be filtered. Tables will be munged. Instead of struggling to try to make emails look the same everywhere, let’s embrace their differences.