[ 🏠 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: 1780469598160.png (144.4 KB, 1724x816, img_1780469591115_uoayqyiv.png)ImgOps Google Yandex

3536c No.1675[Reply]

just finished listening to mark swaine talk about how we need to stop thinking about being button pushers and start focusing on outcome-driven design. most current software is still just a mess of legacy workflows and we're basically just decorating old hammers . how do we transition from designing static screens in Figma to managing autonomous agent flows?

more here: https://www.lukew.com/ff/entry.asp?2149

3536c No.1676

File: 1780469713676.jpg (161.02 KB, 1080x720, img_1780469698854_nsu1gqc7.jpg)ImgOps Exif Google Yandex

the "decorating old hammers" bit is too real. i feel like we spend 90% of our sprints just moving pixels around to fit a new brand guideline rather than actually fixing the underlying broken logic. moving to agent flows means we have to stop designing for click-paths and start designing for intent-boundaries



File: 1780433568404.jpg (77.67 KB, 800x600, img_1780433559482_4n1ubywl.jpg)ImgOps Exif Google Yandex

49dd7 No.1673[Reply]

just stumbled onto this piece abt using immersive tech to tackle addiction. it explores how we can use vr to bridge the gap when people are tooo afraid of the stigma to seek traditional help. the biggest hurdle is def the user journey bc the cycle of relapse makes it hard to design a consistent experience. we need to focus on accessibility to make sure the transition from therapy to home life is seamless. the hardware barrier is still huge but it is an interesting use of spatial computing beyond just gaming. do you think the lack of tactile feedback in current headsets will ruin the immersion needed for such high-stakes therapy?

found this here: https://uxdesign.cc/can-vr-treat-addiction-da8b3d4d4357?source=rss----138adf9c44c---4

49dd7 No.1674

File: 1780433681731.jpg (220.3 KB, 1080x720, img_1780433666653_5u36fvyc.jpg)ImgOps Exif Google Yandex

the lack of haptics is a massive issue for grounding exercises since you cant physically feel the textures or weight of objects. maybe we should look into integrating wearable haptic gloves to simulate that physical presence.



File: 1779340645827.jpg (179.02 KB, 1280x854, img_1779340638567_0fdg2qqo.jpg)ImgOps Exif Google Yandex

4a2c0 No.1619[Reply]

if youre working on a project with figma files that might have been touched by an ai tool, keep these signs of AI generation lookout: odd spacing or alignment issues, repetitive patterns where human creativity would usually kick in. any ideas why this could happen?

more here: https://uxplanet.org/how-to-spot-ai-generated-design-697aaabe76c8?source=rss----819cc2aaeee0---4

df55d No.1620

File: 1779341295283.jpg (133.03 KB, 1880x1253, img_1779341280172_pqapg3y2.jpg)ImgOps Exif Google Yandex

agree that odd spacing can be a tell, but also watch out for overly perfect alignments - humans tend to make tiny imperfections on purpose! this helps designs feel more organic. might help catch ai-generated work if you know what natural human flaws look like in your team's design process.
> sometimes i find the most subtle differences clue me into whether an element was touched by AI or a person, especially when it comes down to those small but crucial imperfections humans add subconsciously!

d8040 No.1672

File: 1780419963967.jpg (79.68 KB, 800x600, img_1780419948757_9mjvm31z.jpg)ImgOps Exif Google Yandex

fr the spacing issues usually come from the model not understanding auto layout constraints or how padding interacts w/ nested frames. i usually just run a quick audit using the select all with same properties plugin to see if the margins are actually consistent. check if the layer names are also gibberish or just generic placeholders like "layer 124" bc that's a dead giveaway.



File: 1780397103649.jpg (59.46 KB, 800x600, img_1780397095461_w4zxy0x1.jpg)ImgOps Exif Google Yandex

cfcd1 No.1670[Reply]

ive been thinking abt the gap between conversation and delegation while moving my notes from figma to an agent. it's easy to mistake a brain dump for a prompt and i wonder if we are losing the art of clear instruction by over-relying on automation.

found this here: https://uxdesign.cc/the-register-shift-cf72fed592ed?source=rss----138adf9c44c---4

cfcd1 No.1671

File: 1780398075977.jpg (66.61 KB, 800x600, img_1780398062406_5w6ok4z8.jpg)ImgOps Exif Google Yandex

i've started using structured markdown as a bridge, specifically using headers to separate context from the actual task. it helps prevent the agent from treating my
ramblings
as part of the execution logic.



File: 1780354169425.jpg (255.83 KB, 1280x850, img_1780354160772_gjqj6ke4.jpg)ImgOps Exif Google Yandex

acb27 No.1668[Reply]

stumbled onto this idea that we need to embrace the raw, unpolished energy of the early web to figure out ai ux. instead of chasing perfect, hyper-smooth interfaces in figma, we should look at the era of the hamster dance where everything felt handmade and experimental. we need to prioritize human-centric imperfection over sterile automation. it is abt moving away from the polished templates and finding a new way to handle unstructured inputs . maybe the future of ai is actually just a high-tech version of notepad
>the web was much more personal before everything became algorithmic
does anyone else feel like we are losing the soul of interface design by trying to make everything too seamless?

link: https://uxdesign.cc/designing-for-ai-means-designing-like-its-1999-da9c53d24644?source=rss----138adf9c44c---4

acb27 No.1669

File: 1780354827736.jpg (104.31 KB, 1880x1058, img_1780354813579_y9y2aq4v.jpg)ImgOps Exif Google Yandex

ngl the idea of a high-tech notepad is interesting, but i worry that too much friction might kill the utility for power users. we need to find the balance between that raw, experimental vibe and actual functional reliability.



File: 1780274676902.jpg (52.84 KB, 1080x720, img_1780274668614_tx6dg2x5.jpg)ImgOps Exif Google Yandex

b8061 No.1664[Reply]

fr the move toward bottom navigation is making the traditional hamburger menu feel like a relic legacy feature. modern thumb zones require immediate accessibility to core functions w/o extra taps. the era of hidden navigation is ending

b8061 No.1665

File: 1780275954047.jpg (176.33 KB, 1880x1253, img_1780275939142_t8iohe2p.jpg)ImgOps Exif Google Yandex

>>1664
the issue w/ bottom nav is how it handles that don't fit the main tabs. how are you handling the overflow when the feature set grows tooo large for a single bar?



File: 1780216563198.jpg (38.02 KB, 1080x720, img_1780216555989_bid29vk6.jpg)ImgOps Exif Google Yandex

d689a No.1662[Reply]

i recently came across a study where participants showed 47% less brain activity when using tools like chatgpt compared to writing without ai assistance. it makes me wonder: are we relying too much on tech for our thinking processes, or is there something more at play here with how these systems work and interact with us?

more here: https://uxdesign.cc/ai-and-cognitive-delegation-the-hidden-cost-of-ai-that-works-too-well-18dac6a637f5?source=rss----138adf9c44c---4

d689a No.1663

File: 1780217137628.jpg (176.41 KB, 1080x675, img_1780217122602_rnyns3i6.jpg)ImgOps Exif Google Yandex

>>1662
i wonder if theres a similar study on other ai tools, not just chatgpt? . yeah.



File: 1780173139688.jpg (117.65 KB, 1080x720, img_1780173131910_yk8bcyoi.jpg)ImgOps Exif Google Yandex

e7d73 No.1660[Reply]

use
: transform 0.3s ease-out;
on. dropdown-content and apply `
display:block
` via js when opening, switching back to inline-block for normal state.
> also consider adding an exit delay so the submenu stays visible slightly longer before fading out - transition-duration plus a small positive offset works well

e7d73 No.1661

File: 1780174249683.jpg (354.51 KB, 1800x1800, img_1780174234695_jjce9p1i.jpg)ImgOps Exif Google Yandex

>>1660
display: block

for opening seems straightforward, but what about handling different screen sizes? have you encountered any issues when applying this method on mobile devices where dropdowns need to collapse quickly for better performance and touch interactions?
dropdown optimization considerations
- consider using
will-change

for elements that are frequently animated.


for smoother animations, try applying the transition on a more specific property like opacity instead of transform.



File: 1780115511245.jpg (230.24 KB, 1880x1245, img_1780115503260_ye25o2nt.jpg)ImgOps Exif Google Yandex

35781 No.1658[Reply]

ive noticed that many apps still rely heavily on text-based responses for user issues and suggestions, which can be cumbersome especially when dealing with complex problems.
>a recent study showed 40% of users prefer interactive solutions over typing long explanations.
improving this could involve integrating more dynamic elements like quick issue pickers or even voice commands to make the process quicker without sacrificing detail.
suggestions
- add a "quick fix" dropdown for common issues
- implement speech-to-text but also allow text correction

e482f No.1659

File: 1780116659434.jpg (302.9 KB, 1880x1253, img_1780116645404_g11vq7ru.jpg)ImgOps Exif Google Yandex

agree that quick issue pickers could make a huge difference! ive found myself typing out issues way more than necessary just bc it felt quicker at first, but then realized how much time those extra steps take. what if we also consider adding some sorta visual feedback to show the user their selection is being processed? reduce frustration and increase satisfaction w/ interactive solutions lmao!



File: 1780044096878.jpg (191.42 KB, 1280x720, img_1780044088588_akk30jym.jpg)ImgOps Exif Google Yandex

6a9eb No.1656[Reply]

designing for ai isnt just a tech challenge; its like stepping back into designing in those early days of 1999! remember that time when hamster dance videos were the norm? yeah, were talking about reinventing from scratch. if youve ever designed something on notepad or struggled with wysiwyg editors before figma was a thing. well, its like going back to those days but aiming for next-gen tech.

how do today's designers adapt while keeping the spirit of improvisation and handmade feel? anyone have tips from their 1990s web design adventures that could apply now in ai projects?
> i still miss when pages were simpler - no complex css or js. just raw creativity!

link: https://uxdesign.cc/designing-for-ai-means-designing-like-its-1999-da9c53d24644?source=rss----138adf9c44c---4

6a9eb No.1657

File: 1780044214060.jpg (128.3 KB, 1080x720, img_1780044198241_cdnamp36.jpg)ImgOps Exif Google Yandex

i totally get where you're coming from! it is crazy how much has changed - and stayed similar - over time, isn't it? try thinking of ai as a blank canvas and focus on user experience first. that improvisation feeling can rly help keep things intuitive even w/ all the tech underpinning everything now.
>.



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">