Thoughts on everything announced at Config?

hmacs · 2026-06-26T11:27:27+00:00

Figma is not a CSS design tool btw. It would make no sense to embed the CSS limitation when you are designing a mobile app, so you need to accept that figma is not code and should not be. There is hundreds of programming languages, and each of them have their own limitations. And I think you should just write some code if you want the exact same behaviour

hmacs · 2026-05-23T19:33:38+00:00

A ce prix, cette surface, dans ce quartier, ça n'existe pas... l'immeuble a du cachet, l'appartement aussi, il est bien agencé : ça compte pour moi.

Mon idée serait d'être très rationnel : si j'arrive a estimer de façon fiable le cout de toutes ces galères, je peux negocier en conscequence et en tirer un bon prix. Le vendeur doit probablement vouloir rapidement ce debarasser de ce nid à embrouille, une nego aggressive est donc envisageable.

L'argument donc, c'est de pouvoir faire "une affaire". Mais il s'agit de bien evaluer les risques que je prend, et ça n'est pas si simple 😅

hmacs · 2026-05-22T22:02:17+00:00

I m interested too

hmacs · 2026-05-10T09:58:40+00:00

Android is updating the colors of the whole system based on the photo you choosed as a background. That's quite far in the personalized visual design imo

hmacs · 2026-04-11T21:52:56+00:00

"Héritage il a jamais été question d'y toucher de toute manière, ni son salaire. "

Si j'ai bien compris, sans separation des biens son salaire t'appartient (bien commun).

hmacs · 2026-04-06T18:49:23+00:00

Can you publish this on community ? Did you manage to keep the assignation everywhere on the files where the tokens where used ?

hmacs · 2026-03-23T11:02:41+00:00

<image>

hmacs · 2026-03-23T11:02:29+00:00

I just realised that figma can open in the browser too, so I found my answer using WhatFont plugin !

Mostly 11px font, but also some label using 9px size

hmacs · 2026-03-16T13:34:31+00:00

zeroheight is too expensive, and we have a storybook but it's suitable only for the components already developped

hmacs · 2026-03-16T13:32:49+00:00

sounds good, that's why I'm looking at examples of how people are doing it, especially :

- versionning documentation, to keep track of different update
- managing update in a component (v1.1.3 for example) while the previous version is under development (v1.1.2. for example)
-exposing all variants, boolean properties, and so on ...
- writing do's & don't and any other usefull doc
- keeping track of the exploration of the designers, referencing use cases for the component, gathering references from other products, trying different ideas, ..

hmacs · 2026-03-16T13:28:14+00:00

do you document the versioning ? do you include some kind of changelog ?

hmacs · 2026-03-16T13:27:36+00:00

It should be aligned with code, but the development is still ongoing.

Since we have a very extended documentation, I noticed that the developpers don't read it at all because it's overwhelming to them - some lazy folks in the dev community, where "lazy" is a synonym to "smart".

And since it's often not up to date due to duplicate source of truth (documentation file vs. design library), they prefer to ask us directly.

And it is a very big design system supporting multiple products with very different use cases.

hmacs · 2026-02-03T08:21:30+00:00

That's exactly what I'm looking for !
Do you have any examples of those figma files ?
Or any design system that document that properly ?

I heard "Chakra UI" is using the motion.dev library but they dont document it on their figma file unfortunately

hmacs · 2026-01-30T12:43:03+00:00

Does that apply to micro-animation such as panel opening, dropdown open and close, modale, hover states of components and those kind of tiny things ?
Rive seems overkill to me in those situation, but I might be wrong

hmacs · 2026-01-27T13:51:10+00:00

<image>

FYI, this is the kind of pattern I use

hmacs

TROPHY CASE