In short
Most UX reading lists are graveyards: dead blogs, recycled trend copy and forty newsletters nobody opens. We checked 20 active UX blogs and news sources on 29 September 2026 and sorted them by the job they do: research, platform rules, craft, product strategy and industry news. Each gets its best use, its weak spot and a reading habit, plus weekly stacks for beginners, working designers and product leaders.
In this article
- How we picked these 20 UX blogs and news sources
- Research and evidence: sources that test before they talk
- Platform rules and public-service practice
- UI craft, front-end and design systems
- Product thinking and strategy
- Industry conversation and weekly UX news
- Three weekly reading stacks
- What ANODA does with the decision the reading leaves open
- Turn reading into decisions, not redesigns
The best UX blogs are not the ones that publish the most. They are the few that make your next product decision better: research you can cite, platform rules straight from the platform, craft you can ship, and product thinking that survives a budget meeting. Everything else is noise with a nice font. We checked every source below on 29 September 2026, noted who is behind it, how recently it published and what it costs, and cut anything that had gone quiet.
At ANODA, we design and fix products around the decisions that matter, and we have watched plenty of teams drink from a fire hose. Forty newsletters, three Slack channels of “must-reads”, a Monday tab graveyard. Nobody is better informed. They are just tired, and the product still loses the users the company paid to acquire, because nobody on the team spent those hours watching a real person fail at signup.
Do the arithmetic. Five designers skimming feeds for an hour a day add up to more than half of one designer’s working year. If none of that reading changes a decision, you are paying a salary for scrolling.
Reading about UX is not doing UX. Watching match highlights has never made anyone fitter.
How we picked these 20 UX blogs and news sources
Sturgeon’s law says ninety percent of everything is crap. Design content is no exception, and AI has made the crap cheaper to produce. So we filtered hard. A source made the list only if it passed these checks on the day we looked:
- It is alive. A dated post in 2026, most of them in the last few weeks. A dead blog is a satnav that has not been updated since 2019: confident, detailed and steering you into a road that is now a pedestrian zone.
- Someone accountable is behind it. A named research firm, practitioner, editor or public body. Not a content farm with a stock-photo “team”.
- It adds something beyond recycled trend copy. Research, primary guidance, working experience or real editorial selection.
- Depth, archive and signal-to-noise. Would you search its archive before a design argument? Does one good post come with three sales pitches?
- Level, format and cadence fit a job. Beginners, working designers and product leaders need different diets.
Then we sorted by reader job, not by fame. Every entry below says what it is best for, why it earns a place, where it falls short and how to read it without drowning.
One rule sits above the whole list. Primary platform guidance and credible research outrank any trend roundup, including ours. A building code beats your neighbour’s opinion over the fence, however confident the neighbour sounds.
Research and evidence: sources that test before they talk
Start here if a decision will cost real money. These five publish findings, methods and measurement, which is the closest a blog gets to a lab. They are also the cheapest insurance you will ever buy: an evening with the right study costs less than one sprint spent rebuilding the wrong screen.
Nielsen Norman Group
Founded in 1998 by Jakob Nielsen and Don Norman, and still the reference shelf most design arguments end on.
- Best for: research-backed guidelines and plain explanations of UX methods.
- Why it earns a place: free articles, a huge searchable archive and a steady pace: six new articles in the three weeks before our check.
- Where it falls short: the advice is general by design, and courses and reports are the business. Its September 2026 run was almost all AI.
- How to read it: one article a week, chosen by the problem on your desk, not by what is new.
Baymard Institute
E-commerce UX research, done at a depth most shops never pay for.
- Best for: checkout, product pages, listings and anything that touches a basket.
- Why it earns a place: practical, evidence-led posts, several a month, most recently on 24 September 2026.
- Where it falls short: everything is seen through e-commerce, and the free posts lead to paid tools, audits and certification.
- How to read it: before anyone touches your checkout, not after conversion drops.
MeasuringU
The quantitative corner: metrics, surveys, sample sizes and the maths of UX research.
- Best for: anyone about to put a number in a report.
- Why it earns a place: a new article every week through August and September 2026, grounded in method rather than mood.
- Where it falls short: it tells you how to measure, not what to build, and some posts need a statistics refresher.
- How to read it: search it when you plan a study or defend a metric.
Jakob Nielsen on UX
Nielsen’s own Substack, separate from the firm he co-founded, and prolific.
- Best for: fast takes on where AI and usability meet.
- Why it earns a place: four decades of usability work behind the opinions, and several posts a week in September 2026.
- Where it falls short: it is one person’s view at high volume, and the roundups mix research with commentary. Full access needs a paid subscription.
- How to read it: skim roundup headlines and keep only the long essays.
UXmatters
A web magazine for UX practitioners, published since 2005 and edited by its founder, Pabini Gabriel-Petit.
- Best for: long practitioner essays on research practice, information architecture and design leadership.
- Why it earns a place: new issues roughly every two weeks, with issues on 7 and 21 September 2026, and no paywall in sight.
- Where it falls short: quality varies by author and the pieces are long.
- How to read it: scan each issue and read the one article that matches your current project.
Platform rules and public-service practice
The sources nobody puts in a top-ten list, because they are not exciting. That is exactly why they save money: they tell you the rules before you pay to break them.
Apple Design: What’s new
Apple’s changelog for the Human Interface Guidelines, design kits and design videos.
- Best for: iOS, iPadOS, macOS and visionOS teams who want the rule, not a blogger’s reading of it.
- Why it earns a place: it lists every guidance update and new resource, with fresh entries in September 2026.
- Where it falls short: Apple only, and a changelog explains what changed, not whether it suits your product.
- How to read it: once a month and after every Apple event, before the trend pieces start.
Design in Government
The UK government’s design blog, written by designers across public services.
- Best for: service design, content design and designing for people who cannot choose a competitor.
- Why it earns a place: honest write-ups from people designing public services, including a June 2026 post on designing for people who have lost trust online.
- Where it falls short: slow. We saw three posts in 2026, and the context is public sector.
- How to read it: subscribe and let it arrive when it arrives.
WebAIM blog
Posts from WebAIM, a non-profit at Utah State University working on web accessibility since 1999.
- Best for: practical accessibility judgement, plus its WebAIM Million report on homepage accessibility errors.
- Why it earns a place: specialists who have worked on accessibility since 1999, writing plainly. The latest dated post was in August 2026.
- Where it falls short: posts are occasional. The deeper value sits in its articles and reports.
- How to read it: follow the blog and read the Million report when it comes out.
UI craft, front-end and design systems
Where design meets the code that ships. Beginners over-read this shelf and under-read the research one.
Smashing Magazine
Long-running magazine on UX, CSS, accessibility and front-end.
- Best for: detailed how-tos where interface design meets implementation.
- Why it earns a place: substantial articles several times a month, most recently 16 September 2026, from working practitioners.
- Where it falls short: a large part of the feed is for developers, and membership, books and workshops are the business.
- How to read it: filter to UX and design articles; send the CSS ones to your front-end lead.
A List Apart
A magazine about the design, development and meaning of web content, online since 1998.
- Best for: essays on the craft and ethics of the web.
- Why it earns a place: thoughtful pieces that age well, the latest published 30 June 2026.
- Where it falls short: a handful of articles a year now. Essays, not news.
- How to read it: keep it in your RSS reader and read each piece properly.
LukeW
Luke Wroblewski’s long-running site on digital product design.
- Best for: interaction patterns, mobile and, lately, AI interfaces.
- Why it earns a place: short, specific notes from a product designer, several times a month, the latest on 24 September 2026.
- Where it falls short: one author’s lens, and recent months are almost all AI.
- How to read it: skim in RSS and save the pattern posts for your next AI feature.
Brad Frost
The Atomic Design author’s blog on design systems and front-end workflow.
- Best for: design system thinking, from components to governance.
- Why it earns a place: practical posts from someone who has spent years on design systems, updated several times a month.
- Where it falls short: course promotions and personal posts share the feed.
- How to read it: follow the design-system posts, skip the rest.
Reading about design systems is like reading about wiring a house: useful, until someone has to decide who owns the fuse box. If your library of components already has three kinds of button and no owner, reading will not fix it. A governed design system built with your team will.
Design systems
Read enough about tokens and components? Your product still has three buttons that do one job.
We turn the principles into a working system: components, rules, owners and a way to change it without a civil war.
Figma blog
Figma’s own blog: product news, team stories and craft interviews.
- Best for: how teams run design work and design systems in the tool most of them use.
- Why it earns a place: about two posts a week, and many case stories name the teams involved.
- Where it falls short: it is a vendor blog. Three of the eight most recent posts were Figma product news or feature stories.
- How to read it: read the case studies, skip launches unless you will use the feature this quarter.
Product thinking and strategy
Designers who skip this shelf get outvoted in roadmap meetings. Product leaders who read only this shelf get products nobody can use.
SVPG
Silicon Valley Product Group, with articles mostly by Marty Cagan.
- Best for: the product operating model, empowered teams and product leadership.
- Why it earns a place: a clear, consistent position, with new articles every few weeks, most recently 25 September 2026.
- Where it falls short: opinion, not data, and the firm sells workshops and transformation work.
- How to read it: once a month, then argue about it with your product lead.
Lenny’s Newsletter
Lenny Rachitsky’s newsletter on building product, growth and careers, with over a million subscribers.
- Best for: product management and growth practice from named practitioners.
- Why it earns a place: weekly issues with guest experts, plus a podcast.
- Where it falls short: every issue, the archive and the community sit behind a paid subscription, and design is a side topic.
- How to read it: read the free issues. Pay only if you will use the archive.
The Beautiful Mess
John Cutler’s newsletter on how product organisations actually behave.
- Best for: product leaders untangling rhythms, planning and team structure.
- Why it earns a place: about weekly, free, and honest about the mess every company pretends it does not have.
- Where it falls short: abstract for designers who need a pattern by Friday.
- How to read it: one issue a week with coffee, shared with whoever runs planning.
Mind the Product
Product management community with articles, a podcast and conferences, owned by Pendo.io.
- Best for: day-to-day product practice from many practitioners.
- Why it earns a place: almost daily posts in late September 2026, and the editorial content is free.
- Where it falls short: many contributors mean uneven quality, and the owner sells product analytics.
- How to read it: take the newsletter, pick one article, ignore the rest guilt-free.
Industry conversation and weekly UX news
This is the shelf people mean when they search for UX news. It is useful, and it is also where trend copy breeds. Many voices, more heat than light.
UX Collective
An independent design publication founded by Fabricio Teixeira and Caio Braga, with a weekly newsletter.
- Best for: the pulse of what designers are debating this week.
- Why it earns a place: a curated weekly issue, the latest on 28 September 2026, plus stories from many outside authors.
- Where it falls short: volume and uneven quality in the stories. Opinion pieces dominate.
- How to read it: the newsletter only, once a week.
Sidebar
Five design links every weekday, collected since October 2012.
- Best for: a two-minute daily scan.
- Why it earns a place: ruthless brevity and a living archive, updated on 28 September 2026.
- Where it falls short: links, no analysis. It was created by Sacha Greif and is maintained by Fabricio Teixeira, who also edits UX Collective, so expect overlap.
- How to read it: daily if you like, or weekly by newsletter. Never both.
UX Design Weekly
A weekly newsletter of hand-picked UX links, curated by Kenny Chen.
- Best for: one email that covers the week’s UX reading.
- Why it earns a place: issue 607 went out on 28 September 2026, which is the kind of consistency most newsletters abandon by issue 30.
- Where it falls short: a list of links with sponsor slots. The judgement is still yours.
- How to read it: ten minutes on Monday, open two links, close the rest.
Curated feeds overlap. The same viral post turns up in three newsletters, then again in your team chat with “have you seen this?”. Subscribe to all of them and you are paying in attention three times for one article.
For visual inspiration rather than UX thinking, we keep a separate list of the best UI design blogs. Different job, different shelf.
Three weekly reading stacks
Nobody needs all twenty. Following every source on this page is being a jack of all trades and master of none, with a reading list instead of a portfolio. It is the pupil who highlights the entire textbook in yellow: every line marked, nothing learned. Pick the stack that matches your job, give it a fixed slot and protect that slot like a client meeting.
If you are starting out. One Nielsen Norman Group article a week, UX Design Weekly on Monday, one Smashing Magazine design article, Apple’s What’s new once a month and WebAIM when it posts. About an hour a week. You learn the vocabulary, the methods and the rules before you learn the fashions.
If you design for a living. Research by problem from Nielsen Norman Group, Baymard or MeasuringU, LukeW and Brad Frost in RSS, the UX Collective newsletter, platform changelogs monthly. About ninety minutes, most of it chosen by what you are designing this sprint.
If you lead product. SVPG and The Beautiful Mess, the free issues of Lenny’s Newsletter, the Mind the Product newsletter, one Nielsen Norman Group article on whatever your team is fighting about, and Jakob Nielsen’s headlines for the AI noise. Share one piece a week with the team and ask what it changes.
What ANODA does with the decision the reading leaves open
If your team has saved ten onboarding articles but new customers still stop before their first useful action, another subscription only adds to the bill. The next step is a clear decision about your actual users, your product and the flow that loses them.
ANODA connects research to that decision, prototypes the important states and carries them into the interface and handoff. In SEOSpace, our work connected onboarding, the web app and Chrome extension, with consistent task priorities and release design QA. Your team gets from a useful principle to screens people can act on. See the SEOSpace redesign and bring ANODA the flow your team needs to fix.
Turn reading into decisions, not redesigns
Here is where the money leaks. A team reads that everyone is doing bento grids, glass or an AI panel, and a quarter later the dashboard has all three. Activation has not moved, and the users you paid to acquire still leave at the same step. Trend-chasing is a magpie’s hobby: shiny things collected, nest no warmer.
We see this in almost every product we audit. The fix is to treat every trend as an input to test against your product, never as a verdict. Ask four questions. Who is this for? What evidence is behind it: research, a platform rule or somebody’s mood board? Which of our users and flows does it touch? What would we stop doing to make room for it? If nobody can answer the third question, it goes back on the shelf.
AI makes this sharper, not easier. It can summarise a thousand posts before lunch. It cannot tell you which paragraph applies to your onboarding, which evidence is thin, or what your team should stop doing. That still takes judgement, evidence and someone willing to prioritise. The map is not the territory, and a summary of the map is further still.
Then prune. Resource lists age quickly, this one included. Once a quarter, check each source’s last post, who owns it now and whether anything you read there changed a decision. If not, unsubscribe. It is the streaming subscription you forgot to cancel, except it bills you in attention, not cash.
Build your stack by purpose. Check dates and primary evidence. Drop the dead sources. Treat every trend as a question for your product, not an answer. For practical guidance organised around product decisions rather than headlines, keep reading the ANODA UX blog.
UI/UX design
Done reading? Your product’s problem is still waiting on a real screen.
Show us where users drop off. We turn research, flow decisions and interface states into a clear plan for your product, your team and your constraints.
Written by
