Hey everyone

I m Krisna, a product designer based in Indonesia.

Most of my day-to-day work is thinking about how to improve design workflows and make systems easier to manage as products grow.

We often talk about design systems in terms of components and tokens.

But after working with large Figma files, I noticed that scalability often breaks down in much simpler ways:

Inconsistent naming
Duplicate components across pages
Deeply nested structures
Detached instances
Token usage drifting over time

Visually everything still looks fine, but structurally the system becomes harder to maintain.

As Figma files grow, structure quietly breaks.

Not visually structurally.

Naming gets inconsistent.
Duplicates pile up.
Tokens drift.
Design systems slowly lose discipline.

We realized there wasn t a way to objectively measure file health.

Hey I'm James, a software developer from Australia with 20+ years building things professionally.

Most of my career I've been the person behind the scenes solving hard technical problems, shipping reliable software, making other people's ideas work. Unravl is the first thing I've built entirely for myself, and now I'm figuring out the part they don't teach developers: how to actually get it in front of people who might find it useful.

No funding. No growth team. No playbook. Just me, the product, and a lot of learning in public.

If you've been down this road builder trying to find an audience I'd genuinely love to hear what worked for you. And if Unravl sounds like something you'd use, even better.