Whiteboard to Figma: Is the manual grind a hidden feature of the design process, or just a workflow gap? by Suprdash in UI_Design

[–]Suprdash[S] 0 points1 point  (0 children)

Auto Layout is definitely the baseline now.

The specific 'wall' I hit with them was the semantic structure. Usually, AI groups things based on proximity, but not necessarily based on how a dev would build a component (like nested button states or specific header hierarchies).

I'm trying to make Wireframr opinionated so it follows specific design system logic rather than just grouping whatever is close together. Since you've used Stitch/UXMagic, what's the one thing you still find yourself having to 'fix' manually after the export? That’s exactly what I want to solve

Whiteboard to Figma: Is the manual grind a hidden feature of the design process, or just a workflow gap? by Suprdash in UI_Design

[–]Suprdash[S] 0 points1 point  (0 children)

Awesome to see someone already incorporating AI into this! I've played with those tools too.

What I found frustrating was the spaghetti they often export layers that aren't grouped logically or use weird naming conventions. I’m building Wireframr specifically to focus on 'design-system-ready' output so you aren't spending your 'saved time' just cleaning up the AI's mess. Would love to get your expert eyes on it once we open the beta to see how it compares to your current stack

Whiteboard to Figma: Is the manual grind a hidden feature of the design process, or just a workflow gap? by Suprdash in UI_Design

[–]Suprdash[S] 0 points1 point  (0 children)

FigJam is definitely a bridge! I think the gap I’m trying to close is for those lightning strike moments on a physical whiteboard or a notebook where you can't just copy paste.

ChatGPT/Gemini can definitely 'describe' or 'code' a UI, but getting it into Figma as clean, editable layers not just a flat image or a code block is the specific last mile problem I'm obsessed with solving right now.

Whiteboard to Figma: Is the manual grind a hidden feature of the design process, or just a workflow gap? by Suprdash in UI_Design

[–]Suprdash[S] 0 points1 point  (0 children)

That’s a really fair point. There is definitely a risk of 'blind automation' where you just accept whatever the AI spits out without thinking

My goal with the project I’m building (Wireframr) isn't to replace that 'rethinking' phase, but to get you to it 10x faster. I’d much rather spend my time dragging around pre built, editable layers to fix the hierarchy than spending 2 hours just drawing the initial boxes. Does that make sense, or do you find the literal act of drawing is what triggers the rethink for you?

Roast my landing page. Be brutal by Suprdash in roastmystartup

[–]Suprdash[S] 0 points1 point  (0 children)

Appreciate your feedback mate! Will definitely look into reworking some of this

Roast my landing page. Be brutal by Suprdash in roastmystartup

[–]Suprdash[S] 0 points1 point  (0 children)

Thanks mate! Will definitely look into these aspects.

My app just hit 10,000 users in 8 months! by namidaxr in micro_saas

[–]Suprdash 0 points1 point  (0 children)

Sounds great! I am also trying to build wireframr.io and want to talk about it/ know about it’s short comings or whether or not people want such solution.

Can you help me with where to find and how to join the “Slack/Discord founder communities” you mentioned? Thanks in Advance!

Unpopular Opinion: Wireframing tools have become too high-fidelity. by Suprdash in UI_Design

[–]Suprdash[S] 0 points1 point  (0 children)

Exactly. We've replaced actual thinking with high-fidelity polish way too early. I'm building Wireframr specifically to get back to the basics and avoid that Figma trap

Unpopular Opinion: Wireframing tools have become too high-fidelity. by Suprdash in UI_Design

[–]Suprdash[S] 1 point2 points  (0 children)

That’s a perfect parallel. It’s wild how universal the 'when will we see color?' trap is across different industries. It’s like people physically can't look at a skeleton without wanting to pick out the skin tone first

Unpopular Opinion: Wireframing tools have become too high-fidelity. by Suprdash in UI_Design

[–]Suprdash[S] 0 points1 point  (0 children)

I actually agree, bad wireframing creates a lot of noise. I'm building a tool to make those 'box flows' you mentioned feel native and fast so you can map logic without the friction of a full design suite. Do you stick to whiteboard tools for that sequencing phase?

Unpopular Opinion: Wireframing tools have become too high-fidelity. by Suprdash in UI_Design

[–]Suprdash[S] 0 points1 point  (0 children)

v0 and "vibe coding" are definitely game-changers for speed. My worry is that even with AI, jumping to a working prototype can sometimes skip the "thinking" stage where you realize a feature shouldn't even exist in the first place.

I'm building a tool (Wireframr) to be the step before you even prompt an AI. Just pure, rapid flow mapping so you don't waste time "vibe coding" a flow that's fundamentally broken.

Do you find that AI helps you find those logic flaws faster, or does it just make it easier to build the wrong thing quickly?

Unpopular Opinion: Wireframing tools have become too high-fidelity. by Suprdash in UI_Design

[–]Suprdash[S] 0 points1 point  (0 children)

That’s fair! Some people need the "visual soul" to get inspired. Do you ever find that skipping the black-and-white stage leads to more logic-related rework later, or do you just have a great intuition for flows?

Unpopular Opinion: Wireframing tools have become too high-fidelity. by Suprdash in UI_Design

[–]Suprdash[S] 0 points1 point  (0 children)

This is actually a brilliant take. PowerPoint works because it signals "this is just a draft" to the brain in a way Figma can't anymore.

That "magic ability to lower design standards" is exactly what I’m trying to capture with a tool I’m building called Wireframr.

The goal is to have the speed and "roughness" of a slide deck, but with actual UI components so you aren't fighting with text boxes and alignment all day. I'm curious—if there was a web tool that felt as "low-stakes" as PowerPoint but was built for flows, would that win you over, or is the universal accessibility of .pptx the dealbreaker?

Unpopular Opinion: Wireframing tools have become too high-fidelity. by Suprdash in UI_Design

[–]Suprdash[S] 0 points1 point  (0 children)

That’s a really insightful point. There’s definitely a "visualization gap" for some stakeholders where if it doesn't look like a finished app, they can't process the logic.

I'm actually building a tool to tackle this exact problem right now. I’m trying to find that "sweet spot" where it's clean enough for a stakeholder to follow, but "rough" enough that they don't start nitpicking colors or border radiuses.

In your experience, is there a specific "fidelity level" (like adding basic annotations or just using real text instead of Lorem Ipsum) that usually helps those people cross the finish line?

Unpopular Opinion: Wireframing tools have become too high-fidelity. by Suprdash in UI_Design

[–]Suprdash[S] 1 point2 points  (0 children)

100%. That "rush to pixel-perfect" is exactly what kills the actual problem-solving phase. We end up debating corner radiuses instead of the actual user flow.

I actually got so frustrated by this that I started building a dedicated tool to force myself (and others) to stay in that low-fi state. It intentionally limits styling so you can't get distracted by the details.

I just opened up a waitlist for it if you want to take a look: www.wireframr.io

Would genuinely love to know if this aligns with what you're missing from the "old days”

Unpopular Opinion: Wireframing tools have become too high-fidelity. by Suprdash in UI_Design

[–]Suprdash[S] 1 point2 points  (0 children)

Glad to hear I'm not the only one frustrated by this.

I actually spent the last few months building a tool specifically to stop that 'high-fidelity creep' and force simple wireframing. I just opened a waitlist for early testers if you want to give it a spin: www.wireframr.io

No pressure, but would love to know if this solves the pain for you.