or Connect
New Posts  All Forums:

Posts by VL-Tone

It's not that simple because content providers see the TV screen as something completely different. It's a legacy market they're trying to protect. They're willing to put apps on devices like tablets and smartphones because it's "not TV". The ability to stream those to the Apple TV trough Airplay is a hole that they would've like to plug, but since its too late they still add the feature in their apps to stay competitive with other apps. Take a look at ChromeCast, unlike...
I see phablets as something between phones and tablets (hence the name). So to me 3:2 is ok, especially if it opens the possibility to split-screen apps on the iPad and help manufacturing by using the good half an iPad mini screen when the other half has a defect. But yeah, perhaps you're right too! It's just some wild speculation from my part.
 Having resolutions that are multiple of existing ones was useful for devices that have the same screen size, because UI elements could stay exactly at the same place and with the same size on screen (and the iOS made the 2x coordinate conversion automatically). Avoiding fractional multiplication of screen coordinates is not a necessity with a screen size changes since UI elements need to be moved around and layouts have to be redone anyway. The iPad doesn't have...
Your whole point was based on the idea that it would require "FAR more work" to go from the 16:9 app to a 3:2 phablet because the aspect ratio was different. But you forgot (and I forgot too) that every single iPhone app has to support 3:2 screens anyway so your point is moot.
I was mainly thinking about "small" mobile phones like the 4" iPhone. On a 5"+ device (which I don't really consider the same device category) it might make more sense for some.
 What will complicate things for developers is the significant screen size difference requiring rethinking the layout, not the aspect ratio change. The lazy developers I was talking about would simply blow up their UI as a native phablet app and never work on optimizing it. I wasn't talking about those who would use this as a temporary solution. But anyway developers will have to support the 3:2 screen of the iPhone 3/4 for a while now, so this discussion is moot.
 Well obviously those apps would be "fat binaries" just like iPhone+iPad apps that exist on the App Store.
Why this "throw-away" account reference? I'm simply discussing some theory/speculation of my own. Not sure why I deserve that remark.
Why would it be? Apps layouts have to be completely redone anyway, you can't just scale up coordinates. This is a touch screen device, touch target sizes have to be optimized. If this prevents lazy devs from simply blowing up their apps  (which would be easier but stupid) then I'm all for it. 
 I never said anything about split-screen multi-tasking on a mobile phone. I also think it's absurd. I was talking about running two apps side by side on an iPad. Half an iPad mini screen could be used in an hypothetical 5.7" Apple phablet, and optimizing apps for this size would also mean optimizing for split screen on full size iPads. I understand what you're saying about relying on dynamic resizing to make tablet apps from phone apps, something Apple has tried to avoid,...
New Posts  All Forums: