upvote
But will you gain anything by building for it? Will you see noticeably more users or people choosing another alternative because you didn't specifically building the app for Duo? At least if it doesn't outright break.
reply
I would get a little bit of joy if a duo user noticed the effort I put into making my app work well on their device. Why put effort into anything? Your take is bordering dangerously on cynicism. :)
reply
No, it's based on pragmatism. Every feature is a cost/benefit tradeoff. You didn't answer the question: would it be worth it?
reply
> But will you gain anything by building for it?

We're not talking about 0/1 here. There's making sure the app works and looks ok on the Duo and then there's building out Duo specific features. The works/looks ok is generally pretty easy with new devices. Just build with the new SDK and fix places where the app wasn't doing something likely already suggested by Apple. A big one will be safe areas which people often ignored except on the top and bottom.

reply
As a user, this attitude makes me sad.

As a professional programmer, it at least gratifies me to know this is the attitude I'm competing against.

reply
Thanks for the backhanded compliment, very mature..

I'm not an iOS developer, never made an app at all, I asked because I'm curious. What is it really to gain?

reply
You could say this about every QoL feature though. That’s not a reason to not do it though, it adds up and at some point other apps that do bother to make their apps as good as possible will become more popular than yours.
reply
Can two people use opposite sides while in tent mode? Because that makes for some fun in-person games.
reply
Apparently the camera has to be active to render on both displays
reply
Duo users also likely have disposable income to spend on in app purchases, maybe click on ads to purchase things, and other monetization. So I do think it's worth building for it.
reply
But will you gain anything by building for it?

Nothing ventured, nothing gained.

Will you see noticeably more users or people choosing another alternative because you didn't specifically building the app for Duo?

I haven't done iOS development in a long time, but my understanding is that if your iPhone app is designed well and uses all of Apple's recommended methods, adjusting for different screen sizes and orientations is fairly easy.

If you decided to go cheap/easy/dumb from the outset, then you made your bed, and now you get to lie in it.

reply
It is exotic, and bring only a little to the table for a stiff price increase.
reply
Not really. It's an iPad + iPhone. That's hardly exotic. Both of those product categories sell very well. People who own an iPad mini and an iPhone have every reason to consider this for the merged cost.
reply
Exactly. Maybe not v1, but the Duo will likely lead me to not buy another iPad.
reply
I use an iPad Mini every day (I’m on it, right now). I also have an iPad Pro, that I never use.

It’s likely that I will end up getting one of these, eventually.

I suspect all my apps will run OK on this. I have been designing for flexible screen dimensions since Day One (2012). It was a habit I already had, from MacOS development.

I am interested in seeing if I can leverage running on inside and outside screens. That might be interesting (but I don’t know if that’s possible. They may switch off the outer screen, when the device is open).

I’ll bet that Apple may ship an Apple Pen Mini, for these.

reply