so voice is great when you can talk out loud. touch is great when you can look at a screen and use both hands. but there's a ton of moments that fit neither.

you're in a meeting. on a train. someone's asleep next to you. your hands are full and it's not a good time to talk. and you just wanna do one small thing, skip a song, turn something off, reply with a yes.

what do you even use there? a tap on a watch, a gesture, a button, something else. honestly i can't think of a great answer that works for most people.

has anyone designed for this gap, or is it just unlocked phone by default?

So we do moderated usability sessions every quarter and they're fine, but it's like 20 people in a controlled setup doing tasks we basically handed them meanwhile there's 50k monthly actives in the app and i honestly have no idea what most of them are doing analytics shows me where they drop off but not why like what were they stuck on right before they bailed I've been wondering if session replay on native mobile is actually worth it for this on web it seems pretty solid but for ios/android i keep hearing mixed things and i'm worried it turns into hundreds of hours of recordings nobody watches lol

I looked at a few tools but it's hard to tell from demos how useful any of them are in real life anyone running replay on a native app actually find stuff you'd never catch in a moderated study ? and how do you even pick which sessions to watch when you have that much volume

I'm not looking to ditch the moderated sessions btw, just want to know if this makes them less of a shot in the dark.

Our team creates websites for businesses, and we’re used to looking at them through the lens of design, structure, logic, conversions, and other professional considerations. But when you work on something for a long time, it’s easy to stop noticing things that are obvious to the user.

As regular users, what do you look for? For example, do you generally pay attention to good design, the product and portfolio, reviews, prices, company information, an easy way to get in touch, or something else?

What might turn you off in the first few minutes, and what builds loyalty and trust?

Earlier testers said anything under ~5 seconds felt "too early", so I raised the threshold and added a 10-second grace period at the start. I'd like to know if that fixed it.
Prototype (1 min, no signup): https://quiet-hci.pages.dev/?src=ux
Does it match how you'd want a tool to behave, or is "wait for hesitation" the wrong signal?

I have a question and the question is - is it possible, that Reddit may add, an auto translate function in the 3 horizontal dots, next to the share feature, that is underneath the entered comment?

Excessive onboarding is a major gripe I have with a lot of apps, especially those that are local-first.

Either they highlight the same features as the screenshots in the app store, or the hold your hand through obvious and tedious flows, intimidating permission grants, forced paywalls and then finally hit you with a login. I think if you're an established brand and reputation you can survive this friction, but for most startups, surely this has to be seen as an anti-pattern?

I'm not guilt free in this, either; my first side project Instillr is a photo app that guided you through features, permissions and the setup process of a photo album. But users dropped like flies by the third slide; only 1/4 users actually stuck around long enough to take a photo in my photo app. I was devastated. So I tightened it up, made it much more visually appealing and give interactive examples of the outcomes you can expect from the app, without wasting the user's time. The number of users who took their first photo shot up to 3/4. So a lot better, but still not perfect.

For my latest app, a screen time control suite called Screentide, I've not included a single onboarding slide. I made this decision after spending minutes being scolded in competitor apps for how much of my life I was wasting on my phone. I personally don't respond well to being guilted like that; users already know they need the app, or they wouldn't have downloaded it. Opal, a very popular screen time app, was one of the worst offenders and takes about 5 minutes to complete the onboarding due to slowly revealed text telling you how bad you are at life. This is an app designed to reduce screen time!

That's not to say my app is unguided. Rather, it launches sheet flow whenever a user creates an entity, like a screen time rule. My bet is that this creates trust through autonomy by not forcing a use case on them, and bombarding them with questions when they're really just trying to answer "does this app do x?"

But in testing, what was interesting was seeing where users went the moment they first opened the app. Do they immediately create a rule? View the calendar? Check the pricing? I expected most people to immediately create a rule, but only 60% of people did that. The rest explored. What was interesting was many people went to the calendar and spent some time there, because it was a feature not many other apps in this space offer. My hope is these early signals will give great insight into what is attracting users to my app once I get a few more in the door.

On the flip side, I've already had some testers ask why there wasn't any onboarding, perhaps out habit. There is every chance I add a few slides in the near future, too, and run an A/B test, just because they are somewhat comforting and give a professional vibe.

Time will tell if this was a good idea, as my app just launched today!

So over to you....

When does app onboarding become an anti-pattern?

Have you found the sweet spot for how many slides and/or what kind of slides retain users best, or turn them away the most?

Most keen to hear from anyone who has done extensive A/B tests, or any evidence collation, around this question.

Context first: I've been a product designer in tech for a few years and started using Claude Design (C.D) for rapid prototyping and refining explorations. However the bridge to continue working in Figma after refining in C.D is pretty poor.

To speed up my workflow I've been creating a Figma plugin that lets me easily turn my html prototypes into full Figma flows that are even created from editable local components with DS atoms all instantly. Formatted exactly how I like to map flows.

For me my progress so far is looking like it could be a game-changer to speeding up my workflow.

I'm curious:

Would anyone else find this useful? / Should I bother releasing it on Figma community?

Is there any problem like this you'd be willing to pay for a solution that solves it well?

Happy to hear if this is absolutely useless to you!

I am working on what is likely going to be a dev tool (although it has other use cases, like demos).

What are some examples of really good UX for highly technical products, Dev Tools, Hosting, Security tools.

I come from the space and outside of some of the IDEs I am yet to find a really good user experience in the wild, particularly when it is a hybrid experience.

I remember getting Instagram dark mode before everyone else and literally posting it on my Story like I'd been selected for the Avengers.

Now I'm 23 and I can't stand it.

Give me black text on a white background.

Especially when I'm reading.

Maybe I'm getting old.

Maybe I've matured.

Or maybe dark mode just sucks. 😂

Light mode people, where are you?

Full Read: https://jaainil.com/articles/i-used-to-love-dark-mode-now-i-hate-it-heres-why

Hypervoice by TaskAGI is a TTS service.

When you pay money and subscribe, both the terms and conditions and the refund policy state that upon cancellation of the subscription, you will retain your access until the end of your billing period.

But as seen in image 1, the moment you go to turn off auto renewal, you are faced with the big orange warning and the moment you click confirm to unsubscribe, all your tokens are confiscated and all access to paid features is revoked - even if you have a full billing term ahead of you.

Hey. I added two pictures of a UI. Ignore all the stuff other than inputs and buttons, the other elements are just there to give you a feeling as if its baked into a UI. My question is, if you like the 36px-version (tinier first one) more or the 40px-version (bigger second one). Im thinking of migrating my package from 40px to 36px.

Hey. Currently working on a DateRangePicker and need your opinions. Do you think the second-date-invalidity I show currently by making the second selection-cell red with an icon is good or do you think i should just mark all invalid fields as disabled after the first date is selected?

As we all now it's common for a UX designer (or Product designer or UX/UI or whatever the trend is in your area) to be 'splained user needs, discovery, design by their product team. Or ignored. Or having their deadlines dismissed.

What I see too often (but maybe it's because I'm a woman ?) is designers doing this to researchers. Being explained heuristics, being handed over assignments last minute, dismissing our remarks because they, too, do research so they know.

How common is it and most importantly, how do you handle it ?

Designers : why ? Do you catch yourself doing this ? Where does it come from (because I'm sure there is a legit reason why some of you do this... maybe very similar to why PrD crowd do it to you...) ?

Post your portfolio or something else you've designed to receive a critique. Generally, users who include additional context and explanations receive more (and better) feedback.

Critiquers: Feedback should be supported with best practices, personal experience, or research! Try to provide reasoning behind your critiques. Those who post don't only your opinion, but guidance on how to improve their portfolios based on best practices, experience in the industry, and research. Just like in your day-to-day jobs, back up your assertions with reasoning.

Are you beginning your UX career and have questions? Post your questions below and we hope that our experienced members will help you get them answered!

Posting Tips Keep in mind that readers only have so much time (Provide essential details, Keep it brief, Consider using headings, lists, etc. to help people skim).

Search before asking Consider that your question may have been answered. CRTL+F keywords in this thread and search the subreddit.

Thank those who are helpful Consider upvoting, commenting your appreciation and how they were helpful, or gilding.

An error state crosses several responsibilities. Engineering knows what failed, product knows what actions are allowed, design controls hierarchy and placement, and content design may own the language. When ownership is unclear, the interface often exposes a technical message or gives the user no useful next step. What process keeps error copy, recovery actions, support guidance, and logging aligned as the product changes? Is there a source of truth that has worked well across teams?