Working on https://xitter.cf/t.co/KZE9FjYUmL. Former Director of Product Design @CreditKarma, leading design systems.
New York, NY
Joined August 2011
- Tweets256
- Following949
- Followers6.3K
- Likes8.7K
Jules Forrest retweeted
Brazil’s results tonight are a big endorsement for the idea that every country should have a second “are you you sure about that” election a couple weeks after the first one for the important stuff
Working in HTML artifacts has become such a powerful way to do "zoom in" / "zoom out" design work.
In my experience, design tools have subtly siloed distinct but interdependent design tasks. Because the tools are designed to give you the "best experience" for tackling each kind of problem, you often have to explore different design levers individually.
Instead of isolating design tasks like visual systems, layout choices and interaction design, HTML artifacts allow you to create custom levers to match whatever mental model you're currently using to solve a problem. And when you're done, you can just throw it away.
Today, I'm working on a new theme but also cleaning up some janky looking "just get the functionality in" screens. It's been so helpful to be able to jump between new vs. old theme and new vs. old design to verify the work along the way.
How many fonts is too many fonts for a single mobile app?
30%2
35%3
13%4
22%The limit does not exist
23 votes • Final resultsBecause who has the time to redraw all of those screens by hand anymore?
laidofflunch.com/p/drawing-w…
Had some fun experimenting with a film strip / contact sheet art direction for this week's Laid Off Lunch post.
Newsletter mortality aside, are people really connecting these agents to their primary email addresses?
I'm not there yet and not sure I'll ever be.
a big take I've been noodling on and I’m ready to call:
the newsletter is dead
@every's core business is a newsletter with 120k+ subscribers so I don't say this lightly.
persistent agents mean i dont look at my inbox
with dots (GrokBots, Muse, etc) I almost never look at my inbox. if I do it's for a specific thing I need to reply to.
i think in a year I'll be doing all of my email this way - fully filtered by my dot / something like it.
this is not new: it's a continuation of the trend of having a “newsletter” folder in Gmail, but 10x more filtered.
what it means
It doesn’t mean people won't read newsletters, but it does mean that getting a person’s email is no longer the guarantee that you have a relationship with them that it used to.
luckily, with persistent agents (and AI coding more generally) there is an entirely new playing field to build relationships with readers. instead of fighting to get an email address, publishers and creators will need to make sure we're installed in our reader's agent harness of choice, so that they get directly notified when we do something new.
we're already starting to experiment with this @every with our MCP and the frontier alerts we send users of our slack agent (every.to/agent)
it's also more affordable than ever for publishers and creators to build their own platform ecosystem: you can have your own website, app etc. and you can use AI to publish 100x more high-quality stuff to your community—so we may see a world where many creators themselves are running their own little empires that have their own apps, feeds etc.
to be clear: It'll take a while before this actually happens, but the idea of getting someone's email creating a direct relationship with them is over.
here's a set of predictions I made 3 years ago about AI and media that panned out pretty well: every.to/chain-of-thought/we…
Back in corp land, we used to do the "press release" exercise to kick off projects. They helped align everyone on the vision, final outcome and impact we were looking to achieve before getting started.
I was curious if today's version of that exercise could be more visual and engaging by making a sizzle reel. Partly because I wanted an excuse to build this prompting skill and partly because it's a nice antidote to the daunting feeling I get when I finish a big spec, knowing there's a lot of work ahead to make it real.
Also, because it's fun. Here's one I made this week for our grocery list experience.
We're in a funny catch-22 right now... previously inaccessible skills like motion now "feel" accessible.
But to get to a useful result, you need to invest time in learning just enough about that skill to be able to creative direct it... which is not easy or free.
So then you're distracted you from whatever you were trying to do in the first place, you know it's still not "professional" quality but it's tempting to invest more time learning to be get to professional quality, and on and on and on.
In the middle there, I was feeling stuck thinking about traditional checklist type experiences and tried out the new Venmo feed design layout on for size to get unblocked.
Borrowing a layout from a completely unrelated type of experience is the best way for me to get out "designer's block." Lifting a layout exactly is almost never the right answer, but it does force me to mentally reshuffle the information architecture in a way that helps me see other possibilities I wasn't able to picture previously.
Just found @mattpocockuk's AI Coding Dictionary site which is a much better execution of a similar idea
aicodingdictionary.com
When you're a designer embarking on building something for yourself for the first time, you often don't know what you don't know when it comes to the technical architecture of how modern web and mobile apps get built.
It can be incredibly overwhelming to wade through resources and documentation that assumes you already understand the major technologies and building blocks in play.
I created the type of resource I wish I had when I was starting out, a tool explorer for both my computer's development environment and Al Dente's project setup. I wanted to be able to visualize my setup to see how all of the different pieces fit together.
Check it out here 👇
claude.ai/artifact/GTHQXoD32…