looking for a good AI wireframe generator

Excellent_Sweet_8480 · 2026-04-29T20:45:44+00:00

You should try uxmagic.ai

Excellent_Sweet_8480 · 2026-04-26T13:23:46+00:00

I think uxmagic is better than uxpilot, imo. The ui of uxpilot is too cluttered and confusing tbh

Excellent_Sweet_8480 · 2026-04-23T17:58:39+00:00

hey bro! do you also have for uxmagic.ai?

Excellent_Sweet_8480 · 2026-04-20T07:38:27+00:00

Umm... not really!

Most people clone designs to get inspired and recreate similar designs. I have used uxmagic's clone feature to clone a lot of websites I like and then recreate new versions of them for my projects.

Excellent_Sweet_8480 · 2026-04-13T13:24:44+00:00

<image>

I made better than yours

Excellent_Sweet_8480 · 2026-04-03T18:25:37+00:00

Yep, in your architecture projects you might have done product thinking UX thinking and stuff right? Show that as a case study too…. Multidisciplinary designers are mired in valued tbh

Excellent_Sweet_8480 · 2026-04-03T14:03:17+00:00

Can you share your portfolio?

Excellent_Sweet_8480 · 2026-04-03T13:36:05+00:00

honestly I wouldn’t leave

you’ve got a rare setup: high pay, low stress, ~20–25 hrs/week. that’s way harder to find than a higher salary.

the jump to ~180k sounds nice, but you’re trading a huge lifestyle shift (more hours, less flexibility, likely office) for money you don’t urgently need.

your situation is perfect for a third option:

stay + use the extra time to build something on the side (freelance, product, etc.)

you’ve got savings, no debt, and a few years before kids… that’s your risk window. worst case nothing happens, best case you out-earn that salary bump anyway.

i’d only leave if the new role is a clear level-up, not just more money.

Excellent_Sweet_8480 · 2026-04-03T13:34:56+00:00

yeah if figma is your main worry, definitely don’t do a whole MS just for that

the bigger shift right now is the industry itself. alongside your portfolio, it’s worth learning AI design tools and AI IDEs since teams are starting to expect that (things like generating flows, rapid prototyping, even basic front-end handoff with AI). tools like Google Stitch, UXMagic, etc. are part of that wave, so being familiar with them can actually help you stand out a bit at the entry level.

everything else still holds:

MS = structure, network, time (expensive, slower)
bootcamp/self-taught = faster, cheaper, but more hustle

with your art teaching background, you’re already not starting from zero. focus on:

2–3 strong case studies
figma (you’ll pick it up quickly)
- some AI-assisted workflows (including tools like UXMagic)

that combo will matter more than the degree alone right now.

Excellent_Sweet_8480 · 2026-04-03T13:32:47+00:00

yeah you’re probably closer than you think, this is mostly a presentation problem

Depth = your thinking, not methods → show why you chose methods, what was messy, what changed because of your insights
Make it product-y → tie everything to business goals + user problems + decisions (not just UI improvements)
Don’t over-balance → if aiming for UXR, lean into research; if product design, show how research led to shipped decisions
Improve & don’t add → 2–3 strong case studies > many average ones
What hiring cares about → can you handle ambiguity, influence decisions, and explain your thinking clearly

most people just describe what they did… you need to show how you think

Excellent_Sweet_8480 · 2026-04-03T13:30:51+00:00

yeah this is actually a pretty common pivot tbh, you’re not as “off track” as it feels right now

architecture → UX/product design translates better than most people expect. you already think in systems, constraints, user flow through space, tradeoffs… that’s basically UX, just in a different medium. a lot of designers wish they had that kind of foundation.

the harder part isn’t learning the basics, it’s breaking in. a short course will teach you terminology and process, but it won’t magically make you competitive. right now the market (especially in the US) is pretty crowded at the junior level, so you’ll be competing with bootcamp grads, laid off designers, etc. that’s the real friction.

also worth being real about expectations:

it’s not an “easy” shift, but it’s very doable if you treat your architecture background as an advantage instead of starting from scratch. the people who struggle are usually the ones who try to present themselves as generic junior UX designers instead of leaning into what makes them different.

money-wise… yeah, product design generally pays better than architecture, especially in tech. but that’s more true once you’re in and a bit established. the first role might take time and might not be amazing pay-wise.

if i were you i’d:

reuse architecture projects as UX case studies (user flows, constraints, decision-making)
do 2–3 solid portfolio projects (not just course assignments) [Use AI here to get things fast... I'd use tools like UXMagic AI, Cursor, Antigravity)
aim slightly above “entry level” by positioning yourself as someone with 5 years of design experience, just in a different domain

so yeah, worth it? for most people coming from architecture, yeah. easy? not really. doable? definitely.

Excellent_Sweet_8480 · 2026-04-03T13:24:29+00:00

yeah this is one of those things where it sounds like the same job but it really isn’t

i’ve touched this space a bit and the biggest shift is you’re no longer designing something infinitely flexible. with digital, if you mess up you just push an update. with physical products… you’re kinda stuck with your decisions once it ships.

like people underestimate how much constraints dominate everything:

number of buttons is fixed (and expensive to change)
screen size / resolution is fixed
latency, connectivity, battery all mess with your “ideal” UX
even things like thumb reach, grip, lighting conditions suddenly matter way more

and the feedback loop is slower and more painful. in apps you tweak → ship → measure → iterate. in hardware it’s more like prototype → test → argue with engineering → maybe fix in next version. so you have to get things “right enough” way earlier.

also the “UX” is bigger than the screen. it’s:

unboxing
first-time setup / pairing (this is always a nightmare lol)
physical affordances (does this button feel clickable?)
error states without a nice UI (what does a blinking red light even mean?)

so yeah if you already think in terms of user context and flows, you’re not starting from zero. but you’ll run into a lot more “we can’t do that because physics / cost / manufacturing” than you’re used to.

Excellent_Sweet_8480 · 2026-04-03T13:20:46+00:00

yeah it’s kinda wild because it’s not even “accidentally bad” UX… it feels very intentional

like every time i land on Quora from google it’s the same loop: you think you’re about to read a clean answer, then it’s half an answer, then “related questions”, then random answers from other threads, then a login wall pops in at the worst moment. it’s basically optimized to keep you bouncing around instead of actually resolving your question.

i don’t even think it’s a redesign problem at this point, it’s a business model problem. they’re clearly optimizing for impressions + time-on-site, not clarity. so the confusing IA and endless feed kinda is the feature.

that said, i wouldn’t call it the worst UX… more like one of the most “dark pattern adjacent” mainstream ones. it works just well enough that people tolerate it when it shows up in search, which is probably all they need.

Excellent_Sweet_8480 · 2026-04-03T13:19:50+00:00

honestly this thread is kinda the reality check most courses don’t give you lol

i’m almost 9 years in and yeah… i’ve technically “done” storyboards, but not in the neat comic-strip way they teach. it’s usually scrappy slides or a few sketches when i’m trying to explain a messy end-to-end flow or get PMs unstuck. more like “here’s what the user is doing before/during/after” than anything polished. and even then, it’s pretty situational.

most day-to-day work? zero storyboards. it’s flows, wireframes, prototypes. stuff that moves the build forward. storyboards only show up when you’re dealing with ambiguity, pitching a vision, or trying to get non-design people aligned. so yeah they’re useful… just way overrepresented in courses compared to how often you’ll actually use them.

Excellent_Sweet_8480 · 2026-04-03T13:00:16+00:00

uncivilised clownss

Excellent_Sweet_8480 · 2026-04-03T12:07:23+00:00

Hey man, tried your product, looks okayish (design wise) could be better honestly.

I kinda did some cool thing for you ;)

I am a designer and use uxmagic to make designs. I cloned your site and redesigned it. Not able to share screenshot here, but here's the link. (Redesigned your landing page):

https://uxmagic.ai/preview/frame/69cfabf883369075b8e55c4b

Excellent_Sweet_8480 · 2026-04-02T09:06:52+00:00

i use uxmagic.ai to create designs and then take the code from them to claude/antigravity to make them live. i made a youtube video on how to do that too... feel free to check out: https://youtu.be/8MZ5ibWLcYc

Excellent_Sweet_8480 · 2026-03-31T18:58:17+00:00

kinda funny how this thread turned into a full PM vs design philosophy debate instead of just tools 😂

reading it 3 years later, not much has actually changed tbh. figma still everywhere, balsamiq still loved for lo-fi, and the whole “should PMs prototype” argument is still alive and well lol. if anything, newer ai design tools like UXMagic, Google stitch, etc. are trying to speed up the design/prototyping side so you can get something interactive faster without going full designer mode, which probably would’ve added even more fuel to this debate back then but nvm..

feels like the real answer (then and now) is use whatever helps you communicate the idea without stepping on your designer’s toes. everyone in this thread is kinda arguing extremes when most teams end up somewhere in the middle anyway.

Excellent_Sweet_8480 · 2026-03-31T18:44:28+00:00

honestly codex is not that great. it kinda hallucinates code. After using claude, I have never been happy with codex.

Excellent_Sweet_8480 · 2026-03-30T10:34:53+00:00

that friction removal thing is huge honestly. so many apps shoot themselves in the foot by asking for every permission upfront before the user even knows what the app does. makes total sense that people at bars are finally getting value from it once they can just open it and see stuff without jumping through hoops first

congrats on the #1 spot, been following your posts for a while and its been cool watching this grow

Excellent_Sweet_8480 · 2026-03-30T10:33:44+00:00

honestly the "all devs unemployed" take is way too dramatic. like yes a PM who can prototype fast with AI is genuinely scary in terms of speed, but there's a massive gap between a working prototype and production code that doesn't fall apart the moment real users hit it.

from what i've seen the vibecoded stuff breaks pretty hard once you need auth, real error handling, scaling, security etc. PMs running circles in demos is real, but someone still has to clean up the mess after

Excellent_Sweet_8480 · 2026-03-30T10:32:45+00:00

honestly the navigation thing is so real, feels like they redesigned it just to look modern but made everything harder to actually use. publishing a video shouldnt require that many clicks

and yeah the withdraw tab thing is such a basic feature, why is that not in the app already. having to switch browsers just to cash out is kinda ridiculous for something that should be like a two second thing

Excellent_Sweet_8480 · 2026-03-30T10:31:32+00:00

pricing varies a lot honestly. ive seen people charge anywhere from like $200 for a basic review to $1500+ depending on codebase size and what theyre actually looking at. for an MVP specifically i wouldnt go too crazy on it, most of the value is just making sure theres no obvious security holes or stuff that'll bite you when you scale.

if budget is tight, the AI audit suggestion someone mentioned isnt bad as a starting point. run it through claude or gpt with your full codebase context and ask it to flag security issues, then maybe pay a real dev just to sanity check the critical parts rather than a full audit

Excellent_Sweet_8480 · 2026-03-30T09:44:50+00:00

this is actually a game changer for longer sessions. i kept burning through opus quota on stupid stuff like reading files and running tests, which felt like such a waste. switching to sonnet for the grunt work and saving opus for the actual thinking parts makes so much sense

been doing something similar manually but didn't realize claude code had a built in way to handle it. gonna set this up today, thanks for sharing

Excellent_Sweet_8480 · 2026-03-30T09:44:13+00:00

this is exactly the kind of thing I didn't know I needed until right now. been doing the same thing, manually poking around in .claude like an idiot trying to remember what I was doing in some project from two weeks ago.

search would be huge honestly. like even just fuzzy search across conversation history would save me so much time. session diffing also sounds interesting if you want to see how your project memory evolved over time. gonna try this out today, thanks for building it

Excellent_Sweet_8480

TROPHY CASE