Lance Ulanoff (via Joe Rossignol):
Srouji told me that when Apple architects silicon, they start by looking three years out, which means the A11 Bionic was under development when Apple was shipping the iPhone 6 and its A8 chip. Back then we weren’t even talking about AI and machine learning at a mobile level and, yet, Srouji said, “The neural engine embed, it’s a bet we made three years ahead.”
[…]
The high-performance cores and efficiency cores introduced with the A10 Fusion CPU got an iterative update, including the addition of two more cores and the ability to handle asymmetric multi-processing, which means the chip can run 1, 2, 3, 4, 5, or 6 cores at once. Managing the core use on the now 10-nanometer CPU is one of the reasons the A11 Bionic, according to Apple, is 70 percent more energy efficient (even while being 25 percent faster than the A10). How the system decides which cores to use (high performance or high efficiency) and how many is a little non-obvious.
[…]
The secret sauce of a Neural Engine, what makes it different from other parts of the A11 Bionic, is its ability to handle matrix multiplications and floating-point processing.
Apple is not, however, opening this neural brain to everyone.
[…]
There are other things the A11 Bionic controls that Apple doesn’t often talk about, including the storage controller that includes custom error-correcting code (ECC) algorithms.
This last bit relates to APFS not checksumming its data blocks.
John Gruber:
I asked Apple last week what exactly was “bionic” about the A11 chip system. The answer, translated from Apple marketing-speak to plain English, is that The Bionic Man and Woman were cool, and the A11 chip is very cool. I think they’ve started giving these chips names in addition to numbers (last year’s was the A10 Fusion) because the numbers alone belie the true nature of how significant the improvements in these chips are. Going from A10 to A11 is like going from 10 to 11 mathematically, which implies a 10 percent improvement. That’s not the case at all here — the A11 is way more than a 10 percent improvement over the A10. So they’ve given it a name like “Bionic” to emphasize just how powerful it is.
Update (2017-09-22): Mark Spoonauer (via Phil Schiller):
The “Bionic” part in the name of Apple’s A11 Bionic chip isn’t just marketing speak. It’s the most powerful processor ever put in a mobile phone. We’ve put this chip to the test in both synthetic benchmarks and some real-world speed trials, and it obliterates every Android phone we tested.
[…]
The iPhone 8 even edged out the score from the 13-inch Apple MacBook Pro with a 7th-generation Core i5 processor. That notebook notched 9,213. Is Geekbench 4 really comparable from phone to desktop? According to the founder of Geekbench, John Poole, “the short is answer is yes that the scores are comparable across platforms, so if an iPhone 8 scores higher than an i5, then the iPhone 8 is faster than the i5.”
Update (2017-10-03): David Heinemeier Hansson:
Google Pixel scores a meager 50 on the JetStream JS benchmark. iPhone 8 is at 220. Almost 5x?!? Even iPhone 6S is at 128. Embarrassing.
Dan Masters:
As I’ve repeatedly said: if iOS is artificially slowing down basic tasks due to animations, it doesn’t matter how fast Apple’s chips become.
Apple A11 Apple File System (APFS) iOS iOS 11 iPhone 8 iPhone 8 Plus iPhone X Processors Storage
Jason Snell:
At long last, Apple Maps provides lane guidance, so you can see at a glance which lane you need to be in so that you can make your turn (or not make a turn you don’t want to make). In my testing, this feature was a bit spotty—at one point, a trip up the freeway didn’t show proper lane guidance, but the return trip down the freeway did. Still, when it’s there, it’s great, because it’s awfully nerve-wracking to not know whether you need to get over another lane.
Similarly, Apple Maps now displays the current Speed Limit for the road you’re driving on, a feature I’ve been using in other navigation apps for years. Again, better late than never.
Google Maps for iOS has had good lane guidance for a long time but doesn’t show the speed limit.
Update (2017-09-21): Ed Marczak:
Google Maps does show the speed limit…sometimes. It does in California, but not in NY, so 🤷
Corbin Davenport:
According to a post on the Android Auto support forum, the speed limit indicator is only live in the San Francisco Bay Area and Rio de Janeiro, Brazil.
Apple Maps Do Not Disturb Google Maps iOS iOS 11
Riccardo Mori:
From a hardware perspective, the cameras and sensors in that part of the iPhone couldn’t have realistically been placed anywhere else, so what do you do if you want an edge-to-edge display? You either have the display reach them, surround them; or you maintain a minimum of bezel on the ‘front’ and ‘chin’ of the phone, and leave them out of the display area.
[…]
Well, I can’t believe I’m writing this, but I actually prefer these two design choices over what Apple has done with the iPhone X. Like with the notch on the iPhone X, my eye is immediately attracted by the Essential Phone’s front camera, ‘breaking’ the display’s continuity there in the middle. Yet I think that it’s small enough to get enough out of the way aesthetically, and not be a hindrance to the phone’s user interface. More information can be displayed both to the left and right of the camera. To be fair, Apple had too much technology to cram there to achieve a similar, less visually annoying result. Then why not opt for a Samsung-inspired approach?
John Gruber:
I’m not on board with Apple’s “embrace the notch” user interface, but I do find it commendable that they showed the notch everywhere during the keynote Tuesday.
[…]
Ben Bajarin did get an answer from Apple on this at the event, and I was correct: the default is for video not to zoom to fill every pixel, so you won’t see the notch in video playback unless you double-tap.
Bryan Irace:
Remember when we first saw all of this wasted space and thought “Surely this will make sense on the new phone”? 🙄
Marco Arment:
I was hoping that the long-rumored edge-to-edge iPhone screen would still be a rectangle, possibly even with room for a Home button on a narrower bezel, so I wouldn’t have to change my habits (or my app’s layout).
[…]
Apple would’ve lost what the iPhone has had since its introduction: a unique, recognizable shape that distinguishes itself from all of the other boring rectangles out there.
John Gruber:
My objection (again, after admittedly only spending 10-15 minutes with an iPhone X in hand) remains that Apple could embrace the notch on the lock and home screens, allowing for this new iconic silhouette, without embracing it all the time.
Keith Harrison:
If you are not using safe area layout guides or layout margins there is a good chance your controls will end up too close to the device edges. The rounded edges, top central housing or bottom home indicator can clip, hide or overlay controls that would be fine on other iPhone models.
[…]
There is a new property (insetsContentViewsToSafeArea) on table views in iOS 11 that controls whether the content view of a table view cell is inset for the safe area. This is true by default which causes a subtle change with table views in landscape on an iPhone X.
Paul Haddad:
Feels like so much wasted space, landscape has less “safe” area than the 8.
Marco Arment:
The X’s biggest UI-design problem for me isn’t the notch — it’s the home indicator and the rounded screen corners.
iPhone UIs basically can’t use the four corners anymore. That’s not a small deal.
We’re going to have to add a lot of margins everywhere.
Will be challenging to have the same UI scale between the iPhone SE, 6/7/8, Plus, and X.
SE owners will get the worst UIs forced on them.
Joe Cieplinski:
I do have to wonder as well, why so many people seem obsessed with this edge-to-edge screen concept. It’s important enough for Apple to make a major design tradeoff with the notch, so it’s clearly a big deal to people. But as I’m reworking my apps to behave correctly on the X's screen, what I’m learning quickly is that all four far corners of the screen (the areas that used to be blank “chin” areas) are too inconvenient for thumbs to reach easily. Which means they are lousy for UI interactive elements. Thanks to the notch, and the fact that the phone is no longer 16 x 9, watching video full screen is a poor experience as well. So most of what’s important is going to end up in the “safe” areas—in other words, the exact dimensions of your iPhone 8 screen. Basically, we’re lighting up the edges of the X screen with background color and calling it a revolution.
NIELS:
Don’t place interactive controls at the bottom of the screen. The spacing around the home indicator is purely created for gestures, swipe up to go home. Placing buttons near this indicator or in the bottom round corners of the display might not be great. Users might accidentally use the home gesture and your UI will be difficult to reach. You can however still use tab bars and function bars, but keep in mind that they should not interfere with the home indicator.
Previously: iPhone X, iPhone and iPad Resolutions.
Update (2017-09-22): Max Rudberg:
These are explorations on how certain design patterns can be adapted to the new screen.
Update (2017-09-23): Chris Pirillo:
Is the iOS “Plus” landscape keyboard layout artificially cramped because we’re paying for the screen sins of the iPhone X?
Update (2017-09-27): Dan Masters:
If “all screen” is so important, why draw attention to the non-screen part with iOS’ bleed-through status bar design?
[…]
If for brand differentiation, why not simply show the bleed status bar on the home and lock screens (much like Springboard has become iconic in its own right), while at least having it black inside apps to keep the focus on the software experience?
Update (2017-09-29): Timothy Horton (via John Gruber):
Other pages — especially those designed with full-width horizontal navigation bars, like the page below — can optionally go a little further to take full advantage of the features of the new display. The iPhone X Human Interface Guidelines detail a few of the general design principles to keep in mind, and the UIKit documentation discusses specific mechanisms native apps can adopt to ensure that they look good. Your website can make use of a few similar new pieces of WebKit API introduced in iOS 11 to take full advantage of the edge-to-edge nature of the display.
Update (2017-10-03): Todd Ditchendorf:
When u ask your engineers to invent these kinds of hacks to work around your HW design…don’t u stop & reconsider it?
Marco Arment:
Can I just look at my layout on the landscape X and cry?
I’m sure we’ll all like the notch eventually, but damn, landscape is just awful.
Colin Cornaby:
Not completely offended by the notch, but I’m definitely not sure rounded display corners is a good idea for phone UI in general.
The notch is less disruptive than adding massive right/left/top/bottom margins specifically because of the curves.
Bob Burrough:
Bondi Blue iMac: shape defined by display
iMac G4: shape defined by display
iPhone: shape defined by display
iPhone X: display defined by shape
Ken Segall:
That’s why it makes me nervous when I see today’s Apple playing loose with words and images to sell a product.
Case in point: the “all-screen” iPhone X.
Of course we can see with our own eyes that iPhone X is not all-screen. It has a noticeable edge around the entire display, which even the Samsung S8 does not have. And then there is “the notch” — the object of many a critic’s venom.
[…]
“It’s all screen,” says the headline. Yet, astonishingly, the image focuses almost entirely on the only two parts of the phone that are not screen—the visible edge and the notch.
Update (2017-10-04): Peter-Paul Koch (via Hacker News):
During the introduction of the iPhone X a hilarious gif made the Twitter rounds, showing a list scrolling past the new notch.
I asked the question any web developer would ask: “Hey, is this even possible with web technology?” Turns out it is.
Max Rudberg (via Nick Heer):
In the same spirit as the first post (UI Design for iPhone X: Bottom Elements), this post will deal with designing for the iPhone X. I use findings in our own apps in some of the examples.
Update (2017-10-20): John Gruber:
But with the notch? No way. Here’s one simple way to think about it: what does Apple do 2-3 years from now if they ship an iPhone with no notch? Describe it as “Really all screen this time”?
Update (2017-10-21): Bob Burrough:
iPhone 1 bezel width: 4.64 mm
iPhone X bezel width: 3.91 mm
This is according to Apple’s developer documentation.
iPhone 5, 5S, 5C, SE all have bezel widths narrower than iPhone X.
Update (2018-01-23): Brad Ellis:
iPhone X rounded screen corners don’t use the classic rounding method where you move in a straight line and then arc using a single quadrant of a circle. Instead, the math is a bit more complicated. Commonly called a squircle, the slope starts sooner, but is more gentle.
Update (2018-09-03): Ryan Jones:
iPhone XS wallpaper does a stellar job of hiding the notch. Apple not embracing the notch.
Update (2018-10-26): Rob Griffiths:
The notch adds nothing to the iOS experience, but takes away much. Those stupid ears grab my eyes every time I see them, and there’s no way to avoid them, save never using anything but an all-black screen. When not in an app, they show status items on a black background, which is fine…as long as your iPhone’s wallpaper is also black.
But once you’re in an app, you’re in Notchville…
CSS Design iOS iOS 11 iPhone iPhone X Web
