Pinned Tweet
The floating @framer window. Many design tools have them. You don’t want them flying out of the screen bounds. Did you know that you can fully rely on CSS for the constraints? Checkout the thread to learn how to implement the dragging, constraints, and rubber banding.
We just shipped one of the most-requested features in @framer: Lists. It’s one of those rare 1,000-in-1 releases. A single feature that unlocks countless new possibilities. Huge thanks to @edoardomercati for the amazing design. Check it out now!
We just shipped a new CMS field in @framer that makes managing lists much easier. Works great with repeating content like FAQs, features, and case studies. And it includes full API and Agent support from day one! ✨
Lost all trust in @claudeai CLI when its using 21 million tokens for a simple code review. Other harnesses don't behave like that.
Astra helped me quickly build a working prototype in our massive codebase. Then I spent the next day trying to land the actual changes. Wow, so many weak engineering decisions. If this is AGI, it’s a pretty junior and lazy AGI
AI translating restaurant menus in Spain: basically flawless.
AI translating restaurant menus in Sweden: confidently making up every single dish.
Luckily, the waitress saved us.
This guy is on a rolllllll…
I’m in the final stages of building the next version of @framer’s agent harness. It’s getting so good that I’ve become convinced that any teams paying attention will reverse engineer and copy its key innovations within a month. Not giving any hints, but you’ll be able to tell if agents suddenly get faster, more responsive, and use less tokens. More soon.
Heading to Copenhagen at the end of August with my wife and our dog, Flossie. We’d love to discover some incredible food while we’re there. Any must-visit restaurants, bakeries, cafés, or hidden gems that are dog-friendly? 🍽️🐶
ALT Our dog Flossie in the Barcelona harbor on a windy day
Great workflow unlocks from our new branching solution 👇
On our biggest client builds, 15–20 people touch the same @framer site in a single week: designers, copywriters, content editors, strategists, etc.
A few months ago that still meant one shared canvas and a lot of "don't publish yet, I'm still working on something."
Framer Branching finally fixed that.
How we use branches at @TrueformCo:
→ One branch per work stream, not one giant shared file.
→ Branches are our new client approval tool.
→ Big AI edits go on a branch. Always.
→ CMS migrations and bulk imports from external agent stay contained.
→ Creating different design directions in branches.
→ Production never freezes.
A few tips if you run a bigger team:
→ Name branches like a team or feature, not new-22 or final-final.
→ Give "apply to main" an owner/gate-keeper.
→ Keep branches short-lived.
→ Use the changelog as your client update.
Speed comes from the agents. Control comes from branching. For a team in our size, that second half is the part that actually made AI usable on real client work.
Great example how the new agents in @framer make templates easier to use👏
@Framer launched 3.0 and I personally think it's a new era for web design. Let me tell you why.
Right after the launch, they kicked off a 24-hour hackathon dedicated to the new features. I decided to participate, and here's a thread about it 🧵
I promise it gets interesting!
Branching. A last minute feature that made everything else we shipped today better. Curious for all of the workflows this is going to unlock…
Fun fact: @framer branching shipped due to agents. After some initial user tests we realized people didn't trust / grasp undo for agents yet, so they were hesitant to try it on real projects.
We had just rebuilt our projects on CRDTs which allowed us to build great branching in six weeks. It has some cool details like never having merge conflicts, and therefore you never have to rebase (we keep it updated with main).
Great outside perspective on the why’s of our @framer release today 👏
they did it. they fucking did it.
i am AGASP seeing what this amazing team has pulled and the tremendous value they keep bringing to the community.
let me explain, it is not a secret that to a lot of us the rapid advancement of ai has been a blessing and a curse.
sure, you can ship faster, but that inevitably lowers down the overall quality output and process that a lot of creators put into their work, bastardizing their craft by leaving ai do all the thinking for them... this isn't that.
they very thoughtfully made such a smooth integration with LLMS where they LITERALLY looked at all the boring shit that's part of the design workflow and said "let's make this better".
you can skip through the 1% that feels like going from 92 to 99 in runescape (iykyk) and still have complete control over your work, actually empowering and boosting your already existing workflows instead of replacing them !!
some use cases they shared:
- adding staggered animations to pages
- making different component variations
- MAKING PAGES RESPONSIVE HELLO
- adding styles to pages and finding layers without styles
- tagging layers, pages and styles to update
- light and dark theming
- reverting and applying changes to iterations
- creating different versions
- creating style pages
- iterating on components / sections
- switching up repetitive copy and placeholder images
- running audits to check for seo and accessibility
OUT OF WORDS, THIS IS WHAT AI WAS SUPPOSED TO BE ABOUT, GETTING RID OF THE BORING SHIT SO WE CAN FOCUS ON WHAT MATTERS, GODSPEED @framer LFGGGGGGG! ⚡
For scroll-linked layouts, staying perfectly in sync means letting CSS handle the layout. Luckily position sticky is a lot more capable than you might think. Here is a prototype I made @framer
Great thread about the engineering behind our super easy to use analytics
Did you know @framer analytics works without cookies or localStorage?
We do not store per-visitor state on the server either. Only events, tied together using a hash derived from the request plus a salt that rotates daily.
Here’s how it works..
