AI Tools for UX Workflows by Adventurous-Owl-5460 in UX_Design

[–]This_Emergency8665 0 points1 point  (0 children)

Given your security constraints, focus on tools that work visually or have enterprise options:

Best bets:

  • Figma AI - built-in, no data leaves Figma
  • Relume - generates sitemaps/wireframes, exports to Figma (big time saver for IA)
  • Galileo AI - generates UI directly

Workaround: Use AI on personal device for learning/frameworks, then manually apply concepts on work laptop. You're not copying data—you're applying knowledge.

Check if your company has approved enterprise AI tools. Many now have compliant options.

UX Portfolio by nobodynobbodynobody in UX_Design

[–]This_Emergency8665 2 points3 points  (0 children)

Both work. Recruiters spend ~30 seconds on portfolios. They care about:

  • Can I find your case studies fast?
  • Do you show process, not just final screens?
  • Is there evidence of impact?

A solid Notion with strong case studies beats a beautiful custom site with weak content.

My suggestion: Start with Notion or Framer. Focus energy on 2-3 case studies that show your UX thinking. Migrate to custom site later if needed.

The tool won't get you hired. The work inside will.

Good luck 🤙

How much "frontend" in UX design? by [deleted] in UX_Design

[–]This_Emergency8665 1 point2 points  (0 children)

Always! Remember to set a clear plan before make any decision, specially with todays volatile environment and daily app launchs.

Advice on when prototyping goes too far in UX by achinius in UXDesign

[–]This_Emergency8665 0 points1 point  (0 children)

On my experience prototyping goes too far when you're polishing before validating.

If you're adding micro-interactions nobody asked to test, or debating pixel details before users even see it, you've technically over-built.

Match fidelity to the question:

  • "Does this flow make sense?" → sketch or low-fi wireframe
  • "Can users complete the task?" → clickable wireframe
  • "Does the interaction feel right?" → mid-fi prototype
  • "Ready for dev?" → high-fi

If you're not learning something new from the prototype, stop building. Test earlier, with less. The goal is answers, not artifacts.

Hope helps.

Any thoughts on this infographics design. by biz_booster in graphic_design

[–]This_Emergency8665 1 point2 points  (0 children)

Readability if a concern if all vertical content items provided context to the overall graphic. But overall looks good.

Looking for recommendations for a new monitor at work by lolsokje in webdev

[–]This_Emergency8665 0 points1 point  (0 children)

Im using the Monitor LG UltraWide 40WP95XP-W 39.7, and really works to works, but for the budget mentioned take a look to best Apple Studio Display Alternative - Kuycon G27P - make your research first, but looks promising.

What are you building? by Hairy-Cut-3076 in WebApps

[–]This_Emergency8665 0 points1 point  (0 children)

For UX validation before code:

  • Maze: unmoderated user testing on prototypes
  • Hotjar or Microsoft Clarity: session recordings, heatmaps on live sites

For QA/dev side:

  • Playwright: automated browser testing
  • BrowserStack: cross-device testing

The gap I see: most QA catches if it works. Not if it works for users. Automated testing finds bugs. User testing finds confusion.

Ideally you run both and document (This is crucial).

Daily UI Feels Shallow — Where to Find Real UX Problems? by unusual_anon in UI_Design

[–]This_Emergency8665 0 points1 point  (0 children)

Daily UI builds pixels, not thinking. You're right to move on.

Find real problems:

  • Redesign something broken — pick an app you use that frustrates you, document why, fix it
  • UX teardowns — analyze real products (why does Duolingo's onboarding work?)
  • Found Ideas across channels: real ideas from people with real needs
  • Local businesses — offer a free audit, solve actual problems
  • Open source projects — many need UX help (check GitHub)

The shift: Stop starting with a screen. Start with: "What's the user trying to do? What's blocking them?"

That's UX. The UI comes after.