I think the principle about a "Single Primary Action" per screen heavily depends on the type of app you're building, and which use case you're optimizing for.
Sometimes, especially for power users of an app, it's useful to have multiple actions at their fingertips, even at the cost of introducing a learning curve.
I think the one primary action per page thing works well for most things, but as soon as you're building anything like creativity tools where people want multiple editing options, or a control panel that you expect will be used by a professional several times a day, I think that principle becomes less useful.
I think there's a fundamental difference between a story and a math proof. A math proof is mostly there to give you new knowledge.
While a story definitely can do that, for many people, they're also about human connection. Even if the story isn't true, you feel like you're getting a look inside the author's brain by discovering how they weave storylines together. All the life experience they've head that lead them to write this story.
If I was instead told the story was written by AI, I would be far less interested in what data it was trained on to be able to produce this story, because I cannot relate to an AI having any "experience" whatsoever.
It's a site that lets you call a number to pretty instantly make changes to the website. Not sure how long it's gonna change un-trolled, but I think it's pretty neat!
It might be a small thing to take a principled stance on, given all the bigger things going on in the world, but I've never listened to podcass on Spotify or any other platform that has exclusiev podcasts without an RSS feed. Because to me the fact that they use an open standard, RSS, is an intrinsic characteristic of podcasts, and anything that doesn't, shouldn't be allowed to call itself a podcast.
This looks very promising! Being visually impaired, I often worry that I miss things about form when watching workout videos demonstrating an exercise. If this app could give me feedback to improve my form, that's wonderful.
Yes! Just make sure to turn up your volume so you can hear your feedback! Full honesty, we didn't think too much about the visually impaired. We do highlight the mistakes you made on your body using red. If there's something that we should be considerate of as well, would appreciate your input!
Challenges and programs are free try! Just swipe down on the paywall. As one commentor mentioned, there is a paywall for workout customization features. Thank you!
Being visually impaired, I love the independence that the public transport network in Central Europe gives me. I live in the Netherlands, and frequently visit my parents in Belgium. I've also visited friends in Germany, all without relying on a sighted companion for transportation.
This sort of OS advantage is why companies are now required to show you available options when you furst use certain features. I'm not saying the current approach here is the best mitigation, but for instance on IOS during the OS setup, you're asked to pick a default browser. Similarly on Chrome on a new machine, I was recently asked to pick a search engine before I could use the search bar, showing several options.
I'm slightly worried about permissions evaluating to "true" if they're not specified. I think this will lead to a lot of actions being accidentally allowed.
We wanted to lean towards a faster getting started experience. We are thinking about options to change the default, or introducing a kind of 'wildcard' in permissions.
We're always building abstractions on top of abstractions, that's how your whole computer works! Like, Assembly is an abstraction over binary instructions, compiled languages are an abstraction over assembly, etc, etc.
I'm toying a bit with this tool, and I think it's incredibly useful for prototyping.
Toasts showing up far from where the action is take also makes them super annoying for people (like me) who use screen magnifiers. I'm oftne using a site while zoomed in, and will completely miss a toast, because it never enters the "viewport" on the screen I'm looking at.
What kind of design choices do you find helpful with using a magnifier like that? It's not something I'd ever considered before, sounds tricky to design for but I'll try to keep it in mind now.
- Put cause and effect close to eachother
- Don't block my view based on mouse position. I hate video players that ofverlay the pause button when the mouse is over the video, or images that get obscured by some overlay when hovered. My zoom follows the mouse, so I can't move what I'm looking at and where my mouse is pointing independently.
> I hate video players that overlay the pause button when the mouse is over the video, or images that get obscured by some overlay when hovered.
This shit is super annoying for everyone. Even people who do not use magnifiers. Who decided that this was a thing to do and why? I would like this pattern to meet sudden death.
Oh yeah those video players are awful for anyone on mobile too, always ends up somehow getting stuck active and the only way to dismiss it is tap the video, which of course is usually bound to some other disruptive action like pausing or exiting full-screen mode.
Adding to your examples, I hate when video players (both mobile or desktop) don't let me hide the video player controls when the player is paused! I also dislike having to wait a few seconds upon starting/resuming a video for the controls to fade away.
> I hate when video players (both mobile or desktop) don't let me hide the video player controls when the player is paused!
Agreed. This is exceptionally annoying! Who thought this was a good idea? Why don't people copy proven video interface behavior from Google. Why go out of your way to annoy your users?
> I also dislike having to wait a few seconds upon starting/resuming a video for the controls to fade away.
I get the annoyance, but especially on mobile, it conversely helps if you want to advance the video by as few frames as possible to catch a freeze-frame gag or something like that. If the UI immediately disappeared upon resume, you'd have to triple tap to immediately pause the video again. (On desktop you can just mash the keyboard or even use a dedicated "advance one frame" key, but on mobile that's not available.)
I sometimes use a Bluetooth speaker on mobile just so I have a pause button handy. Playing a video full screen requires me to tap once to bring up the controls, and then again to pause.
Good questions - also note that fixes that would help magnifier people also benefit users who have overlapping windows and/or windows partially off-screen. (This is also an example of accessibility features helping people who are "fully-abled")
Sometimes, especially for power users of an app, it's useful to have multiple actions at their fingertips, even at the cost of introducing a learning curve.
I think the one primary action per page thing works well for most things, but as soon as you're building anything like creativity tools where people want multiple editing options, or a control panel that you expect will be used by a professional several times a day, I think that principle becomes less useful.