Build Log 1: I’m kicking off my next big feature for LoFi: the component system.
While looking for inspiration, it feels like Figma’s system is still the only game in town. But to be honest, I’ve never liked how Figma handles components. Here’s why:
1. It makes the user work too hard
Take the humble Button component, probably one of the most standardised elements in any UI. Sure, the style and behaviour might vary slightly by platform, but 90% of the time it’s the same. So why make me build it from scratch?
You could argue Figma’s system is flexible for customisation, and sure, it is. But software isn’t plastic. You can offer full flexibility and ship components like buttons and forms with smart defaults and customisable options out of the box.
2. Too many dropdowns and toggles
The way we customise components is through toggles, dropdowns, nested panels, feels like a solved problem that no one’s bothered to rethink. What if components were context-aware and adapted to the environment they’re placed in?
This is a hard problem to solve. I’ll need to get back to you on that one.
3. Figma components are built for UI/Dev, not for design thinking
Figma’s components focus on structure,size, states. But they ignore design intent.
They don’t help you answer:
What makes a button convert better?
What tone or language should I use here?
When should I use urgency?
How should I pair buttons to guide decisions?
None of that is baked into the system. But it could be.
---
The Challenge
So yeah, the goal is to build a better system than Figma’s. No pressure. I’ve given myself 2-3 weeks to ship it. Can I pull off something creative? Honestly, I don’t know. This shit looks hard.
If you’ve got any ideas, throw them my way. I’m starting from zero here. lol.