Live data from Hacker News

Nobody designs for small iPhone devices anymore

lwgmnz.me

241–250 of 267 posts

Re: Nobody designs for small iPhone devices anymore

#241

Earlier quoted context omitted.

> you clearly know the culture behind it is not sustainable and has no future. It's not a culture shift, it's a technology shift. Systemwide shared-libraries are going away because they involve all-manner of versioning difficulties (DLL-Hell, etc). Simultaneously, computers have enough physical memory such that processes don't need to share libraries in-memory to keep usage low, and the security advantages of single-…

I'm a big fan of static builds. But cannot understand how a 15MB test IPA becomes a 70MB production IPA and takes 300MB to upload. That's IMO software explosion and bloat as Niklaus Wirth ranted on decades ago.

I'm guessing you're using SwiftUI? When you do that, it bundles the entire Swift UI library, including all the parts you're not using, in your package - I think that's because they support runtime-defined UIs which means your app might use currently-unused Swift UI components in future...

I assume you've also seen this article? https://developer.apple.com/documentation/xcode/reducing_you...

Re: Nobody designs for small iPhone devices anymore

#243
post #217
post #214

Earlier quoted context omitted.

> Negative space is good Yeah, no. There's spacing, and there's useless void - negative space is usually being the latter. Websites becoming ridiculous on computers, because everyone keeps designing for fat greasy fingers, and this trend is absolutely horrible.

You know that a proper website is designed differently at different breakpoints right? What you see on a computer screen is not designed based on fingers taps. Of course there are cases where it's taken too far. Not arguing that there isn't bad design out there. But again, negative space is good. It's proven better for comprehension and accessibility

[deleted]

Re: Nobody designs for small iPhone devices anymore

#244

Earlier quoted context omitted.

I'm a big fan of static builds. But cannot understand how a 15MB test IPA becomes a 70MB production IPA and takes 300MB to upload. That's IMO software explosion and bloat as Niklaus Wirth ranted on decades ago.

I'm guessing you're using SwiftUI? When you do that, it bundles the entire Swift UI library, including all the parts you're not using, in your package - I think that's because they support runtime-defined UIs which means your app might use currently-unused Swift UI components in future... I assume you've also seen this article? https://developer.apple.com/documentation/xcode/reducing_you...

No SwiftUI, backwards compatible to iOS 9.0, check the source if interested https://github.com/mro/ShaarliOS

Thanks for the link, I doubt it applies.

Re: Nobody designs for small iPhone devices anymore

#245

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.

You can actually hotlink directly to the Settings page for your app (e.g. Slack does this in their settings).

Re: Nobody designs for small iPhone devices anymore

#246
post #51

Earlier quoted context omitted.

The worst thing is they have a great wakeup time picker (not a generic time picker) for the "Bedtime/Wake Up" feature. That this feature, a completely separate alarm clock logic, even exists is insane.

I use it but it’s really weird that there are two disconnected alarm clocks.

And the input for timers is yet another custom UI where you can’t enter the time with a numpad.

Re: Nobody designs for small iPhone devices anymore

#247
I find it strange that these big companies aren't testing across a broad range of devices. I'm a solo freelancer, but the last app I built for a client, I actually went out and bought an iPhone SE, because that was the minimum spec.

Granted I don't load it onto that phone often, but I checked that it worked as expected, and the layout behaved reasonably.

An iPhone SE (not 2020) will set you back less than $100.

Anything that teenagers use (e.g. Spotify) you have to assume it'll be run across all kinds of budget devices.

Re: Nobody designs for small iPhone devices anymore

#248
I blame the CSS spec for not giving us responsive text sizes. It’s 2021, the Internet was literally built on text, and we still can’t have text that automatically grows and shrinks based on the size of its parent. We can go to Mars, but we can’t have responsive text. Blows my mind.

Re: Nobody designs for small iPhone devices anymore

#249

Earlier quoted context omitted.

While we're on the topic: YouTube, which is inherently a video content viewing service, goes out of its way to obscure the video content. The TV app, the mobile app, and the browser app all insist on overlaying the content with random garbage that no sane human being could possibly be more interested in that the content that they launched with the intention of watching! Heaven help you if you open a popular live feed…

You can turn off chat

What are you talking about? I just clicked through the "Settings" menu, and there's no such option!

Oh, you mean individually, on a per-video basis, using the tiny button that's thoroughly hidden as part of the dark pattern to drive user engagement?

Re: Nobody designs for small iPhone devices anymore

#250
post #214
post #191

Without even debating the pertinence and aggressiveness of this article's title, some of these examples are just ridiculous. Negative space is good. It's good for readability and accessibility. Nowadays, most apps are designed to be scrollable, which means that cramping as much information as possible is probably not helpful. >There’s too much padding on the navigation bar. For me it’s too much for my small phone and…

> Negative space is good Yeah, no. There's spacing, and there's useless void - negative space is usually being the latter. Websites becoming ridiculous on computers, because everyone keeps designing for fat greasy fingers, and this trend is absolutely horrible.

You just proved his point though.
Post reply on HN