Hot nuclear blasts in your area.
(like Eric’s HYDEsim)
This is a fascinating way to explore time and place—a spyglass view of hundred year old maps overlaid on the digital maps of today.
A well-written (and beautifully designed) article on the nature of the web, and what that means for those of us who build upon it. Matthias builds on the idea of material honestly and concludes that designing through prototypes—rather than making pictures of websites—results in a truer product.
A prototyping mindset means cultivating transparency and showing your work early to your team, to users – and to clients as well, which can spark excited conversations. A prototyping mindset also means valuing learning over fast results. And it means involving everyone from the beginning and closely working together as a team to dissolve the separation of linear workflows.
A nice overview of the Payment Request API, which is getting more and more browser support.
A fascinating bit of cartographic reverse engineering, looking at how Google has an incredible level of satellite-delivered building detail that then goes into solving the design problem of marking “commercial corridors” (or Areas Of Interest) on their maps.
Language conjures the world into being.
Just type stuff.
Okay, this is somewhat odd …it looked like I was getting spam webmentions from an escort agency to an old post of mine. It turns out that technically it’s not spam—they’re genuinely linking to my post from this post on their blog which is actually about webmentions.
And that, your honour, is how this site ended up in my browser history.
A beautiful piece of writing from Virginia Heffernan on how to cope with navigating the overwhelming tsunami of the network.
The trick is to read technology instead of being captured by it—to maintain the whip hand.
I quite like this proposal for
geo element in HTML, especially that it has a fallback built in (like
video). I’m guessing the next step is to file an issue and create a web component to demonstrate how this could work.
That brings up another question: what do you name a custom element that you’d like to eventually become part of the spec? You can’t simply name it
geo because you have to include a hyphen.
Monica explains how Shadow DOM could be the perfect answer for scoping CSS:
Although, in a way, Shadow DOM is also another flavour of CSS-in-JS:
A handy tool with some pre-made CSS clip paths that you can then tweak to your heart’s desire.
I’m not sure the particular use-case outlined here is going to apply much outside of AirBnB (just because the direction of code-to-Sketch feels inverted from most processes) but the underlying idea of treating visual design assets and code as two manifestations of the same process …that’s very powerful.
Neither matters all that much and you can use every method on the same project without the universe imploding.
Some interesting approaches in the comments too.
These icons-as-a-service could be really useful for making quick’n’dirty HTML prototypes.
Cennydd enumerates what design sprints are good for:
- generating momentum,
- highlighting the scope of the design process,
- developing the team, or
- provoking core product issues.
And also what they’re not so good for:
- reliable product design,
- proposing sophisticated user research,
- answering deep product-market fit questions, or
- getting the green light.
I think it’s worth revisiting this post by Laurie on a regular basis for a shot of perspective and inspiration.
The web saved my life and then built me a new one. A single living entity, it touches everything in the world and is always getting better — and I can help. I owe it so much; if I can help it out, make it better in any small way, how can I possibly refuse? And if I can make it easier for other people to help make it better, then my efforts are multiplied.