221–230 of 267 posts
Earlier quoted context omitted.
What if you're not sure if you want to trigger the effect of the button?
Unless I’m missing something we’re talking about a tab bar? The worst thing that can happen is that you switch to that tab. Switching tabs should never be destructive.
Earlier quoted context omitted.
The alternative to hamburger menus is to design your app navigation so you don’t need them. Use the settings app for settings, so they don’t clutter your app. Have the user tap an ‘account’ control to do account related things like logout or change passwords. The problem is (oversimplified) these developers start with 20 things they want to show, and then they pick 4 things they can cram in the toolbar and the rest i…
> Use the settings app for settings, so they don’t clutter your app. I’m glad most app don’t do this, except for where they have to for notifications, etc. It’s really unintuitive to go to another app to adjust settings for an app you’re already in.
Instead, superior designers will show very little and explain nothing so the screen can look fabulous. If Apple has taught us anything, it is that fashionable appearance matters most. Users will just have to figure out that they need to leave this app, go open another app, navigate a few screens into it, see if there is an entry for this app, enter it, and scroll around hoping to see something in the master list that looks like it might be relevant to what you needed in the context that other app was in.
The Google Maps example is probably because most people want to see the list of results when you search for a category of businesses - the map is secondary. If you do want to see more map, you can just pull down on that handle at the top of the list or press the "View Larger Map" button.
Many of the other examples seem somewhat nitpicky, so I don't really think this supports the argument that nobody is designing for small devices.
A big part of the problem is people just not following the guidelines. If you have a toolbar with buttons that have labels, it’s not going to fit. But if you’re following the guidelines, you don’t have labels and it fits. If you have a list with a refresh button on the bottom you have to scroll to see that button on a small screen. But if you use the standard pull to refresh control, you don’t even need the button. I…
Earlier quoted context omitted.
Yep, too many UX professionals spend 95% of their energy on the look and maybe 5% on the feel.
I agree with this. I think design has a serious principle-agent problem. A beautiful design will live forever on your personal portfolio, but no one can directly experience usability there. So designers are fighting competing incentives to do what’s right for this product, and what’s right for their professional image. I think this is partly the cause for trend toward stylish-but-less-useable.
> Well, if you’ve been rocking the iPhone SE 2020 you would know If you’ve been rocking the original SE you’d know even better. Such a shame, it’s the best size phone I’ve had.
Likewise. It seems we will never see a comparable size flagship ever again though. I bought two new sealed box original SE's on eBay last year when they announced that the new SE would be larger, in the hopes they will last me for a while. I literally cannot imagine ever wanting another phone. It's without a doubt the best product Apple has ever designed.
That was the case when I owned iPhone 4S. I think that around iOS 9 it was poorly usable partially because developers ignored its dimensions. That's a pity. I still think that 3.5" is the best smartphone size and I would pay good money to buy modern smartphone with good internals. But it does not make sense, even if some Android manufacturer would create it, apps and websites will ruin it.
Earlier quoted context omitted.
Not supporting people jumping to bad conclusions or being toxic, but it's worth pointing out the author said this is the 2020 SE. Which is to say the body of an iPhone 8, not a 5. Which is to say roughly the same size as all iPhones before the X (and larger than the brand-new Mini!). That's not Edit: I was wrong about the mini being smaller; it's somewhat larger than the 8/SE
> Which is to say roughly the same size as all iPhones before the X (and larger than the brand-new Mini!) This isn’t about physical size, though; it’s about screen resolution and aspect ratio. > iPhone 12 mini: 2340×1080 @ 476dpi > iPhone SE 2020: 1334×750 @ 326dpi Yes, the 12 mini’s screen is 5.4” while the SE’s screen is 4.7”, but if the SE had the 12 mini’s DPI, it’d have a workable, modern-ish resolution. (Note h…
[0] https://iosref.com/res [1] https://www.paintcodeapp.com/news/iphone-6-screens-demystifi...
Earlier quoted context omitted.
I have followed the brilliance of google maps from an ux perspective for decades now, and don’t fault them that much for their new changes: it has become much more common now that I actually don’t care much about where a place is, more only about if I found the right place, and how do I get there. If I use public transit then the map becomes even more irrelevant. Given how good Googles places info is, the only time t…
Meanwhile, I get frustrated by the changes in their cartography style almost every time I use Google Maps. Most of the time I do want an actual map, and even when I’m not so fussed about that, the old style conveyed more useful details for the sorts of things I was doing. If you want to explore an area geographically, the changes have been terrible. It’s not uniformly worse than it was a decade ago; there are some ar…
No one designs for IE6 anymore either. If it costs a lot more to support a platform that doesn't bring in money, it would be a terrible business decision. "This is losing is a LOT of money, but it would be a nice thing to do" is not realistic.
The iPhone SE 2020 is hardly comparable to IE6.