Issue #169: Modal vs Page 🤔, GPT-3 Crush 🤖 , and UI Kits 💎

Modal vs Page ❓, GPT-3 Crush 🤖 , and UI Kits 💎

Image: Adobe React Spectrum

Finding a starting point for a project can be daunting: from organising design files to ensuring UIs are accessible, a messy start can lead to a lot of extra work. With that, here’s a few new things we saw this week that can help out:

⚛️ Adobe React Spectrum Libraries: great for teams lacking the resources to prioritize accessibility, internationalization, keyboard and touch support.
🎨 Stark just announced ‘Smart Suggestions‘ to take the guesswork out of accessible colour selection.
📂 Stay organised with this Figma File Setup Template by Femke!

Check out this week’s Toolbox for more UI Kits and component libraries. 👇

This Week in Toolbox

See all →

Projects we loved this week:

Reading List

See all →

Modal vs Page: A Decision Making Framework →

Ryan Neufeld

There are no definitive rules for using models, only a set of recommendations and guidelines. Ryan introduces his own decision-making framework to help us choose when to use a modal, and when to use a page.

100 Days of UI — Should You Take One Up? →

Sophie Clifton-Tucker

From 100 Days of Code to Daily UI, working on your craft is not too dissimilar to practising a musical instrument; if you’re consistent, you’ll get better, things will get easier, and you’ll probably enjoy it more.

Remote working in design: Part 2 of a Design Sprint Trilogy →

Olivia Peacock

Are we building a remote design culture? What are the challenges of remote design work? Olivia explores the impact COVID-19 has had on the design process, with the insight of industry experts.

Choosing the right UI component for communication with your users →

Adam Shriki

Check out Adam’s ‘friction scale’ 📏! A tool to rank UI components by the level of friction they create for users. In this article, he explains how to choose the right UI component depending on the type of message you’re sending to your users.