Like, just a post complaining that screens should be better An Article by Matt Webb interconnected.org It’s been 19 years since Pixar released Monsters, Inc. with all that CGI hair. Where are my hairy icons? Ones that get all long and knotted as the notifications number goes up. Why can’t I feel my phone? I found that paper from 2010 (when I was complaining about keyboards) about using precision electrostatics to make artificial textures on touchscreens. I should be able to run my thumb over my phone while it’s in my pocket and feel bumps for apps that want my attention. Touching an active element should feel rough. A scrollbar should *slip. Imagine the accessibility gains. But honestly I don’t even care if it’s useful: 1.5 billion smartphone screens are manufactured every year. For that number, I expect bells. I expect whistles. A Brief Rant interactionsoftwareinterfacesdevices
Clues for software design in how we sketch maps of cities An Article by Matt Webb interconnected.org Given there’s an explosion in software to accrete and organise knowledge, is the page model really the best approach? Perhaps the building blocks shouldn’t be pages or blocks, but neighbourhoods roads rooms and doors landmarks. Or rather, as a knowledge base or wiki develops, it should - just like a real city - encourage its users to gravitate towards these different fundamental elements. A page that starts to function a little bit like a road should transform into a slick navigation element, available on all its linked pages. A page which is functioning like a landmark should start being visible from two hops away. The Image of the City urbanismcitiessoftwareunderstanding