Replying to @supremeUAA
the second one's thin points will vanish at favicon size, worth testing at 16px
1
1
9
Replying to @MrAlexTech @Blackmagic_News
putting progress % right in the inspector means no opening Fusion for every edit
1
1
392
Replying to @shmidtqq
random stacking is a hierarchy problem, someone still has to decide what moves first
7
Replying to @penguindsgn
building the texture from the same pixel blocks as the mark keeps it one system
1
18
Replying to @ktnr23
is the pixel-to-smooth swap a real shape morph in Figma Motion or a crossfade
1
33
Replying to @bowlcutWiz
good references still need the same constraints as the screen you’re fixing
2
Replying to @Creator_Toolbox
separate layers is the real news, a flattened vector is useless for motion
4
Replying to @Yoni_attlan
for client work I'd trust whichever one lets me fix one keyframe without rerolling
6
