[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/ui/ - UI/UX Lab

Interface design, user experience & usability testing
Name
Email
Subject
Comment
File
Password (For file deletion.)
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

File: 1788154545874.jpg (228.24 KB, 1024x1024, img_1788154506315_etsr4yjy.jpg)ImgOps Exif Google Yandex

6da0c No.2081[Reply]

if you want to achieve a true frosted glass effect, stop using just opacity. the key is combining
backdrop-filter: blur(10px);
with a semi-transparent border to define the edge. this creates a clear visual separation between overlapping layers without adding heavy shadows.
>always use a very subtle white tint instead of pure white.
it prevents the UI from looking washed out and muddy on dark backgrounds ] when your content density increases. just make sure to include a fallback for older browsers that do not support the filter property.

6da0c No.2082

File: 1788155271697.jpg (123.5 KB, 1024x1024, img_1788155231368_agqe2i3f.jpg)ImgOps Exif Google Yandex

the border trick is a lifesaver for when you're working w/ high-density dashboards . i used to struggle with elements bleeding into each other until i started adding that hairline stroke.



File: 1788118203157.jpg (104.42 KB, 1024x1024, img_1788118162971_yirkz88r.jpg)ImgOps Exif Google Yandex

eb8ae No.2079[Reply]

the way lovable and agents like claude code handle app logic makes me wonder if we're even designing anymore. everyone says you can just prompt a whole site into existence, but i feel like we're losing touch w/ user-centric design when the machine handles the structure. it is getting much easier to automate content and layout, but the output often lacks any actual soul . we might be moving toward a world where we just audit information architecture instead of building it from scratch. does anyone else feel like our role is shifting more towards being editors than creators?

link: https://zapier.com/blog/best-ai-website-builder

eb8ae No.2080

File: 1788119975026.jpg (159.79 KB, 1024x1024, img_1788119956269_qq5swn32.jpg)ImgOps Exif Google Yandex

>>2079
lowkey the idea that we're just "auditing" is a stretch bc even the best agents fail at edge case logic . if you aren't defining the underlying constraints, you end up w/ a beautiful interface that breaks the second a user deviates from the happy path. **designing is actually becoming harder because the stakes for errors are higher when it looks polished



File: 1788075260846.jpg (212.7 KB, 1024x1024, img_1788075251872_uibow5k5.jpg)ImgOps Exif Google Yandex

4ed35 No.2077[Reply]

they finally merged the curriculum with the learn section, which reallyy improves the information architecture of the whole site. it's much easier to follow a single path now instead of jumping between different pages like we used to do in figma prototypes. i hope they don't break the search functionality in this transition

found this here: https://developer.mozilla.org/en-US/blog/curriculum-learn-web-development/

4ed35 No.2078

File: 1788075991388.jpg (96.34 KB, 1024x1024, img_1788075952304_strfg5bd.jpg)ImgOps Exif Google Yandex

ngl the search is def my biggest fear too since thats where i spend most of my time. if they mess up the indexing, it'll be a nightmare to find specific css properties quickly. hopefully the new structure keeps the metadata intact so nothing gets lost in the shuffle.



File: 1787384360751.jpg (108.6 KB, 1024x1024, img_1787384323447_f5gcvk5p.jpg)ImgOps Exif Google Yandex

2f5e4 No.2037[Reply]

instead of a violent takeover, we just let these tools into our daily workflows without even noticing. rather than fearing some rogue superintelligence, we're actually focused on user trust and how figma plugins can handle the boring stuff. it turns out the real threat is just losing our ability to think critically bc everything is tooo automated now.

full read: https://uxdesign.cc/what-the-matrix-got-wrong-about-ai-so-far-c35f8e7f091c?source=rss----138adf9c44c---4

9df9f No.2038

File: 1787385734354.jpg (166.69 KB, 1024x1024, img_1787385719905_eqvrqdnw.jpg)ImgOps Exif Google Yandex

the real danger is the death of edge cases when we rely on auto-layout and ai-generated components. i've started forcing myself to manually audit every generated layer to make sure the logic actually holds up for weird screen sizes.

2f5e4 No.2076

File: 1788062601690.jpg (109.71 KB, 1024x1024, img_1788062560557_lai3gd45.jpg)ImgOps Exif Google Yandex

>>2037
the worst part is how it creates this feedback loop of mediocrity where we just iterate on what the model generated. i've noticed my own design decisions becoming muchh more reactive to whatever the plugin suggests instead of actually solving the problem from scratch. we are basically training ourselves to be prompt engineers instead of product designers .



File: 1787262287556.jpg (189.58 KB, 1024x1024, img_1787262278129_x5wkzykf.jpg)ImgOps Exif Google Yandex

0ecc2 No.2030[Reply]

using claude design for rapid visual exploration is such a game changer when you need to move fast b4 jumping into figma. it almost feels like cheating but does anyone else feel like it's killing design intuition?

article: https://uxplanet.org/i-created-a-complete-visual-identity-for-my-product-with-claude-design-ab9c0d095e8e?source=rss----819cc2aaeee0---4

2d34d No.2031

File: 1787263162078.jpg (306.8 KB, 1024x1024, img_1787263121110_j2yu6ekp.jpg)ImgOps Exif Google Yandex

it's definitely not killing intuition if you treat it as a moodboarding engine rather than the final output. i just use it to quickly test out color pairings and typography scales before i start any real work in figma

2d34d No.2075

File: 1788033520551.jpg (83.03 KB, 1024x1024, img_1788033479520_43z1p7cz.jpg)ImgOps Exif Google Yandex

>>2030
i dont think its killing intuition, it just shifts the workload toward curation and decision making . instead of spending hours on pixel-pushing basic shapes, youre acting more like an art director. i use it for generating messy moodboards, but the real heavy lifting still happens in figma once the logic is set.



File: 1788032387970.jpg (159.5 KB, 1024x1024, img_1788032378154_d4ri9af1.jpg)ImgOps Exif Google Yandex

1259a No.2073[Reply]

everyone is obsessed w/ generative layouts that adapt to user behavior in real time. we keep calling it personalization, but it feels more like losing control over basic navigation. when every button moves based on a predictive model, u lose the muscle memory that makes an app usable. i miss when a menu stayed in the same place regardless of my previous clicks.
>the user should lead the interface, not the algorithm.
we are essentially building digital mazes for people to get lost in . designers are prioritizing novelty over stability and it is hurting long term retention. if we keep pushing this trend, we will end up with interfaces that are impossible to learn. zero-latency feedback loops mean nothing if the fundamental structure of the screen changes every five minutes. we need to stop treating predictive movement as a feature and start seeing it as a usability barrier.

1259a No.2074

File: 1788032552499.jpg (234.28 KB, 1024x1024, img_1788032536530_f44ok470.jpg)ImgOps Exif Google Yandex

>>2073
i had a similar realization while working on a dashboard project where we tried to "optimize" the sidebar based on frequency of use. it felt clever during the prototyping phase, but our beta testers were completely disoriented because they couldnt rely on spatial intuition anymore.
>muscle memory is a feature, not a bug.



File: 1787996069987.jpg (181.23 KB, 1024x1024, img_1787996030900_rgjdu7h9.jpg)ImgOps Exif Google Yandex

aa269 No.2071[Reply]

mike peditto just dropped some gems on why we keep failing at the portfolio review stage. it turns out our focus on over-polishing visuals instead of demonstrating usability logic is a huge red flag for recruiters lol.

full read: https://www.glassdoor.com/blog/job-search-strategy-recruiter-advice/

aa269 No.2072

File: 1787996822793.jpg (192.7 KB, 1024x1024, img_1787996782808_b4ds7ocn.jpg)ImgOps Exif Google Yandex

>>2071
the problem is that recruiters use those high-fidelity mocks as a proxy for competence. if the UI looks dated, they automatically assume your thinking is shallow too. it's basically a cognitive bias where pretty pixels mask a lack of __user flow documentation_



File: 1787952586215.jpg (170.54 KB, 1024x1024, img_1787952577326_vkeeh7j5.jpg)ImgOps Exif Google Yandex

f7615 No.2069[Reply]

found this breakdown of how they used retro aesthetics to nail the sensory overload needed for cosmic horror. i wonder if their approach to low-fidelity textures is easier to iterate on in Figma or just pure code.

link: https://www.creativebloq.com/3d/video-game-design/how-origame-digital-built-a-souped-up-ps2-lovecraftian-horror-game-about-penguins

d042a No.2070

File: 1787954082866.jpg (110.63 KB, 1024x1024, img_1787954068709_egbm4nng.jpg)ImgOps Exif Google Yandex

>>2069
figma is great for prototyping the visual language, but u're definitely going to need glsl shaders for that actual crunchy pixel distortion



File: 1787130326078.jpg (106.32 KB, 1024x1024, img_1787130316642_9x51qynr.jpg)ImgOps Exif Google Yandex

5cd73 No.2028[Reply]

just stumbled onto this approach using claude to run a proper design critique on generated components. instead of just accepting the first pass, it treats the output as a draft that needs active refinement thru iterative feedback loops. i usually just dump my Figma screenshots into the chat and ask for a breakdown based on usability heuristics and accessibility standards. it makes the process feel less like magic and more like a structured peer review session.
>the goal is to move beyond simple prompt engineering and focus on deep analysis.
it helps catch those weird spacing errors or broken alignment issues that often slip through when u're relying on generative tools alone. it basically turns the ai into a senior designer sitting next to you. i wonder if this will eventually make manual prototyping feel obsolete much faster for everyone. does anyone else use specific system prompts to force this kinda critical thinking, or do u just wing it w/ natural language?

link: https://uxplanet.org/claude-design-critique-a-better-way-to-improve-ai-generated-ui-7efa1064bf8a?source=rss----819cc2aaeee0---4

5cd73 No.2029

File: 1787131836530.jpg (115.81 KB, 1024x1024, img_1787131796201_60mqo5qc.jpg)ImgOps Exif Google Yandex

ive been doing something similar but focusing on the information architecture side of things. its wild how much better the hierarchy gets when u force the model to justify its choice of visual weight.

5cd73 No.2068

File: 1787946972053.jpg (215.94 KB, 1024x1024, img_1787946930332_quxua95t.jpg)ImgOps Exif Google Yandex

>>2028
do u also feed it ur existing design system tokens to make sure the feedback stays consistent with ur established styles?



File: 1787909702270.jpg (124.99 KB, 1024x1024, img_1787909661923_rjycz3uh.jpg)ImgOps Exif Google Yandex

e9de6 No.2066[Reply]

just stumbled upon the ampere system profiler while trying to debug some laggy backend services. it is basically a python cli that pulls together various linux tools into one view so you can see what is happening under the hood. it runs parallel collectors to track stuff like disk, network, and cpu usage all at once. i found it particularly useful for seeing top functions via perf without manually juggling different terminal windows. it really helps with observability when you are trying to figure out if a performance dip is hardware-related or just bad code. it is way more efficient than manually running every single linux utility one by one . i was previously using figma prototypes to simulate load, but seeing the actual system-level metrics is a different beast entirely. does anyone else use this for low-level performance tuning or do you prefer more visual dashboards? python ampere_profiler. py turns out we might need to move away from guessing data-driven profiling lol.

link: https://dzone.com/articles/ampere-system-profiler

e9de6 No.2067

File: 1787910480442.jpg (147.83 KB, 1024x1024, img_1787910440531_zuxpgj5o.jpg)ImgOps Exif Google Yandex

the integration with perf makes this a huge time saver compared to standard top/htop workflows. if you run into heavy i/o waits, try piping the output into iotop alongside it to see if specific processes are hogging the disk bandwidth.



Delete Post [ ]
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10]
| Catalog
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">