Pinned Tweet
Demo of Lofi - a FREE wireframing tool. I’d love to hear your feedback! 🙂 No sign-up required, and your data is saved locally on your computer. Link in comment
1
2
461
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.
1
2
337
To start the build, I wanted to try something different: getting different AI models to pitch me solutions. I copied and pasted this post for context and told the models I’d go with whoever gave me the best answer. I tried three models: Grok 4: This model understood the pitch best and worked the hardest. But it only expanded on my thinking. It didn’t bring any new or great ideas to the table. Sonnet 4: It didn’t try very hard. It just built on my thoughts and suggested practical ways to implement what I already had. Nothing new here either. OpenAI o3: This one didn’t even try. Total nothing burger. I ended up going with a recommendation from Grok 4, take a premade system (Shadcn), parse it into LoFi’s JSON format, and build on top of that. I gave Grok 4 the job. I did a pretty bad job parsing the components though, so I scrapped the build and started over with another model. I tried Sonnet 4 again. It failed too. I’ve concluded that these AI models are struggling because they aren’t familiar with LoFi’s layout system. They don’t know what 'good' looks like, so they can’t automate the process properly. I’ll have to manually create a few solid examples first, then try automation again later. I need a new solution.
1
112
Since the AI model doesn’t know how to build good components with my system, I need to create an engine that lets me build components manually. Something like Figma could work. I decided to use the most expensive model, Claude Opus 4. I don’t have time to mess around, so the cost justified the time. I gave it a simple prompt: “Research the Figma components and variants, then see how you can implement a similar system for our app. No code, just a report.” I reviewed the report, adjusted things like where components should live, and simplified the scope. I gave it no UI or UX direction, mostly because I was lazy, but also because I was curious to see what a very expensive model would come up with on its own. I built a basic component system in about 15 minutes. If you’re wondering what UX quality the most cutting-edge model can produce without guidance, here’s your answer: it looks like shit. So, designers, you can keep your jobs for now. UX doesn’t matter that much at this stage. What matters is that the code is in the right place and the foundation is solid. From here, I’ll just keep shaping it. Design feels a lot like sculpting to me these days.
1
112
🚢 Shipping new feature this week: AUTO LAYOUT. Took about a week, a lot of swearing, and not much sleep. Wouldn’t recommend building it urself.
109
Demo of Lofi - a FREE wireframing tool. I’d love to hear your feedback! 🙂 No sign-up required, and your data is saved locally on your computer. Link in comment
1
2
461
Hi, I’ve been building this FREE wireframing tool every night while my kids are asleep. If you need a simple app to make wireframes, please check it out, more to come, feedback welcome :) lofi-design.com/
1
102
I'm launching a FREE wireframing and ideation tool soon. Do you like the bottom toolbar?
106
MagicBook is the most fun way to create AI illustrations. It’s inspired by the charm of scrapbooking, hands-on, personal, and a little imperfect. I could automate everything, but I believe there’s magic in putting together something yourself.
1
1
104
I wanted to bring the idea of scrapbooking into my app. On MagicBook, you can drag things onto the canvas, press a button, and it creates an image based on your moodboard. This adds more friction to the process and makes things slower, but the friction is intentional. It creates a moment to pause, reflect on the work, and enjoy the process of making.
1
116
I’m not building this app. Instead, I’ll write a brief for the AI, let it do the work, and review it the next day. Will report back.
81
MagicBook is a print design app, like InDesign but with AI. Building the system that handles single and double-page spreads, auto-save, and page reordering was the most technically challenging thing I’ve ever built. I failed three times. On the fourth try, just after midnight, it finally worked (for now).
1
100
Made my first book with MagicBook today. This one’s not so kid-friendly tho.
64
Just wrapped up the new toolbar for MagicBook, finished it just after midnight. I’m a woodworker, and I’ve been trying to sneak a bit of that vibe into the app for a while. I'm not working within a design system, winging everything.
64
Making my first app just for fun
Most vibe-coders are out here building apps to make millions. I’m just trying to make an app so I can print silly little books to read to my kids. While everyone’s chasing features to get more users, I’m over here pulling midnight shifts building whatever sparks joy, like Marie Kondo but with more code and less sleep.
4
141
Most vibe-coders are out here building apps to make millions. I’m just trying to make an app so I can print silly little books to read to my kids. While everyone’s chasing features to get more users, I’m over here pulling midnight shifts building whatever sparks joy, like Marie Kondo but with more code and less sleep.
2
371
My take? The app logos don’t matter that much. As long as it doesn’t look like a penis, it’s fine. I made this one manually in under 30 mins because I had a vibe in mind. Used to spend days on this stuff, only designers care. What do you think?
1
107
How I made the MagicBook logo in Figma (in under 30 mins) Step 0: Hunt for inspiration. This one’s loosely inspired by Apple’s iconic “Hello” gradient. Step 1: Draw an oval. Step 2: Outline it, slice it up like digital sushi. Step 3: Duplicate the line and give it some oomph. Step 4: Add a loop. Step 5: Sprinkle in a star. Everything’s better with ✨ Step 6: Chop the line into five pieces, gradient them like a rainbow on LSD finesse the layout, and throw in some texture for that final chef’s kiss.
1
135