iPhone Duo
721–730 of 1001 posts
Re: iPhone Duo
#722The one downside of my iPhone 13 mini is the rare case where I do need more screen.
I couldn't spend $2000 on a phone, but I don't mind the direction.
Re: iPhone Duo
#723As a recent Android foldable phone owner (Google Pixel), I'm excited that the Duo will get developers to actually design apps for foldables. Right now, some apps don't work at all and others are just stretched. I feel a better use of the screen space is around the corner for both Android foldable and Duo users.
I don't want to be pessimistic, but I can see a single app now showing two different feeds to doomscroll.
Re: iPhone Duo
#724I’m not always in the best areas so this def comes up for me personally
Outside of that I think I’d give this a shot
Re: iPhone Duo
#725The hard corners when its folded is a huge design breaker. The whole thing is THICK when folded. Jobs only added the bezel because it competed with the cases wrapped on phones. I don't see how any case will work on this behemoth.
I've seen what happens to the fold crease after a year, its a bit noticeable. It will degrade the prestigious quality of the brand.
Lastly, this copies all other fold phones. I'm surprised is all.
Re: iPhone Duo
#726Re: iPhone Duo
#727Re: iPhone Duo
#728These threads are often amusing with people obliviously asking: why doesn't Apple make exactly what I want? And then stating with certainty how well their custom requirements would sell. I'll probably wait and see how this phone does over the next few years. If it is still highly regarded by version 3 then I could imagine making the switch to a folding phone. For now I will remain conservative since my phone is such…
100%. It was so funny to see how for years, everyone on HN was harping on about how well a smaller iPhone would sell. Then Apple finally released the iPhone mini and nobody was buying it, so they had to kill it after a couple of iterations. Basically, try to do the opposite of what HN is saying and you might just create a successful product.
And by "nobody", you mean "actually a lot of people, just not as many as the bigger model". It's ok to have a model that meets a less common, but still extant, need in the market. If everyone followed Apple's logic on this, people with very small or very large bodies would have to go naked because companies would go "that size doesn't sell as much, we have to kill it" rather than (as actually happens) charging more per unit to make up for the overhead of lower volumes of sales.
Re: iPhone Duo
#729As a recent Android foldable phone owner (Google Pixel), I'm excited that the Duo will get developers to actually design apps for foldables. Right now, some apps don't work at all and others are just stretched. I feel a better use of the screen space is around the corner for both Android foldable and Duo users.
Instead, they just hand you some poorly documented loose parts in a box and tell you, “good luck” and you’re on your own to fill the gaps. Compose is a little better about giving the tools you need than the preceding Android Framework, but it’s still much more “assembly required” and “batteries not included” than the UIKit+SwiftUI world is.
Many iOS apps built using system components will behave 90%+ correctly on the Duo by just compiling against the iOS 27.1 SDK because there are well supported methods of doing things that Apple can leverage to reduce dev work. In contrast, on Android there's 10 ways of doing anything none of which get full-throated support (on top of all the other ways devs invent), and so any time it gains support for a new form factor almost nothing is automatic and it all falls on the devs’ shoulders.