Every week I share a list of curated articles, resources and tools about UX, UI and mobile design, HTML, CSS, the web industry, process inspiration and more…
This week’s selection: resilient web design ebook, UX of textareas, SVG animations, FontsNinja tool, PWA builder tool, 7 design psychology fundamentals every designer should know, rediscovering information architecture, CSS width animation, 19 principles of User Interface Design, 9 tips to improve your UI, UX Strategies for Multiple Devices and Platforms, a list of 300 CSS properties, a lot of dataviz resources, design systems, CSS Online drop-shadows generator, etc.
Reminder: the amazing “Resilient Web Design” book by Jeremy Keith is available online, and offline. Also it’s a PWA so you can add it to your homescreen and read it wherever and whenever you want. Offline for the web is amazing
“Rediscovering information architecture” I’ve seen this happen a lot, the urge to move fast so that devs can start coding as soon as possible, designers becoming pixel pushers with almost no time to understand and structure the content and info. “Read the user story and design me a mockup for this part of the page” user story beeing a wish list of content that does makes zero sense without understanding business and user needs. So designers try to reverse engineer it to try to build an information that makes sense (ish) “As a user I want to see a 404 with a text that tells me that the page doesn’t exist so that I know the page doesn’t exist”, “As a user I want to have a list of X and a button to delete X so that I can open the X or delete them”. “Information architecture is the way that we arrange the parts of something to make it understandable.” But this is how you end up designing parts of content with almost no global pictures so it the end they might not make sense together. Bottom line: information architecture ♥️
“The death of design files” welcome to the prototyping and collaboration area. Well at least if you don’t work for a company that blocks any tools in the cloud. Otherwise it’s back to PDF export sent by mail and comments to collaborate 😁I’m joking around but this is a real problem. Devs get “Cloud” tools that can be installed on company servers like Jira and Gitlab. I wish we got the same for design collaborative tools, a version you can self host for such companies. Meanwhile you get creative and use the tools of the company. You learn to design user flows in PowerPoint. Wireframes in an Eclipse plugin. You use PowerPoint comments to give feedback on mockups, links within documents to create interactive prototypes you export in PDFs. Welcome to the pragmatic design world
“Dear Clients: Read this. Love, Designers.” I understand most of the frustrations here, I worked in web agencies but I also think that it’s our task as designers to educate clients about all of that and help them help us create the best work we can!
“Invisible design systems“, design systems reflect your company culture, before revisiting which color to use for calls-to-action, we first need to revisit the values our company holds.
“Our Design System is a Meeting” I get the feeling that that it’s like in many places especially when you have different design teams and technologies. In the end, it’s all about findings ways to better communicate with the rest of the teams
“Some Imaginary CSS” yes, yes, yes for container queries, those would have saved me so much time when I used to still code for a living ❤️ (those days I just code for fun on the blog and to build quick animations prototypes for my FrontEnds ^^)