Brilliant retweeted
meanwhile opus 5.5 high in @usebrilliant (4k closeups in comments)
What is the explanation for why models still cannot one-shot truly top notch UI design?
3
3
25
1,352
Brilliant retweeted
is everyone sleeping on Gemini 4 Argon for design? 🧵
I know, I know, making fun of gemini is extremely fun.
HOWEVER
Example 1: check out the detail and structure of the groovebox
I know, I know, making fun of gemini is extremely fun.
HOWEVER
Example 1: check out the detail and structure of the groovebox
5
5
31
2,494
Brilliant retweeted
UNGODLY levels of performance
250K+ elements, 1x speed, IN THE BROWSER
250K+ elements, 1x speed, IN THE BROWSER
5
3
42
3,312
Gemini 4 Argon, now available in Brilliant!
Try it here, free, no sign in required: brilliant.design/playground
Try it here, free, no sign in required: brilliant.design/playground
3
4
25
2,415
Brilliant retweeted
Why can't HTML/CSS-based canvases pose a threat to Figma?
The three rendering-engine choices and where each one breaks:
The three rendering-engine choices and where each one breaks:
Fine, I'll bite.
Paper will never, ever, eat Figma's lunch.
Not Paper, not Claude Design, not Google Stitch, not V0, bolt, lovable, base44 or any of the HTML/CSS-based canvas.
Why? The number one reason:
Performance.
Paper struggles at 2-5K elements of plain rectangles
For ched video: a small, early-stage exploration canvas with 13K elements.
Real-world projects are tens of thousands sometimes hundreds of thousands of elements.
Why do you think Figma has a hyper-optimized webGL rendering engine? It would've been way easier to have an HTML/CSS-based canvas if that was feasible.
Figma's money comes from tens of thousands of organizations where *at the very minimum* need to support these canvas sizes.
Does it hurt Figma that many individuals and small teams are switching to other tools? arguable.
Does Paper have better *MCP support* than Figma*? 1000 percent. Not even close.
but MCP support != better overall or even an option for most.
I'm not saying Figma's lunch won't be eaten.
I have a huge horse in that game, betting it will be.
I'm saying *HTML/CSS-based canvases, specifically* won't.
8
4
41
3,416
Brilliant retweeted
lol, this might be the best worst attempt I've seen at a hero design
muse wonder _full_ testing (1/4) 🧵
(the better one, not not-full)
muse wonder _full_ testing (1/4) 🧵
(the better one, not not-full)
Introducing Muse Wonder, our new family of frontier models with state of the art performance for personal and professional agentic work.
1
3
11
1,154
Brilliant retweeted
Fine, I'll bite.
Paper will never, ever, eat Figma's lunch.
Not Paper, not Claude Design, not Google Stitch, not V0, bolt, lovable, base44 or any of the HTML/CSS-based canvas.
Why? The number one reason:
Performance.
Paper struggles at 2-5K elements of plain rectangles
For ched video: a small, early-stage exploration canvas with 13K elements.
Real-world projects are tens of thousands sometimes hundreds of thousands of elements.
Why do you think Figma has a hyper-optimized webGL rendering engine? It would've been way easier to have an HTML/CSS-based canvas if that was feasible.
Figma's money comes from tens of thousands of organizations where *at the very minimum* need to support these canvas sizes.
Does it hurt Figma that many individuals and small teams are switching to other tools? arguable.
Does Paper have better *MCP support* than Figma*? 1000 percent. Not even close.
but MCP support != better overall or even an option for most.
I'm not saying Figma's lunch won't be eaten.
I have a huge horse in that game, betting it will be.
I'm saying *HTML/CSS-based canvases, specifically* won't.
Paper will never, ever, eat Figma's lunch.
Not Paper, not Claude Design, not Google Stitch, not V0, bolt, lovable, base44 or any of the HTML/CSS-based canvas.
Why? The number one reason:
Performance.
Paper struggles at 2-5K elements of plain rectangles
For ched video: a small, early-stage exploration canvas with 13K elements.
Real-world projects are tens of thousands sometimes hundreds of thousands of elements.
Why do you think Figma has a hyper-optimized webGL rendering engine? It would've been way easier to have an HTML/CSS-based canvas if that was feasible.
Figma's money comes from tens of thousands of organizations where *at the very minimum* need to support these canvas sizes.
Does it hurt Figma that many individuals and small teams are switching to other tools? arguable.
Does Paper have better *MCP support* than Figma*? 1000 percent. Not even close.
but MCP support != better overall or even an option for most.
I'm not saying Figma's lunch won't be eaten.
I have a huge horse in that game, betting it will be.
I'm saying *HTML/CSS-based canvases, specifically* won't.
61
11
248
45,370
Brilliant retweeted
been a minute since I shared some technical details on @usebrilliant, so here's a short thread about WHAT makes these incredible stats possible 🧵
1
6
17
1,228
Brilliant retweeted
Fuck it. Enjoy: brilliant.design/remove-backgro…
Free incredible background removal for the masses (mobile friendly)
Free incredible background removal for the masses (mobile friendly)
there's also a human interface btw
3
9
35
2,297
beta.101 is LIVE! A few incredible additions are now live:
Blazing fast Remove Background:
select an image (or a frame of images) and remove its background from the right-click menu, the inspector or the command palette, one undo step, Restore Background to bring it back, and er cut-out. Agents get it as a tool. Runs on Brilliant AI.
Blazing fast Remove Background:
select an image (or a frame of images) and remove its background from the right-click menu, the inspector or the command palette, one undo step, Restore Background to bring it back, and er cut-out. Agents get it as a tool. Runs on Brilliant AI.
1
2
18
4,935
Brilliant retweeted
The bull case for Figma (and Brilliant) and the future of product dev
Warning: long opinionated thread with hot takes.
If you're building a design tool you're likely going to disagree and I invite you to prove me wrong
Almost everyone building AI design is making the same bet:
at writing HTML/CSS" +
"My actual website is HTML/CSS" +
"No need to actually look at the code anymore"
= "The canvas should be HTML/CSS"
Incredible because:
"No handoff"
"HUGE unlock for building with AI agents"
"Manual control for craft and taste when needed"
"The product is fully interactive on the canvas"
This "aha" moment hits almost everyone thinking about the future of product development.
You and agents on the canvas which is also the code base.
Paper just raised $34M from Accel and ICONIQ on a similar thesis.
Claude design, google stitch, lovable, base44, bolt, MagicPath, wonder and likely 10,000+ other apps all reached the same conclusion and are building "the future interface of product development"
Here's where I completely agree with this thesis:
1. A canvas is an incredible god-view over a product for both humans and agents
2. The coding part of product development is on the trajectory of being fully managed and orchestrated with AI agents
Where I think the thesis breaks, and why Paper, and other tools will have a hard time becoming the future interface of product development:
Warning: long opinionated thread with hot takes.
If you're building a design tool you're likely going to disagree and I invite you to prove me wrong
Almost everyone building AI design is making the same bet:
at writing HTML/CSS" +
"My actual website is HTML/CSS" +
"No need to actually look at the code anymore"
= "The canvas should be HTML/CSS"
Incredible because:
"No handoff"
"HUGE unlock for building with AI agents"
"Manual control for craft and taste when needed"
"The product is fully interactive on the canvas"
This "aha" moment hits almost everyone thinking about the future of product development.
You and agents on the canvas which is also the code base.
Paper just raised $34M from Accel and ICONIQ on a similar thesis.
Claude design, google stitch, lovable, base44, bolt, MagicPath, wonder and likely 10,000+ other apps all reached the same conclusion and are building "the future interface of product development"
Here's where I completely agree with this thesis:
1. A canvas is an incredible god-view over a product for both humans and agents
2. The coding part of product development is on the trajectory of being fully managed and orchestrated with AI agents
Where I think the thesis breaks, and why Paper, and other tools will have a hard time becoming the future interface of product development:
every design app now (working on this too lol)
7
3
58
7,047
Brilliant retweeted
there's also a human interface btw
blazing fast background removal, in the upcoming version of @usebrilliant
1
3
11
3,319
Brilliant retweeted
blazing fast background removal, in the upcoming version of @usebrilliant
3
4
15
1,724