I had a coworker still waiting on the iPhone Duo “pre-orders start soon page” while another had already placed their order. People are pretty annoyed.
My test device will be here only a few weeks after launch, could be worse.
Very strange system, is Apple still using WebObjects here??
This is not the most pressing issue on social media these days (obviously). But I despise photographers who do this. Your photos are content. Get over yourself.
If you add a border around your photo, and then upload it to the photography social network that populates a widget on my iPhone home screen, I’m blocking you. I’m opening the app, tapping your profile, and I’m blocking you forever.
And also: the restrictions on Siri phrases are so arcane lol. There’s a hard limit of 1000 phrase/parameter combinations (per locale) that gets hit silently (!) and seems to only be documented in a 2023 WWDC session.
I changed my iPhone into French yesterday to test some app shortcuts Siri phrases. Which booted me back to iOS 26 Siri (and stayed in English anyway??)
So I got to use iOS 26 Siri for the first time since June.
The iOS 27 Siri is not perfect, and it is a *qualified* improvement. But my goodness is it an improvement.
Maybe I’m just a Siri sicko, maybe everyone else either gave up on voice assistants or moved to Amazon or Google. But it’s nice after fifteen years to finally be able to tell Siri “remind me about the gazpacho.”
I'm loving Designed in California – particularly, the current "Apple's Mac OS Crisis" series.
I'm endlessly fascinated by this era of Apple. The failure of Pink, Taligent, Copland, BeOS, and more. Eventually Apple + NeXT succeeded but this required NeXT to be consumer focussed, Apple to be less dysfunctional and Jobs to overcome his "mercurial" nature and reluctance to rejoin his former company.
It could easily have gone so many other ways.
This is my first conference talk in over five years.
A retrospective on my professional detour to React Native, and then back towards native iOS development.
My slow return to a Swift career.
Archeologists in the future, "It was likely a religious or ritual object."
I don’t like ragging on OSS contributors, but Expo sells services as a part of their whole deal. I think it’s fair game here.
This SDK is the foundation they’ve built their business on, it’s the foundation they’ve been inviting developers to build their apps on for a decade, and there’s been a crack growing in it for six years.
And unlike a normal React Native app where devs could do the UIScene migration themselves, Expo apps *have* to wait for the project to release a new update. That is the value prop of Expo: it’s easier.
Follow-up: someone asked for an update from Expo yesterday about their UIScene support, now that iOS 27 is out publicly. (Expo is how many mobile apps use React Native).
The Expo project has locked the issue. Which is probably smart! Since developers are probably angry their apps are crashing. But it would have been smarter to fix this in the six years leading up to yesterday. Apple said at WWDC 2025 that this migration would be required soon, so even a year ago would have been prudent.
... I'm very tired (from making sure my apps respond to bounds changes)
it's this, or I go crazy thinking about the MS Surface Duo
"Please! Duodenum is my father's name, call me Duo."
“Welcome to React Native! BTW you need to upgrade to this prerelease version or YOUR APP DIES.”
I’m professionally qualified to say this is “typical of React Native”, and “lol“, and also “lmao”
What. The. Fucking. Hell.
React Native’s support for UIScene was merged only two weeks ago, and is currently in an RC. That means developers creating a new React Native app *today* won’t even have a resizable app. They also won’t be able to submit their app with Xcode 27 because iOS will crash it at launch.
I don’t know about the state of affairs on Flutter. But I generally don’t think that developers using cross-platform tools tend to give much weight to what Apple wants them to do.
The iPhone Duo needs apps to actually conform to its affordances, in order to deliver on the UX that its price tag implies. I suspect this will go very poorly.
I think that, maybe, asking iOS developers to redesign their apps in only a month (for the sake of a niche device that almost no users will own) is a tall order (after asking developers to redesign their apps just last summer).
The more I think about this, the more I think Apple is being unrealistic. I think it will bite them. But I’ve been wrong about this kind of thing before.
You know that feeling during WWDC 26 where it looked like there weren't a lot of changes required over the summer?
This is the opposite of that.
I’m afraid to learn the answers of how the safe area insets work on this thing
THIS ANSWER IS A MESSAGE... IT IS PART OF AN AUTOMATED SYSTEM OF MESSAGES... PAY ATTENTION TO IT, AS OPTIONS HAVE CHANGED!
YOUR CALL IS IMPORTANT TO US. WE CONSIDERED OURSELVES TO BE A POWERFUL COMPANY.
THIS CUSTOMER SERVICE LINE IS NOT A PLACE OF HONOR... NO HIGHLY ESTEEMED CORPORATION IS CONTRACTED HERE... NOTHING VALUED IS HERE.