Finally! So we have a little over a month between getting the simulator and first customers running our apps in Duo.<p>I expect that most apps will look rather broken on release, but it will be smoothed out eventually.
> I expect that most apps will look rather broken on release, but it will be smoothed out eventually.<p>I don’t think it'll be "most apps".<p>Apple all but told developers in June [1] to update their apps not to assume a fixed screen size.<p>One of the apps Apple's engineers demonstrate new features was called Origami [2]. When I watched the video, it seemed pretty clear: a device that folds was in our future.<p>If you’re a developer that's kept up with the latest iOS developments, you'll be in good shape for the Duo.<p>But if you're up to your eyeballs in technical debt using deprecated frameworks and APIs… it's probably gonna be a while for you.<p>[1]: <a href="https://developer.apple.com/videos/play/wwdc2026/278" rel="nofollow">https://developer.apple.com/videos/play/wwdc2026/278</a><p>[2]: "Modernize your UIKit app" — <a href="https://en.wikipedia.org/wiki/Origami" rel="nofollow">https://en.wikipedia.org/wiki/Origami</a>
Apps that support iPad are 95% fine unless you do crazy custom things (which Apple has been telling developers for decades now that they shouldn’t do), and apps that are phone only are letterboxed, but still entirely usable.<p>How many customers do you expect to be running on Duo for the first year of its existence?<p>I’d be surprised if it was >0.01% for anyone. Apple wants you to drop everything to support all the bells and whistles for their new device, but even if you take 3 months to fix minor layout bugs, I don’t think it’s that big of a deal.<p>I have friends who dropped everything to support the Vision Pro, and I don’t think any of them felt like it was worth it in retrospect. Even the ones that got featured by Apple as a result didn’t see more than a few thousand downloads.
> I have friends who dropped everything to support the Vision Pro, and I don’t think any of them felt like it was worth it in retrospect. Even the ones that got featured by Apple as a result didn’t see more than a few thousand downloads.<p>They should remember that they got quite a bit of social capital within Apple by doing that and hopefully they're keeping those relationships warm. But yeah Vision Pro hasn't turned out to be a big ecosystem so far.
> a bit of social capital within Apple by doing that and hopefully they're keeping those relationships warm<p>That social capital and $5 will buy me a cup of coffee.
Because Apple has always treated its developers so well!<p>Vision Pro will be cancelled at some point, it’s just nowhere near popular enough and never will be - the air has gone out of that VR bubble.<p>I wouldn’t be surprised if duo is also cancelled because it is another copycat move which is not central to Apples business and will not be mass market.
Usually just compiling with the new SDK will get apps basic support if they have been following Apple standards.<p>> I have friends who dropped everything to support the Vision Pro<p>The VP was a niche device for a niche market. Phones are not that. I think the Duo will do very well. The one knock are the cameras do not match the Pro. I don't think will care though.
> How many customers do you expect to be running on Duo for the first year of its existence?
I’d be surprised if it was >0.01% for anyone.<p>How do you figure? Assume the average Apple cell phone replacement cycle is somewhere between 3 and 4 years. At the longer end, you’d need the sell-through rate of the Duo compared to other phones to be less than 0.04% to hit your number. We know from the Mini and other phones that Apple tends to avoid designs that it expects to have less than a 5% sell rate, two orders of magnitude higher. Even if you assume they’re aiming for 5% of dollars instead of units, and you take into account the non-Apple market (which certainly should not be unit-weighted for folks thinking about app revenue), you’re off by well over an order of magnitude.
Apple does many crazy custom things in their own apps. Their advice is not sacrosanct. It just means you must prepare for less notice than they had if you want to compete with the frontier UI aspects that Apple apps achieve.
Fired it up to check my own app (RunnerCast) and it looks fine. The Liquid Glass menu moves from the bottom to the right side automatically both on the inner and outer screens. If you already had a layout that worked for iOS and iPadOS, things adapt fine to the inside screen and when you go split screen with two apps, the layout adapts nicely. I don't think I'll need to do a thing.<p>I've also noticed a flurry of recent app updates from some of the bigger apps (MLB, NYTimes, etc.) to switch to the Liquid Glass menu which I assume Apple strongly suggested they do prior to the Duo launch.
> some of the bigger apps to switch to the Liquid Glass<p>Interestingly, Instagram decided to implement a custom liquid-glass like tab bar which surely now turns to be a PITA.
It’s really interesting to note how the bigger apps deferred adopting Liquid Glass altogether until iOS 26 is out for almost a year. Do most developers making large apps also loathe it? Do they have in-house designers telling them not to adopt it?
Unless Apple uses their stick (whip, or whatever else) to drive the developer community, I bet iOS will experience the same app fragmentation as Android does regarding various form factors, more so than between iPad, iPhone and iWatch already.
"You are a experienced iOS Software Engineer, your task is to migrate this application to the iPhone Duo layout...
“Here is your iOS app migrated to Surface Duo…”<p>Tongue half in cheek, my point is that agents may be unreliable with fresh libraries.<p>It looks like there are some fun edge cases too:<p>> A reserved region can be active or inactive. For example, a reserved region that represents the fold is active when iPhone Duo is partially open, but inactive when it is fully open.<p>source: <a href="https://developer.apple.com/documentation/technologyoverviews/preparing-your-app-for-iphone-duo" rel="nofollow">https://developer.apple.com/documentation/technologyoverview...</a>
> <i>Tongue half in cheek, my point is that agents may be unreliable with fresh libraries.</i><p>You may find Axiom (my FOSS project, updated for iPhone Duo) helpful. <a href="https://charleswiltgen.github.io/Axiom/" rel="nofollow">https://charleswiltgen.github.io/Axiom/</a><p>Note: I'm scrubbing it against the final 27.1 beta SDK as I type this, so it's likely that its Duo knowledge will get an update within the next few hours.
Fun fact, I’ve now worked on the surface duo (technically the windows version not the android version) and the iPhone duo.<p>I thought the ideas of the surface duo were great and I’m super excited to see them evolved and shipped in a product that I think a lot of people are going to love.
Yeah, good luck with that.
<i>I expect that most apps will look rather broken on release, but it will be smoothed out eventually.</i><p>Sadly, many apps will continue to look rather broken.<p>There are still thousands of apps that still look wrong on iPad 16 years after its release, even with the 2x button pushed, for no good reason.<p>I think I heard that Instygram only recently figured it out.
Instagram released a Reels-first iPad app that is much, much worse than the old iPhone-on-iPad app.
To me that's said more about Instagram than the feasibility of building an app for a tablet.
Most apps people actually use will look fine because there's a team of mobile devs in all big companies who get paid to keep up with Apple breaking their apps every year with their 'updates' (among other things).<p>I mean, don't expect <i>advanced</i> features like consistent smooth scrolling, non-broken UI, absence of animation flickers, cloud sync that works consistently even for <i>paid</i> apps developed by Apple or anybody else but other than that :)
This is the first time we get an iPhone skew that is significantly different and with no sales track record.<p>For instance, very few company bothered to do anything for the Vision Pro. Now we'll see if Google or Microsoft for instance see the iPhone Duo as a main line product or an exotic offshoot that needs to prove itself before any money is spent on it.
In plenty of big companies one month is not even enough time to get a new release into production, let alone test and fix the layouts.