Live data from Hacker News

Designing Websites for iPhone X

webkit.org

131–135 of 135 posts

Re: Designing Websites for iPhone X

#131

Earlier quoted context omitted.

The current consensus among browser implementors is that, on the whole, prefixed properties have hurt more than they’ve helped. So, WebKit’s new policy is to implement experimental features unprefixed, behind a runtime flag. : https://webkit.org/blog/6131/updating-our-prefixing-policy/ As the article states, prefixes have created a set of problems, which is why Apple, Google, Mozilla and Microsoft stopped using them…

But the things they added aren't behind a runtime flag, but enabled by default and without any prefix, yet not standardized.

https://www.w3.org/TR/css-2017/#future-proofing is the current WG policy.

I have no idea whether or not there's a WG resolution because the WG is terrible at tracking resolutions.

Re: Designing Websites for iPhone X

#133
post #123
post #58

I like that the Webkit team decided to use standard features to solve this, but OTOH having to add custom safe areas for a single device goes against any common sense. No Apple, we won't change all our websites for your new gimmick.

Apple isn’t asking you to do anything. They’re just describing how to customize the behavior if you want to .

My point is that the simple fact Apple is even thinking about the possibility is wrong.

Re: Designing Websites for iPhone X

#134
post #40

What a mess. My condolences to the Apple engineers who had to implement this. The notch is probably something that marketing thinks is really important for branding reasons, but I'd guess most engineers dislike it. Yet some of them had to add all this complexity to their codebase.

I think Apple (and especially Ive) would definitely prefer if the phone was notchless and 100% display.

The issue is where you put the various sensors on the front - even with just a camera you’re still going to have a notch (see the Essential phone) until we can use these sensors behind an OLED screen.

Phone manufacturers are going to be shooting for the bezelless design for the foreseeable future so this issue isn’t something that’s going to be isolated to Apple alone.

The alternative is an asymmetrical bezel, which is “less sexy and cool” than the (mostly) edgeless design. Defaulting to this avoids the problem, but you’re no longer hip.

This is another weird case of being in a transitionary period (wireless headphones is another) of functional design. Until the kinks are worked out, we’re just gonna have to deal with the weirdness because it’s not going away.

Re: Designing Websites for iPhone X

#135

Earlier quoted context omitted.

And in some cases, the bewildering array of options makes the decision difficult. I don't even know if the X is actually better than the 8 for me, let alone whether it's worth the price premium. Things have really gone sideways with the X, because there's no longer an obvious best. The X is worse than the 8 in important ways, like no Touch ID and no home button. It's better in other ways. Which one wins? I don't know…

Things have really gone sideways with the X, because there's no longer an obvious best. The X is worse than the 8 in important ways, like no Touch ID and no home button. It's better in other ways. Which one wins? I don't know. I think you're over thinking this—the iPhone X is by far the best phone anyone has ever made. Think of it as the deluxe iPhone 8. You're assuming Face-ID is a detriment; however, Apple wouldn't…

>You're assuming Face-ID is a detriment; however, Apple wouldn't have shipped it unless it was as at least as good as Touch-ID.

What an odd argument. Couldn't you have used the same argument for removing the headphone jack? And yet, the iPhone 7's lack of one was a detriment to me.

Post reply on HN