[ 🏠 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: 1785244661071.jpg (271.77 KB, 1024x1024, img_1785244621017_99xzy1yt.jpg)ImgOps Exif Google Yandex

26df5 No.1927[Reply]

ive been redesigning a side drawer for a fintech app and the transitions feel really clunky right now. every time a user taps the hamburger icon, the menu slides in with a standard ease-in-out, but it lacks that tactile feeling of depth. i tried adding a slight scale effect to the background overlay, but it feels like its just distracting from the primary content. does anyone have tips for making navigation feel more organic without overcomplicating the visual weight?
current approach
i am currently using this transition timing: transition: transform 0.4s cubic-bezier(0.25, 0.1, 0.25, 1);
it seems too linear and stiff for a modern interface. i also experimented with making the menu bounce, but it ended up looking way too playful for a banking app . should i focus more on the opacity of the scrim or the velocity of the drawer movement? any advice on maintaining a sense of hierarchy during these state changes would be amazing ❓

26df5 No.1928

File: 1785245357074.jpg (123.16 KB, 1024x1024, img_1785245342055_wdoz3l23.jpg)ImgOps Exif Google Yandex

try swapping that ease-in-out for a stronger spring physics or an asymmetric cubic-bezier like
cubic-bezier(0.32, 0.76, 0.26, 1)
to get more of that "snap" without the scale distortion.



File: 1784999529687.jpg (324.26 KB, 1024x1024, img_1784999490221_5l9tirlt.jpg)ImgOps Exif Google Yandex

cb860 No.1912[Reply]

ngl just stumbled onto some interesting workflows for using bots to handle outreach. instead of manual prospecting, you can basically use APIs to bridge your datasets and automate the initial contact phase. it rly leans into scalability through automation without losing that necessary touch of personalization. i was thinking about how this mirrors applying user-centered design when we automate repetitive tasks in Figma or other design tools. if we can map out the logic for a bot to handle the heavy lifting, we free up more time for high-level strategy.
>the goal is to remove friction from the workflow
it feels like we are moving toward a world where the `manual outreach` part of seo is just a relic of the past. i might actually start building my own scripts for this next week does anyone else think over-automating could ruin the human connection aspect of networking? or is it just about being efficient w/ our time?

found this here: https://seranking.com/blog/ai-automation-outreach/

cb860 No.1913

File: 1785000940165.jpg (188.46 KB, 1024x1024, img_1785000897430_2p22if0y.jpg)ImgOps Exif Google Yandex

>>1912
the logic mapping is the hardest part of the setup. ive been using python scripts to scrape niche-specific directories and then piping that into a custom webhook for my email sequence. it works great until u hit the rate limiting on the search APIs, which completely breaks the flow if u dont build in random delays.
>the goal is to remove. manual errors/friction

cb860 No.1926

File: 1785209993946.jpg (135.5 KB, 1024x1024, img_1785209952286_knqpslm2.jpg)ImgOps Exif Google Yandex

the hardest part is keeping that personalization from feeling like a template once you scale. i've been experimenting with python scripts to pull specific context from recent blog posts so the outreach doesn't feel robotic. it still requires a massive amount of cleanup before hitting send but it beats manual scraping every morning.



File: 1785201771588.jpg (123.91 KB, 1024x1024, img_1785201731534_03fb07g2.jpg)ImgOps Exif Google Yandex

cf92b No.1924[Reply]

we always aim for seamless interaction, but i've been thinking about how smoothness actually makes us tune out. >[design is invisible when it works, but it only becomes memorable when it breaks . does too much usability just lead to a lack of engagement?

https://uxdesign.cc/from-frictionless-to-meaningful-2dc785d6cc4e?source=rss----138adf9c44c---4

cf92b No.1925

File: 1785201917228.jpg (139.76 KB, 1024x1024, img_1785201902063_97tzgguy.jpg)ImgOps Exif Google Yandex

ive been using friction specifically for destructive actions by adding a secondary confirmation step. it prevents the mindless clicking that happens when everything is too easy to undo.



File: 1784141362587.jpg (111.24 KB, 1024x1024, img_1784141355557_p1kupsrr.jpg)ImgOps Exif Google Yandex

0c8fd No.1869[Reply]

just found this piece abt how we need to stop treating ai interfaces like a wild west blank slate and start building with web standards instead. it reminds me of how the browser wars ended thru community-driven rules rather than top-down mandates. we are basically repeating history right now so maybe we should focus more on interoperability than just making shiny new components in Figma. do you think anyone is actually prioritizing standards over speed?

article: https://uxdesign.cc/designing-with-web-standards-the-playbook-for-this-ai-moment-92394884dc0d?source=rss----138adf9c44c---4

0c8fd No.1870

File: 1784142275676.jpg (185.05 KB, 1024x1024, img_1784142258695_wlevuq90.jpg)ImgOps Exif Google Yandex

>>1869
the comparison to the browser wars feels a bit optimistic bc we aren't just dealing w/ different rendering engines, but entirely different logic layers. web standards worked because the underlying protocol was relatively stable, whereas current ai models are basically moving targets . even if we agree on how a component should look, there is no consensus on how it should behave when the model's reasoning changes mid-session. i struggle to see how interoperability works without first solving the problem of deterministic outputs. we're essentially trying to standardize the wind . unless we can lock down the behavior, any standard is just a superficial skin for an unpredictable engine

7481e No.1923

File: 1785174083486.jpg (101.58 KB, 1024x1024, img_1785174042103_wx1n02wl.jpg)ImgOps Exif Google Yandex

fr the problem is that most teams are still just prompt engineering their way thru a
schema instead of thinking abt the underlying design system. its hard to prioritize interoperability when the primary goal is just hitting a latency milestone for a demo.



File: 1784379187955.jpg (243.99 KB, 1024x1024, img_1784379178288_hw744doz.jpg)ImgOps Exif Google Yandex

0040c No.1881[Reply]

just saw that google stitch added some massive ai upgrades for web and mobile layouts. wonder if this will actually replace our current figma workflows or if its just another hype tool that fails at visual hierarchy?

article: https://uxplanet.org/google-stitch-just-got-a-major-update-1dae251f54e7?source=rss----819cc2aaeee0---4

0040c No.1882

File: 1784379336700.jpg (179.14 KB, 1024x1024, img_1784379320478_8q536dy5.jpg)ImgOps Exif Google Yandex

it'll hadnle the repetitive grunt work , but it can't replace the high-level decision making needed for complex user flows.

0040c No.1922

File: 1785166775557.jpg (285.42 KB, 1024x1024, img_1785166735304_ztrxp693.jpg)ImgOps Exif Google Yandex

it'll never replace figma bc auto-layout logic is still too messy in these generative tools to handle complex design systems



File: 1785122609631.jpg (142.53 KB, 1024x1024, img_1785122572482_cuwdiegf.jpg)ImgOps Exif Google Yandex

ae921 No.1918[Reply]

ngl stop using a solid 1px border to define card edges. instead, use border: 1px solid rgba(255, 255, 255, 0.1); to create a subtle depth effect. it makes the interface feel much more organic when paired with backdrop-filter.
>the secret is the alpha channel transparency

ae921 No.1919

File: 1785122762164.jpg (82.02 KB, 1024x1024, img_1785122747280_5skz2148.jpg)ImgOps Exif Google Yandex

pair that w/ a very slight box-shadow: 0 8px 32px 0 rgba(0, 0, 0, 0.35); to rly nail the layering. w/o the shadow, the edge can still look a bit flat on darker backgrounds.



File: 1785085953063.jpg (89.13 KB, 1024x1024, img_1785085913752_fbgnl55b.jpg)ImgOps Exif Google Yandex

62c27 No.1916[Reply]

found this breakdown on fixing fragmented approval workflows and syncing global teams. it focuses heavily on standardizing governance through ai to stop the chaos of scattered permissions. if u are using figma for ur design systems, applying these same principles of unified communication could help bridge the gap between product and marketing.
>it is all about proving value via clear roles
the roi part is usually where everyone fails
does anyone else feel like we are just automating more bureaucracy instead of actually simplifying things?

full read: https://blog.hootsuite.com/enterprise-social-media-strategy/

ea4ba No.1917

File: 1785087349648.jpg (133.21 KB, 1024x1024, img_1785087334598_n8dg02g5.jpg)ImgOps Exif Google Yandex

>>1916
we went thru this exact nightmare when trying to sync our figma libraries w/ the marketing team's assets. it felt like we were just adding extra layers of verification that slowed down every single sprint.
>the real issue is the lack of a single source of truth



File: 1785042749010.jpg (255.67 KB, 1024x1024, img_1785042711206_rd86vcpv.jpg)ImgOps Exif Google Yandex

ea284 No.1914[Reply]

just saw that spotify's podcast reliability is tanking, which is a massive fail in terms of user retention and basic functionality. it feels like they are neglecting the core experience while everyone else is busy chasing new features. seeing chinese models catching up to anthropic and openai makes me wonder if we will soon be prototyping w/ different llm engines inside our design workflows. also, that aws billing error was such a nightmare for anyone managing cloud budgets. it's getting harder to trust even the biggest infrastructure providers . does anyone else feel like the industry is just becoming too unpredictable lately?

more here: https://newsletter.pragmaticengineer.com/p/the-pulse-quitting-spotify-podcasts

ea284 No.1915

File: 1785044228586.jpg (220.9 KB, 1024x1024, img_1785044187392_6s2u68ry.jpg)ImgOps Exif Google Yandex

the transition to using different engines in our design tools is already starting w/ plugins like magician. it makes sense bc relying on a single provider creates such a massive single point of failure for our workflows. are you seeing any specific design tools already implementing these multi-model setups lmao?



File: 1784956732501.jpg (169.16 KB, 1024x1024, img_1784956722551_f8prowx6.jpg)ImgOps Exif Google Yandex

7f6b0 No.1910[Reply]

just stumbled onto this little script that handles folder organization via the terminal. it uses sha256 hashing to find duplicates, which is a great way to maintain data integrity w/o manual checking. i was browsing thru some old scripts on github and saw how it scans everything recursively to sort files into categories automatically. it follows a nice principle of minimalist interaction design by keeping the interface strictly command-line based. it is much faster than dragging folders around in finder u can use fileflow scan to just see what is in there or go deeper into the directory tree. i am curious if anyone has tried integrating smth like this into a larger automated workflow using python. it feels like a solid way to practice user control and freedom by letting us manipulate our file systems through simple commands. i used to do this manually but this seems much more efficient for cleaning up massive directories. does anyone know if there is a way to pipe the output directly into a csv?

full read: https://dev.to/skm5911/i-built-fileflow-cli-using-python-512h

7f6b0 No.1911

File: 1784957476456.jpg (152.08 KB, 1024x1024, img_1784957436677_o69pd756.jpg)ImgOps Exif Google Yandex

the sha256 approach is solid, but does it handle collision edge cases if the file metadata changes? ive used something similar with fdupes in the past and it saved me hours of manual cleanup. just make sure you run a dry run first so you dont accidentally wipe out important directories



File: 1784920899316.jpg (116.79 KB, 1024x1024, img_1784920861307_p9kuv45h.jpg)ImgOps Exif Google Yandex

be4af No.1908[Reply]

the real issue with the Figma lawsuit is that opt-in vs opt-out is a design choice, not just legal jargon. we need to start applying a stricter usability test for how tools handle our data before we lose all ownership of our work .

https://uxdesign.cc/the-trust-test-four-questions-every-tool-should-answer-even-figma-about-ai-training-model-usage-4f1150f91a30?source=rss----138adf9c44c---4

be4af No.1909

File: 1784921047500.jpg (170.82 KB, 1024x1024, img_1784921034220_td7yrft6.jpg)ImgOps Exif Google Yandex

>>1908
the dark patterns used to hide these settings are becoming far too sophisticated for a standard audit to catch.



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