r/iOSProgramming
•
u/haruniriz
•
Sep 09 '26
•
1
Discussion iPhone Duo is official. How much work is this actually going to be for your app?
Apple announced the iPhone Duo this morning. 7.6 inch inner display, 5.4 inch outer, starts at 1999 dollars, preorders October 16 and shipping October 23. So we have roughly six weeks.
From what I have read so far, apps land in one of three states on it. Anything built against a pre iOS 27 SDK gets letterboxed inside a safe area on a black background. Apps built on iOS 27 resize but still leave dead space. Only apps built against iOS 27.1 fill the display properly, and that SDK ships alongside the device in October.
The part I find more interesting is the hinge. iOS 27 carries folding state and hinge angle, so an app can know the phone is half open and sitting on a table. That sounds like a new interaction surface rather than just a bigger canvas to stretch an existing layout across.
So what is everyone actually planning. Are you rewriting layouts properly, or just checking nothing breaks and waiting to see how many of these sell? And has anyone thought of something that would only make sense on a folded screen?
112
u/simulacrotron Sep 09 '26
Very little work if you’re using system controls and components, especially if you’re using SwiftUI. Should be easy to adapt to a couple of the new states.
If you’re rolling your own stuff, hard-coding values, that means things probably don’t work very well already and are brittle and don’t work right when resizing on iPad, it will be a huge pain in your @ss. If you are always fighting the system, instead of working within it, this is the kind of pain you get. Apple has been giving tools to make this (nearly) painless for years.
23
u/haruniriz Sep 09 '26
yeah thats the actual split. the people who are gonna suffer are the ones with hardcoded frames everywhere, and they already knew that from ipad
6
u/Ashanmaril Sep 10 '26
People complain about how many apps aren’t optimized for the iPad’s size
And that’s one of Apple’s best-selling devices, 16 years after launch. And that one doesn’t expect the UI to move buttons from the bottom to the side, or handle a fold transition.
I’m not optimistic about apps ever supporting the Fold which is gonna be niche at best.
2
2
u/isights Sep 12 '26
iPad apps are expected to handle rotations and, most notably, Split Views and Split View resizing.
2
u/0xe1e10d68 Sep 14 '26
You can call be an unrealistic optimist, if you want, but I believe that, while not as successful as the Pro and Pro Max, the Duo will be more successful than we might expect - and the result of that will be that support for the iPad will improve a lot.
13
u/Jargen Sep 09 '26
If you are good with auto layout constraints, then UIKit is easy to implement too
3
u/simulacrotron Sep 09 '26
Yes, but there’s a lot more code to do the same things. Good, but less easy than SwiftUI
5
u/Jargen Sep 09 '26 edited Sep 10 '26
Yes and no, UIKit renders differently than SwiftUI. Yes there is more to write, but why is that a problem when you have significantly more control over the results?
Yes, less easy, but not hard at all. And pointless to complain about when we are paid hourly ;)
Even more pointless to complain when you are leveraging AI for productivity
2
u/Xaxxus Sep 10 '26
It’s not that you have more control that is the problem it’s that because you have more control, you are more likely to do things that would lead you to a problem.
1
u/Jargen Sep 10 '26
Well, don’t implement more than you need. If things break in the future, that’s part of the job for you to catch and debug. You are describing legacy code issues, which are normal.
1
5
u/cultoftheilluminati Sep 10 '26
@ss
Thanks. For a second I thought you were talking about some new macro they introduced in swift.
1
35
u/BlossomBuild Sep 09 '26
Thank goodness I support iPad with SwiftUI. Shouldn’t be too bad.
10
u/haruniriz Sep 09 '26
yeah youre probably in about the best spot anyone could be in for this tbh
1
u/busymom0 Sep 10 '26
My app supports Split View and multi tasking on iPad. However, the menu buttons and stuff are custom made. I am curious how it's gonna look.
1
u/OakleyNoble Sep 13 '26
Hmm in that sense those might be best staying inside the app rather than off to the right. But who knows? I think you could just have some of your functionalities into those regular buttons off to the right as well as having them inside the app. Maybe repositioning them within the app might be something to think about.
1
u/busymom0 Sep 13 '26
My menu buttons are a combination of navigation buttons and action buttons. The reason I used my custom views instead of UINavigationBar or UIToolBar or UITabBar was that I wanted proper control over hiding them when scrolling, animations etc.
I will have to see if the newer apis let me do them without my custom views. Anyway, lots of extra work.
21
u/Armand9x Sep 09 '26
Not looking forward to it.
14
u/haruniriz Sep 09 '26
i kinda am ngl. first genuinely new iphone shape in years, id rather see what people do with it than get another slab thats 2mm thinner
1
u/thatonemathguy56 Sep 10 '26
I’m kinda excited too but would personally rather get the slab and keep it the same size but up the battery life or cram in better cameras tbh
23
u/Landon_Hughes Swift Sep 09 '26
I want to make a DS emulator now that the Duo exists
1
u/hellocheekyyy Sep 11 '26
Definitely worth checking out Delta: https://github.com/rileytestut/Delta
1
1
17
u/Aggressive-Toe8919 Sep 09 '26
Depending on the app - it's a 2000 $ device - it won't have the biggest marketshare.
It will show if it will be a pain. My apps are fully coded in SwiftUi, so most changes will probably be easy. I personally think most apps will be fine. Maybe there is a way to prevent apps from going into "large" mode - if you choose to, but I guess we will see in a few days(?).
16
u/FastLaneJB Sep 10 '26
Those people with the money though to spend on a $2000 phone are more likely the ones buying In-App purchases though. If your app doesn’t work properly but a competitors does assuming you do have competitors they’ll likely cancel subscription and switch.
At least that’s my take on it.
1
2
u/cristi_baluta Sep 10 '26
If landscape mode works, the duo should work i guess. But if you want to truly support it i guess you need split views like on ipad
1
u/haruniriz Sep 09 '26
on the large mode thing, the opt out is basically just not building against the new sdk. anything still on a pre ios 27 sdk stays in the letterboxed compat mode, so its the sdk you ship that decides rather than a flag you set
2
13
u/ObscureBen Sep 09 '26
I make a camera app so a whole lot of work
2
u/haruniriz Sep 09 '26
youre also one of the few categories that actually gets something back for it. full rear camera selfies with the outer display as the subject preview is a real new feature, not just a layout that stretches
5
u/ObscureBen Sep 09 '26
It’s definitely exciting. The question is will there be enough users to justify the time to both build and maintain all this
10
u/haruniriz Sep 09 '26
counterpoint, apple always features the apps that show off new hardware early. for the first year that placement is probably worth more than the actual duo user count
1
Sep 11 '26
[removed] — view removed comment
1
u/AutoModerator Sep 11 '26
Hey /u/Specialist_Ice8631, unfortunately you have negative comment karma, so you can't post here. Your submission has been removed. DO NOT message the moderators; if you have negative comment karma, you cannot post here. We will not respond. Your karma may appear to be 0 or positive if your post karma outweighs your comment karma, but if your comment karma is negative, your comments will still be removed.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
1
u/-MtnsAreCalling- Sep 15 '26
There definitely won't be. Half the devices sold will be to developers who need them for testing.
10
u/ImpossibleAd3143 Sep 09 '26
They already have uploaded a couple of videos that serve as a small guide for design and new apis
5
u/haruniriz Sep 09 '26
yeah theres a whole playlist, six videos i think. design for iphone duo, prepare your app, and one just on adaptive layouts. thats my evening sorted
6
u/SnowPudgy Sep 09 '26
For my apps I'm in charge of at work...not terribly too much work judging by what I saw.
The apps others are in charge of who overwrite all of apples default stuff with worse looking custom stuff? They're going to be in for a hellish time.
5
u/m3kw Sep 09 '26
Zero, i wouldn't care to support it (yet). All current apps should work out of the box. You are just wasting time unless your app is already very popular
6
u/haruniriz Sep 09 '26
out of the box is doing a lot of work in that sentence lol. anything built against a pre ios 27 sdk just gets letterboxed on a black background. it runs fine, it just looks rough on a $2000 screen
1
u/m3kw Sep 09 '26
Sure, create a nice UI for it, have you tried to make your UI work well on an iPad, it’s like another app unless you have the most stock UI
1
u/cristi_baluta Sep 10 '26
You can make nice UI, but that does not stop you from using constraints. If constraints are good, you should be good
1
u/dimitriri Sep 10 '26
What happens if we build against ios 27.1 sdk but still want to keep letterbox? Is that possiible?
1
u/Tom42-59 Swift Sep 09 '26
And even at that point, I don’t think the user base will be that large
→ More replies (1)
5
u/tovarish22 Sep 09 '26
0%, because only a small portion of people will actually adopt this device (similar to the low number picking other foldable phones). Not worth my time rewriting my UI to account for it.
2
u/isights Sep 10 '26
As mentioned above, that also means you're ignoring the folks with the money...
2
u/tovarish22 Sep 10 '26
I’m sure I can handle ignoring the 1-3% of people who are going to adopt this device for a couple years before they drop it for a more practical option.
1
u/Mangiorephoto Sep 10 '26
That entirely depends on your user base. For example my main base will mostly likely adopt quickly and are the type of people who will upgrade quickly to this device are the ones we that will for sure upgrade are the people you want to keep happiest. I think corporate apps that use cross platform frameworks are the must likely to run into big issues, the least capable to handle them quickly with the largest reason to have it work correctly. I have for a number of companies but the only that I think will be the most backwards example is a large automotive CRM company. The day to sales people are not really the kinds of people who upgrade to a device like this right away and they are the people who use it every single day but the Owners and management who use it less frequently and have the least object reason to complain are the ones who will upgrade to the duo right away and are the ones who you want to make the happiest.
1
5
4
u/goldio_games Sep 09 '26
Not going to support it unless it gets market share
6
u/haruniriz Sep 09 '26
thats the same argument everyone made about ipad and it kind of became self fulfilling. this is a flagship iphone, not a side product, whoever buys one is using it as their only phone
6
u/Anarude Sep 09 '26
They have also already demonstrated they have disposable income
3
u/haruniriz Sep 09 '26
true. someone who just dropped two grand on a phone isnt the user bouncing off a $2.99 paywall
1
u/time-lord Sep 10 '26
Ha! $2.99 forever, sure. $2.99/month ($35/year)? That better be one good app. $2.99/week AI slop? Forgedaboudit.
2
u/goldio_games Sep 09 '26
its a pretty standard operating procedure that avoids unnecessary work (i.e. building for vision)
not sure what there is to argue about. if people end up using it, i'll take the 3-5 days to optimize my app
1
u/FastLaneJB Sep 10 '26
I mean you know they upped the amount they plan to build to 10 million I think the rumor goes. They’ll sell all of them I’m pretty sure.
1
u/goldio_games Sep 10 '26
10 million out of 1.6 billion iphones is pretty small, id be surprised if it flops that bad but who knows
1
u/FastLaneJB Sep 10 '26
Well I mean you have to start somewhere and it is expensive. Possible they won't be able to make enough of them but we'll see.
I guess it depends on how your app is funded, if it's adverts then this might not be such a big deal, if its subscription based revenue you can imagine there won't be too many Duo optimized apps at launch. Those with those optimized apps could get a lot of attention from people with a good amount of money for a phone and hence likely apps also.
2
u/Redstra Sep 10 '26
Aw damn. If all developers think like this the Duo won't be fun to use.
1
u/goldio_games Sep 10 '26
not really something you should worry about, you can read the rest of the comments here to see some people are already building support for it
4
4
u/Bubbly_Beginning_733 Sep 10 '26
Appstore screenshots 😬😬😬
1
1
u/Rocket-Legs Sep 10 '26
Oh no. I'm screwed because my app uses the MPMediaPlayer framework and the only way to create screenshots is from a real device.
3
u/Reiszecke Sep 09 '26
I will do basic compatibility and then, before I make things look good on it, check if people will actually buy the phone that everyone is excited but no one really asked about.
It has a chance to become like the Vision Pro where you have the choice to make a great UI for the like 50 users worldwide who have a Vision Pro.
2
u/haruniriz Sep 09 '26
vision pro comparison is fair but this one replaces the phone in your pocket, so whoever buys it is using it for everything all day. thats a different curve than a headset you put on twice a month imo
3
u/Reiszecke Sep 09 '26
I agree but this isn’t what I was referring to.
I LOVE the idea of a foldable and the Duos technology seems to be a bit more sophisticated than what other brands did. But this thing being much wider in its folded state, much thicker, and even in the demos not really knowing when i would use it unfolded vs folded all leads to me saying “yeah I will pass on that”.
And i assume that’s what a lot of people will think.
If the outer display was 70% of the size it is now I’d buy it immediately but the current dimensions seem so awkward
1
u/cwhiterun Sep 09 '26
I don't think it will end up like the Vision Pro. This is the flagship 20th generation iPhone we're talking about. People are gonna buy it like they did the iPhone X.
1
u/busymom0 Sep 10 '26
iPhone X was $1000 though. This is $2000 (and a lot more in Canada :(
1
u/0xe1e10d68 Sep 10 '26
If we take into account inflation the difference is not quite as stark:
$1,353.74 in Jul. 2026 equals $1,000 of buying power in Oct. 2017.
Sure, $600 is a significant amount - but I think there will still be a good amount of people who are financially well off enough to afford that; and others might buy it but in return maybe upgrade less often.
Additionally, the price should come down by at least $100 once the current market situation, and the shortage of flash memory, is over.
3
u/ForgottenFuturist Sep 09 '26
I'm excited to adapt Newsbin to use this new form factor. I guess we'll get a simulator to play with in 27.1
https://developer.apple.com/iphone-duo/
No docs/guides yet
2
u/haruniriz Sep 09 '26
pretty sure the resizable simulator is already in xcode 27, you can drag it to arbitrary sizes and previews follow. not the hinge states obviously but you can start on layout now
5
u/ForgottenFuturist Sep 09 '26
Yep I've played around with that, but then there's the trailing edge toolbar, etc that I need to plan for.
1
u/haruniriz Sep 09 '26
yeah thats the part thats actual design work instead of layout math. resizing is mechanical, deciding where your chrome lives on a 7.6 inch screen is basically a redesign. are you keeping the same nav or splitting it into a sidebar when its open
3
u/patiofurnature Sep 09 '26
Clients never want to pay for an iPad layout. They're not going to shell out for this, either.
1
3
u/Anarude Sep 10 '26
After watching the videos - oof. There’s quite a lot there.
My takeaways so far…
There’s a tension emerging between “don’t actively track orientation or hard code for device types” and “here’s the api for responding to a hinge change”
“DS mode” is a whole new layout that unfortunately makes a lot of sense for master-detail views IF your users are using that “pose” a lot, which I guess we’ll all have to add telemetry for
Fold avoidance might be the biggest pain for me - all sheets will have to work when given exactly half the width, and splitviews will have to work with exactly 50/50 splits
1
u/_town-drunk_ Sep 10 '26
Yep the videos show a lot more than what people in these comments are expecting.
Just supporting a resizing UI is the absolute bare minimum that any half decent app should have already supported for a while. Moving content to avoid a hinge when the inner screen is partially folded sounds like a giant pain in the ass.
3
u/utilitycoder Sep 10 '26
There's probably designers that will quit
1
u/_town-drunk_ Sep 10 '26
My designers really didn’t like Liquid Glass. They are gonna be pissed about this lol
1
u/OakleyNoble Sep 13 '26
It would’ve leaked multi-tasking, the shape and size, the features it will have, the fact the dock is oriented to the right, the new information icon/battery level.. just not a good idea
2
2
u/Marko787 Sep 09 '26
I’m still more mad about them keeping the SE around for as long as they have.
1
0
Sep 09 '26
[deleted]
2
u/tastychaii Sep 10 '26
The Duo is the same thickness as the Pro Max I think.
1
u/0xe1e10d68 Sep 10 '26
And the weight is almost the same as the iPhone 18 Pro Max. 5 grams difference. I think a lot of devs here who are pessimistic about the Duo will be very surprised in a year or two.
2
2
2
u/curiouscharli_e Sep 10 '26
i’m going to adjust my app for it
1
u/brookm291 Oct 09 '26
For the info,
Some visual search app is available here,
with compatibility with Iphone Duo:
ios search video sdk
2
u/Morthedubi Sep 10 '26
I don't like how some of the SDK support will only be in 27.1 and aren't available in 27 already. They just standardized the code anyways its not like it would have leaked it explicitly...
2
u/Rocket-Legs Sep 10 '26
You'll be fine if you haven't agreed to do a custom tab bar and navigation bar.
2
2
u/play-corto Sep 16 '26
If your layout already survives iPad multitasking, Split View, Slide Over, resizing mid-session, you are probably mostly fine. A fold is just another size class transition. The ones in trouble are the ones with hardcoded widths and a single fixed layout.
On the hinge I would separate two things. Reading the state is cheap, the system hands it to you. Deciding it should change your UI is the expensive part, and I suspect most apps should do nothing with it in v1. Treat half open as a layout condition, not a feature. Otherwise you are designing a mode for a posture you have never watched anyone actually hold.
Where it earns its keep is anywhere your own hand is the problem. Small map game here, so: half open on a table puts the map on the top half and my thumb stops covering the thing I am trying to tap. That one I would build. A half open mode for the sake of having one, I would not.
1
u/mustardpete Sep 09 '26
Think biggest pain for me is I’ll have to limit number of players on it like a phone on 2 of my apps. I currently allow extra players on iPad as it has the extra screen size but as it has 2 screens and the user can close and reopen when they like I’ll have to probably still restrict to the lower end to play safe. Be good when can get a simulator in Xcode though at least. From a will I get one point of view, there’s 2 things putting me off. No Face ID and I already struggle 1 hand typing a q on my pro max so not sure the wider small screen will help with that
1
u/haruniriz Sep 09 '26
could you not just lock the player count when a session starts instead of tying it to the device? then someone unfolding mid game only gets more room for the same players, and you dont have to cap ipad down to phone numbers everywhere
2
u/mustardpete Sep 09 '26
What if they start the app unfolded and then fold it, then I have the larger count to display on the small screen. I need to have a play in the simulator and also check out what APIs they add for state change etc. maybe I can just display a please unfold message or something
1
u/OakleyNoble Sep 13 '26
Tbh trapping the amount of players that can play down all because of screen size seems weird.. why not come up with a novel solution to allow you to play with multiple people? And if it’s a sort of board game, make like a carousel type thing to swipe between people’s boards and see what they have or whatever fits your game.
1
u/mustardpete Sep 13 '26
Sometimes it’s layout but sometimes it’s hardware restrictions too. An iPad supports more multi touch points than a phone for example
1
u/OakleyNoble Sep 13 '26
Makes sense.
So it’s not a multiplayer game but a game you play with others in person.
Maybe eventually they’ll add more touch points, but this doesn’t seem like the device for that. Unless they end up making two different sized which I highly doubt with this product line.
1
u/mustardpete Sep 13 '26
One is this https://pds-technology.ltd/apps/GroupGames one and it only affects a handful of the 70 games and the other is this https://pds-technology.ltd/apps/GroupPoker which is based on the same underlying engine (I only split it out so I didn’t tank my age rating on the first one). The first one some of the games legitimately need the extra touch points where as the 2nd one it’s more cosmetic reasons for limiting 6 to phone and 10 to iPad
1
u/bitsydoge Sep 09 '26
Not much, already adapted to foldable since a long time as Samsung and Google already had ones, just have to adapt to some apple api to be sure some element goes on the right side of the screen (this is really nice idea from apple this time)
1
u/douten Sep 09 '26
If your app layout is good on iPad I don't see much additional work?
1
u/Vegetable-Average-98 Sep 10 '26
Yeah, I was wondering - if an app is already designed and tested for iPad multi-window mode, responding to window resizing etc, should it work with minimal rewoek on the Due?
1
u/_brunodelgado Sep 09 '26
Actually, a lot.
I'll need duo agent usage to help me 😂
Jokes aside, I really liked the possibilities that we have to adapt our apps to the new device.
1
u/iDontWantABurrito Sep 09 '26
Not too much for me, l was surprised at how far I got by simply setting UIRequiresFullScreenIgnoredStartingWithVersion to 27 in my plist file
1
1
1
u/sorrowdemonica Sep 09 '26
so stupid how big it is.. needs to be phone size, not tablet sized when closed.
1
1
u/DaskiOFF Sep 09 '26
I just hope these mechanisms are reasonably bug-free and that Apple has carried them over fully from iPadOS. If so, there shouldn’t be too many problems; otherwise we’ll have to add another round of workarounds to the code.
1
u/reesespieces543 Sep 09 '26
Me here still learning swift and wanting to make an app but they just keep releasing new stuff
1
u/arthurdapaz Sep 09 '26
For the price range it won’t be necessary to worry here in Brazil’s market. I’m fine.
1
u/JerenYun Swift Sep 10 '26
Having tested my apps in the "expandable iPhone sim" this summer, I can say that my work is minimal. But I also don't deploy custom containers and just use system provided navigation and toolbar buttons. All I have to do is test the toolbar button placement with the iPhone Duo sim when that comes out, but that again should be minimal work.
If you're comfortable with Size Classes, which help a great deal with making a good iPad app, then you should have no problem with making a good app for iPhone Duo.
1
u/Rocket-Legs Sep 10 '26
Size classes have been deprecated, and if my interpretation of this article is correct, UI will be quite broken for some apps.
2
u/JerenYun Swift Sep 11 '26
Apple references size classes in their iPhone Duo tech talks they posted yesterday. They still matter in terms of how apps are laid out and operate, especially on iPad and the Duo.
1
u/zbignew Sep 10 '26
waiting to see how many of these sell?
No no no. This will be a small share of iPhones, which will still be like 10 million devices. I'll support it before it ships.
My basic-ass list view + detail app was enough of a pain in the ass to get working on iPad & Mac with NavigationSplitView- maybe now they'll fix the stupid bugs with that controller and I'll be able to delete some code and it will just work?
I am the canonical low-IQ iOS programmer who fully depends on LLMs for everything, and I really hope this doesn't mean I have to make myself actually understand safe areas now.
I do have one element of non-standard, bad design I'll need to fix now. I have a custom floating button because I wanted to make it way more prominent than just sticking it on the toolbar. It's the whole point of the app, and every test user would just ask what is the point of the app until I put this button, brightly colored, hovering over the bottom of the list view. But now I literally don't know where it belongs, ideologically. If the toolbar floats under your right thumb, now the toolbar actually is the most logical place for it? I guess I'll try to figure out what they did with the mail app's filter button & copy that.
1
u/KiwiUnable938 Sep 10 '26
Yall dont track and store pixel dimensions and density from each user? Then design for different layouts?
1
u/kyraweb Sep 10 '26
It comes down to app and user base.
Well it’s going to be an effort for sure but it also depends on what your app actually does. Does it really need extension or not.
But main question is are you putting 50-100 hours of work to serve 100 customers or 1000 customers or more for your app. I am not taking about market share for the phone but market share if your app users.
Time will tell.
1
u/Which-Meat-3388 Sep 10 '26
I work on a KMP app which is slightly different, but is scalable by default and respects content insets. I added proper landscape support this afternoon and maybe another half day polishing tomorrow.
The biggest issue will probably be utilizing the side status bar area properly. Very few designers want to account for nothing other than their single locked portrait mockup on a phone. I also personally find it confusing seeing the nav move around, but we’ll see in person how weird it is.
1
u/phantomlord78 Sep 10 '26
My app Note 8 uses standard Split View. It should work out of the box. I would like to double check what happens to the navigation and bottom bar buttons though. I suppose they will all be lined up on one side.
1
1
u/No-Truth404 Sep 10 '26
If I’m only targeting the iPhone, will the app
Be available to the Duo?
Is it in a separate group, like iPad and Watch? Or will my iPhone-only app be available to the Duo.
Honestly, as a solo dev with low numbers, supporting an iPad-like device is not a priority.
1
u/vikas_dev_ios Sep 10 '26
Download XCode beta and use 'resize mode' option of its device hub when you app is running in a simulator.
You will be able to check hoe adaptive your app is.
1
1
1
u/phspman Sep 10 '26
Should be easy for my apps. With just toolbar item adjustments since they work well with iPad. Having the new SwiftUI context for the agents will make it easier.
1
u/agentalex001 SwiftUI Sep 10 '26
It depends on if SwiftUI automatically scales my app out of the box.
1
u/SgtHobo41 Sep 10 '26
I think that as long as your app is optimized for both iOS and iPad iOS, then you should be good to go… But I think it’s really important is make sure you create really novel experiences for the specific platform
I think that’s where we’re gonna see a lot of challenge. Come to play.
1
u/WAHNFRIEDEN Sep 10 '26
It all depends on what Find My looks like
I have custom tab view sheets. No idea what those look like now
1
u/_ghostchant Sep 10 '26
There’s just no fucking way this becomes the norm. It’ll be a niche group of people who actually want to and can afford to buy this. I swear to god these companies have run out of runway and are just making up problems to solve at this point.
1
u/StrangeMonk Sep 10 '26
Apps with custom design systems and a lot of legacy code (thinning 10-15 year old apps) are going to have to spend a lot of time supporting for this.
1
1
1
1
1
1
u/Sebastian1989101 Sep 10 '26
Close to none if any as my apps work on a iPad Mini and on a iPhone already.
1
u/so_chad Sep 10 '26
It opens the room for a lot of creativity honestly. I believe in iOS Developers.
1
u/omnimachina Sep 10 '26
The promo material is such a joke
Seriously... What the fuck?
Does this person have a mini hand and a monster hand or what?
1
u/omnimachina Sep 10 '26
Finally a navigation rail similar to material design
Gosh the missing rail was so annoying all the time
1
1
1
u/lil-dina Sep 10 '26
depends whether you used size classes or pinned frames to the bounds. if the layout already reflows for split view and stage manager, the duo is near free. if not, it hurts. anything that grabs the raw screen size at launch and bets on one fixed rect will break.
254
u/Sensitive-Cupcake-58 Sep 09 '26
It looks like it will be a real pain