I for one hope they don't go back to the curve (and I don't think they will). Why... well when you lay the 3G or 3GS on a flat surface, like say a desk, and then you go to press the home button, the phone tips up like a flippin' rocking horse! Very annoying.
I've never found the iPhone 4 uncomfortable to hold either.
To see where their current design direction is going, look at the iPad2, they got rid of the curve on that too. So if they do change the back, my guess would be they would round off the edges but keep the centre flat.
Sure, but how ugly would that look like? Developers have no information yet that they must create a new version for a phone with more pixels (except maybe a handfull of high-profile ones who can be trusted to keep mum). It will take months for even just the most used 10% of all apps to be converted. Do you really think Apple will want people to walk around with new iPhones where almost all of their apps run with a black border?I don't see a big problem with increasing the resolution of the display along with its physical size. If the pixel density remains the same, apps which haven't yet been updated could simply run within the same area of the current iPhone screen.
And iOS never had provisions to just add more 'whitespace' when the display size increases (like Android had, taken to an extreme by running 2.2 on a 7" display). Without adding that to iOS, Apple will not add a slightly different size.Apple has had many opportunities to increase the size of the iPhone and yet they have never done so.
The simplest explanation is that Steve Jobs likes the iPhone's size. We know that his aesthetic favors small, simple, elegant, and thin. Steve doesn't supersize.
I don't want to say that there is no case for a larger iPhone, I just don't understand why Apple would introduce it without giving developers some lead time to adjust for it. Yes, they could have some secret code in iOS 5 that automatically adds whitespace (and makes incremental content like lists, images, maps just display more) but a lot of apps would look somewhat bloated with that approach and a lot of developers would prefer to adjust their apps to the new physical size.I really don't see Apple going below 4.0 inches.
The iPhone 5 will be ridiculously awesome.
- thinner than any phone in existence
- Resolution will be at minimum 1280 x 720, if not higher.
Looks nasty, it'd be super unwieldy in a dock, with such a heavy top.
if this new phone gets thinner at one end i'll be gutted. :-(
Surely Apple wouldn't make such a design error.....surely!
Sure, that is the easiest (some would call it the laziest) option. But as a developer, your touch targets just increased in physical size, do you adjust that again, to do add another button in a row of buttons because if a 2x2 mm touch target was large enough on the existing iPhones, you can add another one of those.why add pixels ? Keep the same number of pixels, make the screen larger.
Yes, keeping a consistent message ('speaking with one voice') is part of Apple's overall concept.why is 300 the magic number??? because apple said so last year?
Sure, that is the easiest (some would call it the laziest) option. But as a developer, your touch targets just increased in physical size, do you adjust that again, to do add another button in a row of buttons because if a 2x2 mm touch target was large enough on the existing iPhones, you can add another one of those.
Yes, keeping a consistent message ('speaking with one voice') is part of Apple's overall concept.
Why is it a "design error"?
Technically yes, but in practice the physical and pixel dimensions have been 100% locked, every iOS developer knows exactly what the physical dimensions of his touch targets are. And in the end the dimensions of a finger are defined in millimeter not pixels, developers design with fingers in mind but enter the values in pixels but so far the question whether to enter a value in millimeters or pixels was a moot one as they two were locked like a fixed exchange rate.Hum... have you ever developped software for Cocoa Touch ? You don't calculate "touch targets" with physical dimensions.
As I said, of course this works but developers still have to ask themselves whether they want to develop a new version of their app that has smaller touch targets in pixels (but the same in millimeters) as this might allow them to fit an extra control on the screen.Users just now have bigger surfaces to touch that will send a touch event to your view.
Well, maybe by your standards but in comparison with almost all other companies they are by far the most consistent one. Let's just look at all the messages HP has been sending out on WebOS over the last year, there have at a dozen of people at HP making statements on it, and the public message has kept changing back and forth (remember the CEO, Mark Hurd, interview where he said, they did not buy Palm to be in the smartphone business only for a press release a few days later saying that he actually did not mean what he was saying).It is ? Since when ? "People don't read books" iBook. "People don't want to watch video on an iPod screen", iPod video.
Keeping a consistent message is as far of Apple's overall concept as you can get.
Technically yes, but in practice the physical and pixel dimensions have been 100% locked, every iOS developer knows exactly what the physical dimensions of his touch targets are. And in the end the dimensions of a finger are defined in millimeter not pixels, developers design with fingers in mind but enter the values in pixels but so far the question whether to enter a value in millimeters or pixels was a moot one as they two were locked like a fixed exchange rate.
As I said, of course this works but developers still have to ask themselves whether they want to develop a new version of their app that has smaller touch targets in pixels (but the same in millimeters) as this might allow them to fit an extra control on the screen.
Well, maybe by your standards but in comparison with almost all other companies they are by far the most consistent one. Let's just look at all the messages HP has been sending out on WebOS over the last year, there have at a dozen of people at HP making statements on it, and the public message has kept changing back and forth (remember the CEO, Mark Hurd, interview where he said, they did not buy Palm to be in the smartphone business only for a press release a few days later saying that he actually did not mean what he was saying).
I'm just ready for Apple to announce it! I've been using a BB Curve for the past three years, The Verizon iphone 4 was the first iphone I could have bought and I decided to wait because I knew of the yearly june updates to the iphone lineup. Oct 7 or 14 can not get here fast enough.
That I find unbelievable. Do you mean if I want to make a 'button' that stretches the whole width of the screen, it would have same 'bounding box' as a button that stretches only half of the screen width?Even if a developer wanted to make smaller "bounding" boxes, there is no information in the OS to do so.
Well, if you design both for iPhone 4 and 3GS, you already have to create the same button with a different set of pixels (and yet another set of pixels for any iPad version).They can't fit extra anything on the screen aside from making them take less pixels, which would be a huge pain.
Sure, in a nice simple binary, black and white world there is consistent and inconsistent. And since Apple is not fully consistent is just as bad as everybody else in this simple binary world view.Apple is as inconsistent with their message as any other corporation.
This is exactly correct! This site is in fact called "Macrumors" , not Macdefinitiveanswers.
It still not going to be 4g so with that logic, just get an iPhone 4 now.
That I find unbelievable. Do you mean if I want to make a 'button' that stretches the whole width of the screen, it would have same 'bounding box' as a button that stretches only half of the screen width?
Well, if you design both for iPhone 4 and 3GS, you already have to create the same button with a different set of pixels (and yet another set of pixels for any iPad version).
A lot of apps have a row of buttons at the bottom (that might be a built-in iOS control but nothing stops a developer from creating their own buttons). If you make the screen physically wider, you can possibly fit another button in there.
Sure, in a nice simple binary, black and white world there is consistent and inconsistent. And since Apple is not fully consistent is just as bad as everybody else in this simple binary world view.
But try to count how many individuals at Apple give interviews and how many at HP do? How many Apple employees blog about their company and how many HP employees do?
Obviously, again, your grasp on the concept is frail.
Interface Builder provides scaling automatically. You just define a button to fit inside a view, no matter what the view's size is in pixels. This is the same functionality in OS X and iOS. View sizes and objects sizes can be defined as percentages of one another.
I had exactly 0 code and parameters to change with the "retina" display for my app to just work. The view is now reporting a 960x640 size on the iPhone 4 simulator, but all the code just works and the UI is all properly positionned.
3.5" screen or 4" screen, if both are 960x640, there is absolutely nothing to change UI wise or Input wise for developers. It just works. Developers don't make different UIs for the MBA's 13" 1440x900 screen and the MBP's 15" 1440x900 screen...