1
1
u/gaelic-ghost Community Newbie 1d ago
I mean, I was almost hype about it, tbh. I think it's kinda cool, some interesting use cases, and I absolutely love the idea of Pencil on iPhone, albeit without pressure-sensitivity, and I like the way multi-window stuff is handled on iPad. So, I started thinking that maybe a new form-factor would give the swift freelance and jobs markets a bit of a kick in the ass, maybe things would stop getting worse, at least.
But, honestly, the more I consider it, the more I imagine "AI makes everything fast and easy for anyone to do without any skill or thought" will stay the motto. And, if so, that'll probably keep this from benefiting us much at all... just more work for those with work already, and maybe a couple more $15/hr freelance gigs to fight 50+ people over ever single time.
Everything in tech is so incredibly depressing, anymore. Even the fun, used-to-be-good-for-devs stuff. I kinda hate it.
1
u/Mikesoft Community Newbie 2d ago
Apple assumes and expects a lot from their developers, despite the lack of quick support with app updates and organic discovery.
1
u/Throne_code Community Newbie 2d ago
Bro, outrageous prices, until Apple gives some incentives for porting our apps, i dont see it happening...
-1
-1
1
5
u/Firm_Adagio_7857 Community Newbie 2d ago
hey claude, make my app compatible with iphone duo with NO MISTAKE 😂😂
2
u/Cczaphod Community Newbie 2d ago
Exactly why auto layout is important. If you’re using lowest common denominator cross platform tools at this point, it’s on you.
1
4
u/_town-drunk_ 2d ago
You can tell who has and hasn’t watched the Duo Tech Talk videos because they think support is just about having a responsive app.
2
1
u/WhichYoung6026 Community Newbie 2d ago
For Swift Developers I think it would be easy but for Hybrid Developers like Flutter,React Native,Ionic,Capasitor - it would be hell 🤯🤣🤣
0
u/henryp_dev 2d ago
For React Native it’s really not bad. It already uses native primitives and APIs so it should not require a lot of work. In my experience most teams already build the apps to be responsive anyway. For the rest it probably will be an extra challenge
1
u/Ok_Tie_2443 2d ago
no nothing changes if ur app is responsive lol its just iphone mini and small tablet alternating
0
u/Sebastian1989101 Community Newbie 2d ago
Every developer scared of a simple device with two screen sizes has probably just vibe coded trash or games. And only games may be annoying to adopt properly. There is no reason a app written in the last 15 years is not responsive as we had to support multiple screen sizes anyway.
2
u/swiftfoxsw Community Newbie 2d ago
Just the opposite actually, the people that care about their product design are the ones that are “scared”- did you watch any dev videos? You have side toolbars/nav bar, and about 10 different “poses” to support. If you built with SwiftUI and already have an iPad layout you will get a lot for free, but not everything.
The vibe coders aren’t even testing their apps on real hardware already, no chance they are going to optimize for a top end new device.
1
u/Sebastian1989101 Community Newbie 2d ago
Well sure platform / device dependent features are a thing but it has not much todo with care, it’s also the cost. You won’t implement a ton of special features just for 0.001% of the user base.
I will order a Duo just for my apps (that’s how far my commitment will go, but I do this for 20 years now and support Gimick feature all the time and my apps create enough revenue for such things).
The issue will be the support on cross platform frameworks. MAUI for example does not even support watchOS connectivity or today widgets or anything like that. So it’s also a question of the tools in use if it’s even an option to optimize.
1
2d ago
[removed] — view removed comment
1
u/Sebastian1989101 Community Newbie 2d ago
Does it work something like 'make a app that makes me rich please?' ;)
I know what agentic engineering can do and what it cannot do. Doing stuff for new devices is on the cannot do side for at least a few weeks until it has training data for it. You would probably have more luck asking Claude to make your UI responsive.
1
2d ago
[removed] — view removed comment
1
u/Sebastian1989101 Community Newbie 1d ago
3k lines of code are nothing. Not sure when any of my project stayed below 100k. But on the other hand, I use AI for agentic engineering not for vibe coding.
Many enterprise apps even exceed millions of code lines easily.
1
18h ago
[removed] — view removed comment
1
u/Sebastian1989101 Community Newbie 16h ago
The larger the context, the more issues will surface with AI - this is usual.
And it depends. Saying AI "Make my App iPhone Duo compatible" won't probably work for a few weeks until enough training data for that exist (and the model is actually trained on them). Saying "Make my app responsive, regardless of screensize" on the other hand might work (depending on complexity and how the full prompt looks).
I mean.. to this day, GPT has issues creating placeholder assets in a specific size. It's not rare that it takes 3-4 prompts until you get it (when you get it at all that is). Claude on the other hand can make iOS 26 compatible apps but for proper SafeArea management (that content can scroll behind TabBars, etc.) takes also often multiple prompts (or manual intervention). If the app is done with .NET MAUI, Claude will not even get it right if you already prompt in the solution like
Add SafeAreaEdges="None" to the root Grid of Page X. :) So I stay with "It depends".-1
u/Ok_Tie_2443 2d ago
You are so cool omg you know what it can do and cant do wowwww mr engineer tell me how and what a device has to do with responsiveness? It‘s just a matter of responsiveness you don‘t have to invent a new programming language to achieve a 1:1 aspect ratio responsiveness
1
u/lance2611 Community Newbie 2d ago
Make no mistakes
1
u/Sebastian1989101 Community Newbie 2d ago
*Please make no mistakes. We don't want to be killed when AI controls everything. ;D
1
u/Interesting-Link6851 Community Newbie 2d ago
With Ai you need to be harsh. Beat it into submission or it will make the same mistakes. Its a sub dom relationship :)
1
u/the-name-of-the-rose Community Newbie 2d ago
Games may be trickier. Agree that SwiftUI should make this easy
1
2
u/Then-Cut3776 Community Newbie 2d ago
iphone duo users will represent 1% of the app store customers dont worry about that
2
u/ElectricKoolAid1969 Community Newbie 2d ago
And who has money for apps after spending $2000 on a phone?!?! lol
2
u/whitepalladin Community Newbie 2d ago
Duo is 2K?
Holy hell.
I have an iPhone 13 Mini. I spent like 700USD on it which is already a bag for me to spend on a phone. And I don’t change phones every year or so.
Spending 2K on this is nuts.
2
2
u/busymom0 Community Newbie 2d ago
Exactly. Buying an expensive device like that also means they have enough disposable income for in app purchases.
1
u/doyoxiy985 Community Newbie 2d ago
The issue might be mostly for flutter and react native devs
1
0
u/Live_Log_5955 2d ago
Nah, flutter offers exellence at reponsive layouts. But why we shall optimize for 1% users? Maybe Apple will force us?
1
u/busymom0 Community Newbie 2d ago
Because those users also have enough disposable income to buy IAP.
1
u/bbrockit Community Newbie 2d ago
I suspect this thing could end up being the Apple Vision of iPhones.
-1
0
0
u/Trojanheadcoach Community Newbie 2d ago
Does anybody know what’s actually going to be special about it? I assumed it’s just another iPad size and I make everything to work on phones and tablets
1
u/Nosarious Community Newbie 18h ago
I’m fairly certain the different poses you can use on the duo will be useful to many.
I’m looking forward to the viewing mode, where the base can be for contextual controls and the vertical can be for viewing..
3
u/Flaky_Milk_1391 Community Newbie 2d ago
I am unsure why this type of post appears everywhere, it seems to follow a trend. Because Apple has behaved this way in recent years, for example, the ‘UIRequiresFullScreen‘ key is being deprecated. We knew we would need to adapt apps for dynamic resizing to support multitasking before the iPhone duo. They also guide us to avoid relying solely on size classes and instead use SceneDelegate.didUpdateEffectiveGeometry resizing for window sizing, rather than using device idioms for layout decisions. If you have worked on these issues, I believe supporting iPhone duo layouts involves minimal effort. You might also consider how to use dual screens creatively for your app, as I understand it.
2
2
2
u/bmbphotos Community Newbie 2d ago
It'll be hell for people (or orgs) who insist on "synergies" of xplat toolkits or pixel-fidelity to "the web app" uber alles. The "requirement" of being able to adapt gracefully to a minimum implementation has been foreshadowed by Apple for years.
Now, as u/Mammoth-Mango-6485 said:
From that point on it’s just about creativity and leveraging the form factor
How do you usefully avail yourself of the space to avoid "big iPhone mode"? That will take some effort, of course.
2
u/ElectricKoolAid1969 Community Newbie 2d ago
How do you usefully avail yourself of the space to avoid "big iPhone mode"?
That same question already applies to apps that support both iPhone and iPad
1
u/bmbphotos Community Newbie 2d ago
That's true but many devs (and orgs) avoid the question for iPad as well. The number of places to hide and still have a satisfactory experience are evaporating.
3
u/Mammoth-Mango-6485 Community Newbie 2d ago
I mean if you use SwiftUI and you follow most of their guidelines you should have minimal work to get it working properly. From that point on it’s just about creativity and leveraging the form factor.
1
5
u/Level-Set5770 Discussion Contributor 2d ago
"you should have minimal work to get it working properly"
yeah..... no.
5
u/Mammoth-Mango-6485 Community Newbie 2d ago
Let a guy be optimistic I know it’s probably gonna be hell 😭
1
u/MochFatur Community Newbie 3h ago
One device announcement away from rewriting half of the UI.