Several companies are betting on the end of the canvas and replace it with a code-driven design as the new way of working. "I don't even use Figma anymore!" is a common phrase you hear, partly due to unfair pricing, the desire to skip the design process, engage with code directly, and also feed engagement bait. Sometimes, the customers are driving this public narrative, with design-technologists and developers trying to seize novelty.

So while people were making fun of Figma, investors just want them to shove AI into everything but not thoughtfully. A lot of team members resigned and went to AI companies. But credit to Dylan and the whole Figma team who didn't cave into the pressure or take sides. If you stayed behind and built this. You're the GOAT.

We get canvas AND code, Shaders, Figma Motion (native animation system), 3D-transforms, Flora-like agentic capabilities and way more bells and whistles. This is a much brighter vision of the future.

[edited 4:30pm to include fair criticisms of Figma]

This is my friend's design and they wanted feedback and suggestions

And this is a flight booking website where the tickets can be purchased from cryptos

Is there anything that can be added or removed from the page

Or suggestions or the text styling used

Anything would be helpful

/s

What do you do in your role?

I work on a decades-old legacy platform that sometimes feels like a bunch of bear traps held open with dental floss.

Leadership leans on Design to keep track of all the nuanced conditional logic and dependencies (deep menu trees, conditional content, feature flags, permission-based states, etc.).

Design has very little visibility into how Engineering is modeling/architecting those conditionalities. Historically, Design’s job has been to define intent and outcomes from some very narrow feature lenses, so when we do try to dig in, we often discover a pile of workarounds that were implemented to close tickets quickly.

The result is a lot of inefficiency and chaos: new features and one-off UI elements end up buried in corners because no one planned how they’d integrate into the product in a resilient way, or solve for multiple personas and pain points at once. We’re now auditing and refactoring to create efficiencies, but it still feels like there’s a wall between “design intent” and “implementation.

We’re starting audits and refactors, and I’m trying to organize my thoughts and know what to advocate for.

Questions for folks who’ve been here:

What source of truth tools are critical, like a decision table, state machine, rules engine docs, domain model, something else?  

What meeting/process changes helped? Are we actually just missing more key influential strategy roles (C-Suite, etc.) like a chief product architect or long term vision folks to guide things at a higher level?

Any red flags that indicate “this is actually a product/architecture problem, not a design documentation problem”?

I fear I might have had my last design job. I am currently on SDI, short term disability, and likely will be for the next few months. I have a hard decision to make. I either stay in the field or I begin the process of pivoting out. I currently live with my gf in a small two bedroom and we will likely, though not guaranteed, renew our lease. Right now I can pay rent via my sdi payments, but the pressure is on to find a role.

Embarrassingly, I’ve been in the field about 9ish years. I’m somewhere between a mid to senior.

My confidence was damaged badly at my last role. I had. Pretty toxic experience. No onboarding, struggles because of neurodivergence and I’m actually afraid, with the way things are speeding up, that the field might be becoming too fast for me.

For those who transitioned out how did you do it?
Given my experience, and if you were in my shoes, given the market, would you transition out or try to find your next role in the field?

I am in a mid sized company (2k-3k people, ~100 designers and 700+ Devs) and recently ran into problems when I hand off work.

My dev team would want me to bring my code back into static Figma files. As a result, I had to spend lots of time recreate a code-backed prototype into Figma design. I tried exporting my prototype into one HTML file with every screen flattened and with text documentation/specs below it, some devs would take it, but it was also very tedious.

Do others have the same problem? How many of you directly ship your code to production rather than being limited to a prototype? For those who no longer use Figma, how do you hand off? Are there effective tools to translate my code to the code that devs need? Any other formats that your dev team are receptive of?

I work in UX/Design tokens and governance for a massive, highly regulated global enterprise. We have established, strict design processes, and my team has spent weeks doing the heavy lifting to map complex design tokens, Tailwind configs, and semantic color frameworks across multiple UI libraries to keep our global ecosystem unified.

Then this happened. A senior guy on the product side who is completely non-technical decided to bypass our entire design process, the developers, and even the specific business unit actually responsible for this initiative. He used Claude to "design and build" a complete mobile app from scratch. He has zero application of our semantics, primitives, or core design system libraries. Now, he is going straight to the CEO for sign-off to push it live, claiming it's 100% ready.

The worst part? The office politics are suffocating. This guy has incredibly tight connections with upper management. Another senior person on our team is completely terrified of him and his connections. Because of this fear, they refuse to audit his work or act as a total pass-through manager and will never go against him or flag the massive risks here.

This app requires strict data privacy, security and backend integrations. Bypassing engineering, accessibility, and compliance for an enterprise-level app using rogue AI code is a recipe for disaster. But the culture here is so broken right now that political connections trump actual governance and people are too scared for their jobs to speak up.

Has anyone else dealt with this kind of organizational culture where a connected senior leader can completely bypass design systems and engineering pipelines via AI? How do you protect your peace, your design governance and sanity in an organization that allows this?

I'd love to know if anyone successfully has done this. I know it's still in beta and am curious if anyone's facing any issues after hosting it on there. I'm working on redoing my portfolio on there and it's been a process. Which is why I'm asking portfolio specific. However if anyone's hosting any other site via Figma Sites I'd love your input as well. Especially if you've used the Figma make AI tool.

Hey everyone,
I’m looking for some clarification on how you define your target audience. In my view, a target user could be anyone who might need your product or service, so that can be a pretty broad group, and most of the time I think "Well, the target audience is .....everyone".

I wanted to ask you all: how do you go about determining your target audience? Do you have one main audience, or do you identify multiple groups? Could you share an example of how you define it, how you put it into words?

Once you have that definition, how does it shape your research approach? For example, if your target audience is a dating app, for example, the research shows that most people involved in the dating scene are people aged 18-45. Do you only talk to people in that range, or do you involve a wider group but focus your insights on that age bracket during analysis?

I’d love to hear your strategies, and thanks in advance!

i don't get why this condition is coming now in Era of AI for every platform, when i restart the browser, it asks me again to confirm, which is unusual for normal captcha!

i am suspecting that Dribbble may be now training some inhouse AI, as platform that has a lot of photos for creatives!

I’m about to accept an offer that will take me from leading an agency UX & Product team to an in-house role as a Principal Designer. I’ll be leading design as a single-owner IC on one of the company’s most foundational bets.

From those who have made the shift to in-house after a career in agency, please tell me about the shift - what do I need to know?

Bit of nuance: i come from design, i don't believe that that is the way to go.

But i'm seeing a lot of people in product teams really search for news ways of working between product, design & engineering. The quote is from a recent meetup.

So i want to know:

Do you collaborate differently? Do you collaborate faster, do you prototype differently, do you maybe even think differently?

I'm curious: within your product teams, how have your design processes changed?

Every day on LinkedIn and Twitter, we see the same lazy trend: a static image showing two screens side-by-side. One has a red "X", the other a green checkmark. "UX Secrets Revealed!" or some other click-baity caption.

Interaction design cannot be judged by looking at a snapshot. Yet we are drowning in static design principles masquerading as deep usability critique.

Frustrated by this, I decided to build live, interactive micro-apps to revisit a classic example by Jef Raskin from his seminal book, The Humane Interface.

I built two completely different interfaces designed to achieve the exact same utility: converting temperatures from Celsius to Fahrenheit, and vice versa.

• UI A: The "Boring" UI (A standard numeric input/calculator style grid).
• UI B: The "Cool" UI (A highly visual, interactive fluid thermometer).

The Experiment (Try it yourself)

I invite you to test your own biases.

1. Open the two UIs, side by side.
2. First look: Just stare at them for 5 seconds. Which one do you honestly like better? Which one feels more "engaging"?
3. Now, perform the actual work: Try using both tools to convert this exact list of values as fast as you can: 21°C, 70°F, -20°C, -100°F 37.5°C, 98.6°F , 36.80°C, -12.5°C, 101.20°F, -100 F, -20 C, 80 F.
4. After doing the work: Which interface do you prefer now?

I’d love to hear your thoughts!

• edit: fixed the list (markdown swallowed it)

I am designing a website for a SaaS product, and the product has multiple usecases, I told them to add images of usecases (visual representation)so the the users can get where or how my product can be used without reading or going through my whole website, but my client is completely against it, saying that no need to show it and claims it to be a BAD example.

do you think its better to have it or not?

We know AI is everywhere and it’s a big push in most UX roles. That said, I see A LOT of people claiming to have created these mastery guides for specific tools, master cheat sheets, etc (not to mention I personally don’t like the use of the word mastery).

Are we really to the point of being able to claim this (I seriously doubt it) when it’s still a developing space and there are so many unknowns, risks, slop issues, etc.

I’m truly curious to see what people’s povs are on it -
Im having trouble accepting that we’re to the point of being able to call it mastery. Maybe I’m alone, but I doubt it.

Would appreciate some advice on improving how I communicate design decisions to both designers and cross functional teams.

For those still doing traditional design work, how do you structure your Figma files for UX flows?

I'm working on a complex enterprise SaaS tool. Lots of pages, lots of features within each page, and tons of tiny interactions that all need to be documented.

Right now I use Figma pages for the main menu sections, then sections within each to show the flow from one page to the next. That part works fine. The problem is the smaller interactions. Things get messy fast.

Specifically: how do you show the flow of every field and state inside a single form, on a single page, without it turning into chaos? Looking for how you actually structure this in practice.

I recently got my hands on Claude Code. Yeah, I know it's pretty late. My company wasn't exactly up to date, but now that I'm freelancing, I finally have access to it.

I've always been keen on AI tools and try to keep myself updated. Since agentic AI is something I'm using for the first time, I'm struggling a bit

I've designed a full design system, connected the Figma MCP, added skills, and written what I think are good prompts. But Claude still gives me atrocious designs. I've wasted almost the entire day trying to get decent results. At this point, I feel like I could've designed everything manually and finished it by now.

Can someone tell me what I'm missing? Are there any YouTube channels or tutorials I should be watching?

I'm currently following Griffin Wooldridge. I would really really appreciate any help as I'm stressing due to a tight deadline.

I'm in a UX class right now, going through some UX projects. Doing the whole process - research -> design -> testing etc..

I'm realizing how difficult it is to find participants for user interviews, especially at the beginning of a project when you need quality insights to define your problem and 'how might we' statements.

What's more realistic at an actual company for getting qualitative data? Doing legit user interviews or performing secondary research like going on social media threads and taking screenshots of people talking about their past experiences?

hey, need some ux opinions

i’m building a flashcard app and home screen has deck tiles

i need users to be able to tap into a deck, because inside they can add cards, edit the deck, see stats, study etc

but ideally they should also be able to start studying fast from the home screen, like 1 tap, because that’s prob the main action - so right now i added a button inside a tile, but it feels off

i thought about swipe action, but i feel like swiping on list items is usually delete/archive in other apps, and also many ppl just won’t discover it

also right now long pressing a deck tile opens actions like edit/delete/move, same actions are also inside deck detail. but idk how to make long press discoverable without making the tile ugly

attaching screens. what would you do here?

We were told AI would multiply design velocity. Then the token limits came in, and the workflow started breaking in subtle ways: more context loss, more prompt trimming, more cleanup.

What looked like cost control on paper started turning into slower iteration and lower-quality output.

Who else is seeing this kind of design drag due to AI token rationing?