Thoughts on iPhone 5 and its larger display
I guess the following thoughts may be interesting to others in our community...
I've been looking at our iOS App - as I need to send out a new build anyway (to appease the British in America, and their pesky Celcius vs Miles issue), I had a look at adding support for the new iPhone 5 with its bigger display.
The iPhone 4S has a screen of 960 x 640, and the iPhone 5 has a screen of 1136 x 640. An extra 176 pixels in the vertical orientation.
1136 vs 960 is a little over 18% taller. Not much difference, right?
If the developer does nothing to his App, it gets letter boxed. Two black borders of 88x640 pixels are added to the top and bottom, and the application virtual size of 960 x 640 is maintained - even though it is running on a 1136x640 display.
It turns out by adding one file to the build project (a specially named splash screen at the 1136x640 resolution), you tell the iOS not to letterbox you, but give you the full screen. Doing that I expected to get a little 18% layout problem.
Not so fast.
If you look at the screenshot (from an iPhone 4S) below, you can see the status bar, top bar, and bottom tab bar are all fixed in size (whether it is running on a 4S or 5). It is the big blue bit in the middle that gets resized.
The status bar is 40 pixels in height, the top bar 128 pixels and the bottom tab bar 98 pixels. That leaves 960-(40+128+98) = 694 pixels (the height of that blue background bit) to show the real application content.
On an iPhone 5, the status bar, top bar and bottom tab bar all remain the same. That leaves 1136-(40+128+98) = 870 pixels to show the real application content.
870 vs 694 is a little over 25% more usable screen real estate.
This explains a lot to me about what is so important about the iPhone 5 being just that little big taller. 25% more usable screen real estate for an App like ours.
I've already re-worked the App auto-layout to at least look on the iPhone 5. Things like the map, tables and lists just automatically work and take advantage of the extra room. But, fixed screens like the Battery and Car will take some work to think about and take advantage of that new usable screen real estate.
Regards, Mark.
Do we have any new or "extra" info that would be of interest that the screen has been too crowded for until now? notably the top view screen maybe we can redistribute the info a little on that screen……? I'll try to take a look at that over the weekend
best
felix b.
On Sep 19, 2012, at 2:27 PM, Mark Webb-Johnson <mark@webb-johnson.net> wrote:
I guess the following thoughts may be interesting to others in our community...
I've been looking at our iOS App - as I need to send out a new build anyway (to appease the British in America, and their pesky Celcius vs Miles issue), I had a look at adding support for the new iPhone 5 with its bigger display.
The iPhone 4S has a screen of 960 x 640, and the iPhone 5 has a screen of 1136 x 640. An extra 176 pixels in the vertical orientation.
1136 vs 960 is a little over 18% taller. Not much difference, right?
If the developer does nothing to his App, it gets letter boxed. Two black borders of 88x640 pixels are added to the top and bottom, and the application virtual size of 960 x 640 is maintained - even though it is running on a 1136x640 display.
It turns out by adding one file to the build project (a specially named splash screen at the 1136x640 resolution), you tell the iOS not to letterbox you, but give you the full screen. Doing that I expected to get a little 18% layout problem.
Not so fast.
If you look at the screenshot (from an iPhone 4S) below, you can see the status bar, top bar, and bottom tab bar are all fixed in size (whether it is running on a 4S or 5). It is the big blue bit in the middle that gets resized.
The status bar is 40 pixels in height, the top bar 128 pixels and the bottom tab bar 98 pixels. That leaves 960-(40+128+98) = 694 pixels (the height of that blue background bit) to show the real application content.
On an iPhone 5, the status bar, top bar and bottom tab bar all remain the same. That leaves 1136-(40+128+98) = 870 pixels to show the real application content.
870 vs 694 is a little over 25% more usable screen real estate.
This explains a lot to me about what is so important about the iPhone 5 being just that little big taller. 25% more usable screen real estate for an App like ours.
I've already re-worked the App auto-layout to at least look on the iPhone 5. Things like the map, tables and lists just automatically work and take advantage of the extra room. But, fixed screens like the Battery and Car will take some work to think about and take advantage of that new usable screen real estate.
Regards, Mark.
<photo.PNG>
OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
Felix,
I was thinking the same. It is quite crowded, and it may just be better to make things a little bigger and more spaced out on the 5.
Regards, Mark.
On 19 Sep, 2012, at 2:37 PM, felix bonnier wrote:
Do we have any new or "extra" info that would be of interest that the screen has been too crowded for until now? notably the top view screen maybe we can redistribute the info a little on that screen……? I'll try to take a look at that over the weekend
best
felix b.
On Sep 19, 2012, at 2:27 PM, Mark Webb-Johnson <mark@webb-johnson.net> wrote:
I guess the following thoughts may be interesting to others in our community...
I've been looking at our iOS App - as I need to send out a new build anyway (to appease the British in America, and their pesky Celcius vs Miles issue), I had a look at adding support for the new iPhone 5 with its bigger display.
The iPhone 4S has a screen of 960 x 640, and the iPhone 5 has a screen of 1136 x 640. An extra 176 pixels in the vertical orientation.
1136 vs 960 is a little over 18% taller. Not much difference, right?
If the developer does nothing to his App, it gets letter boxed. Two black borders of 88x640 pixels are added to the top and bottom, and the application virtual size of 960 x 640 is maintained - even though it is running on a 1136x640 display.
It turns out by adding one file to the build project (a specially named splash screen at the 1136x640 resolution), you tell the iOS not to letterbox you, but give you the full screen. Doing that I expected to get a little 18% layout problem.
Not so fast.
If you look at the screenshot (from an iPhone 4S) below, you can see the status bar, top bar, and bottom tab bar are all fixed in size (whether it is running on a 4S or 5). It is the big blue bit in the middle that gets resized.
The status bar is 40 pixels in height, the top bar 128 pixels and the bottom tab bar 98 pixels. That leaves 960-(40+128+98) = 694 pixels (the height of that blue background bit) to show the real application content.
On an iPhone 5, the status bar, top bar and bottom tab bar all remain the same. That leaves 1136-(40+128+98) = 870 pixels to show the real application content.
870 vs 694 is a little over 25% more usable screen real estate.
This explains a lot to me about what is so important about the iPhone 5 being just that little big taller. 25% more usable screen real estate for an App like ours.
I've already re-worked the App auto-layout to at least look on the iPhone 5. Things like the map, tables and lists just automatically work and take advantage of the extra room. But, fixed screens like the Battery and Car will take some work to think about and take advantage of that new usable screen real estate.
Regards, Mark.
<photo.PNG>
OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
the actual Volt and Ampere font size when car is charging could increase again a little bit. this very usefull information went a bit to small ( there are some OVMS owner close to or above 50:-))
Mit freundlichen Grüßen / Kind regards
Michael Eymann
Am 19.09.2012 um 08:40 schrieb Mark Webb-Johnson <mark@webb-johnson.net>:
Felix,
I was thinking the same. It is quite crowded, and it may just be better to make things a little bigger and more spaced out on the 5.
Regards, Mark.
On 19 Sep, 2012, at 2:37 PM, felix bonnier wrote:
Do we have any new or "extra" info that would be of interest that the screen has been too crowded for until now? notably the top view screen maybe we can redistribute the info a little on that screen……? I'll try to take a look at that over the weekend
best
felix b.
On Sep 19, 2012, at 2:27 PM, Mark Webb-Johnson <mark@webb-johnson.net> wrote:
I guess the following thoughts may be interesting to others in our community...
I've been looking at our iOS App - as I need to send out a new build anyway (to appease the British in America, and their pesky Celcius vs Miles issue), I had a look at adding support for the new iPhone 5 with its bigger display.
The iPhone 4S has a screen of 960 x 640, and the iPhone 5 has a screen of 1136 x 640. An extra 176 pixels in the vertical orientation.
1136 vs 960 is a little over 18% taller. Not much difference, right?
If the developer does nothing to his App, it gets letter boxed. Two black borders of 88x640 pixels are added to the top and bottom, and the application virtual size of 960 x 640 is maintained - even though it is running on a 1136x640 display.
It turns out by adding one file to the build project (a specially named splash screen at the 1136x640 resolution), you tell the iOS not to letterbox you, but give you the full screen. Doing that I expected to get a little 18% layout problem.
Not so fast.
If you look at the screenshot (from an iPhone 4S) below, you can see the status bar, top bar, and bottom tab bar are all fixed in size (whether it is running on a 4S or 5). It is the big blue bit in the middle that gets resized.
The status bar is 40 pixels in height, the top bar 128 pixels and the bottom tab bar 98 pixels. That leaves 960-(40+128+98) = 694 pixels (the height of that blue background bit) to show the real application content.
On an iPhone 5, the status bar, top bar and bottom tab bar all remain the same. That leaves 1136-(40+128+98) = 870 pixels to show the real application content.
870 vs 694 is a little over 25% more usable screen real estate.
This explains a lot to me about what is so important about the iPhone 5 being just that little big taller. 25% more usable screen real estate for an App like ours.
I've already re-worked the App auto-layout to at least look on the iPhone 5. Things like the map, tables and lists just automatically work and take advantage of the extra room. But, fixed screens like the Battery and Car will take some work to think about and take advantage of that new usable screen real estate.
Regards, Mark.
<photo.PNG>
OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
will be kept in mind this w-e!
best
/felix b.
Sent from somewhere in our beautiful universe.
On 19 Sep, 2012, at 17:01, "Michael J.A. Eymann" <Michael.Eymann@Networkz.de> wrote:
the actual Volt and Ampere font size when car is charging could increase again a little bit. this very usefull information went a bit to small ( there are some OVMS owner close to or above 50:-))
Mit freundlichen Grüßen / Kind regards
Michael Eymann
Am 19.09.2012 um 08:40 schrieb Mark Webb-Johnson <mark@webb-johnson.net>:
Felix,
I was thinking the same. It is quite crowded, and it may just be better to make things a little bigger and more spaced out on the 5.
Regards, Mark.
On 19 Sep, 2012, at 2:37 PM, felix bonnier wrote:
Do we have any new or "extra" info that would be of interest that the screen has been too crowded for until now? notably the top view screen maybe we can redistribute the info a little on that screen……? I'll try to take a look at that over the weekend
best
felix b.
On Sep 19, 2012, at 2:27 PM, Mark Webb-Johnson <mark@webb-johnson.net> wrote:
I guess the following thoughts may be interesting to others in our community...
I've been looking at our iOS App - as I need to send out a new build anyway (to appease the British in America, and their pesky Celcius vs Miles issue), I had a look at adding support for the new iPhone 5 with its bigger display.
The iPhone 4S has a screen of 960 x 640, and the iPhone 5 has a screen of 1136 x 640. An extra 176 pixels in the vertical orientation.
1136 vs 960 is a little over 18% taller. Not much difference, right?
If the developer does nothing to his App, it gets letter boxed. Two black borders of 88x640 pixels are added to the top and bottom, and the application virtual size of 960 x 640 is maintained - even though it is running on a 1136x640 display.
It turns out by adding one file to the build project (a specially named splash screen at the 1136x640 resolution), you tell the iOS not to letterbox you, but give you the full screen. Doing that I expected to get a little 18% layout problem.
Not so fast.
If you look at the screenshot (from an iPhone 4S) below, you can see the status bar, top bar, and bottom tab bar are all fixed in size (whether it is running on a 4S or 5). It is the big blue bit in the middle that gets resized.
The status bar is 40 pixels in height, the top bar 128 pixels and the bottom tab bar 98 pixels. That leaves 960-(40+128+98) = 694 pixels (the height of that blue background bit) to show the real application content.
On an iPhone 5, the status bar, top bar and bottom tab bar all remain the same. That leaves 1136-(40+128+98) = 870 pixels to show the real application content.
870 vs 694 is a little over 25% more usable screen real estate.
This explains a lot to me about what is so important about the iPhone 5 being just that little big taller. 25% more usable screen real estate for an App like ours.
I've already re-worked the App auto-layout to at least look on the iPhone 5. Things like the map, tables and lists just automatically work and take advantage of the extra room. But, fixed screens like the Battery and Car will take some work to think about and take advantage of that new usable screen real estate.
Regards, Mark.
<photo.PNG>
OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
Hi Mark,
I have been thinking about this during the weekend……… Right now, as far as I understand, we are running all the graphics on a FIXED position on the screen……. Could we not run everything RELATIVE positions instead…… So we do not need special graphics depending on which phone you have…….. So on the 5 that would automatically space everything out a little…… This does not mean that I do not have to redo the graphics, on the contrary, I really need to redo them but the way it is done would be different…….. What do you think??
I picked up my 5 in HK during the weekend and the current app looks fine so we are not really in a super rush but we should keep up with the Jonses……. So I would just like to vent, in what direction we want to go.
Have a good sunday night
best
felix b.
On Sep 19, 2012, at 2:40 PM, Mark Webb-Johnson <mark@webb-johnson.net> wrote:
Felix,
I was thinking the same. It is quite crowded, and it may just be better to make things a little bigger and more spaced out on the 5.
Regards, Mark.
On 19 Sep, 2012, at 2:37 PM, felix bonnier wrote:
Do we have any new or "extra" info that would be of interest that the screen has been too crowded for until now? notably the top view screen maybe we can redistribute the info a little on that screen……? I'll try to take a look at that over the weekend
best
felix b.
On Sep 19, 2012, at 2:27 PM, Mark Webb-Johnson <mark@webb-johnson.net> wrote:
I guess the following thoughts may be interesting to others in our community...
I've been looking at our iOS App - as I need to send out a new build anyway (to appease the British in America, and their pesky Celcius vs Miles issue), I had a look at adding support for the new iPhone 5 with its bigger display.
The iPhone 4S has a screen of 960 x 640, and the iPhone 5 has a screen of 1136 x 640. An extra 176 pixels in the vertical orientation.
1136 vs 960 is a little over 18% taller. Not much difference, right?
If the developer does nothing to his App, it gets letter boxed. Two black borders of 88x640 pixels are added to the top and bottom, and the application virtual size of 960 x 640 is maintained - even though it is running on a 1136x640 display.
It turns out by adding one file to the build project (a specially named splash screen at the 1136x640 resolution), you tell the iOS not to letterbox you, but give you the full screen. Doing that I expected to get a little 18% layout problem.
Not so fast.
If you look at the screenshot (from an iPhone 4S) below, you can see the status bar, top bar, and bottom tab bar are all fixed in size (whether it is running on a 4S or 5). It is the big blue bit in the middle that gets resized.
The status bar is 40 pixels in height, the top bar 128 pixels and the bottom tab bar 98 pixels. That leaves 960-(40+128+98) = 694 pixels (the height of that blue background bit) to show the real application content.
On an iPhone 5, the status bar, top bar and bottom tab bar all remain the same. That leaves 1136-(40+128+98) = 870 pixels to show the real application content.
870 vs 694 is a little over 25% more usable screen real estate.
This explains a lot to me about what is so important about the iPhone 5 being just that little big taller. 25% more usable screen real estate for an App like ours.
I've already re-worked the App auto-layout to at least look on the iPhone 5. Things like the map, tables and lists just automatically work and take advantage of the extra room. But, fixed screens like the Battery and Car will take some work to think about and take advantage of that new usable screen real estate.
Regards, Mark.
<photo.PNG>
OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
Felix,
The previous version (App store now) positioned everything relative to the top of the screen. It is letterboxed on iPhone 5.
The new version (submitted last week, and hopefully will appear on App store this week) positions the top stuff relative to the top of the screen, and the bottom stuff relative to the bottom of the screen. It runs full resolution on iPhone 5.
The 'relative position' stuff works well, but it appears you can only set the position relative to the top, bottom or sides. I'm still trying to find an automated way of setting it relative to other objects. In particular, to space things out, we need a 'centering' ability, or way of adjusting the spacing depending on resolution. At the moment, with iPhone 5, we just have a lot more space in the middle.
Regards, Mark.
On 23 Sep, 2012, at 11:15 PM, felix bonnier wrote:
Hi Mark,
I have been thinking about this during the weekend……… Right now, as far as I understand, we are running all the graphics on a FIXED position on the screen……. Could we not run everything RELATIVE positions instead…… So we do not need special graphics depending on which phone you have…….. So on the 5 that would automatically space everything out a little…… This does not mean that I do not have to redo the graphics, on the contrary, I really need to redo them but the way it is done would be different…….. What do you think??
I picked up my 5 in HK during the weekend and the current app looks fine so we are not really in a super rush but we should keep up with the Jonses……. So I would just like to vent, in what direction we want to go.
Have a good sunday night
best
felix b.
On Sep 19, 2012, at 2:40 PM, Mark Webb-Johnson <mark@webb-johnson.net> wrote:
Felix,
I was thinking the same. It is quite crowded, and it may just be better to make things a little bigger and more spaced out on the 5.
Regards, Mark.
On 19 Sep, 2012, at 2:37 PM, felix bonnier wrote:
Do we have any new or "extra" info that would be of interest that the screen has been too crowded for until now? notably the top view screen maybe we can redistribute the info a little on that screen……? I'll try to take a look at that over the weekend
best
felix b.
On Sep 19, 2012, at 2:27 PM, Mark Webb-Johnson <mark@webb-johnson.net> wrote:
I guess the following thoughts may be interesting to others in our community...
I've been looking at our iOS App - as I need to send out a new build anyway (to appease the British in America, and their pesky Celcius vs Miles issue), I had a look at adding support for the new iPhone 5 with its bigger display.
The iPhone 4S has a screen of 960 x 640, and the iPhone 5 has a screen of 1136 x 640. An extra 176 pixels in the vertical orientation.
1136 vs 960 is a little over 18% taller. Not much difference, right?
If the developer does nothing to his App, it gets letter boxed. Two black borders of 88x640 pixels are added to the top and bottom, and the application virtual size of 960 x 640 is maintained - even though it is running on a 1136x640 display.
It turns out by adding one file to the build project (a specially named splash screen at the 1136x640 resolution), you tell the iOS not to letterbox you, but give you the full screen. Doing that I expected to get a little 18% layout problem.
Not so fast.
If you look at the screenshot (from an iPhone 4S) below, you can see the status bar, top bar, and bottom tab bar are all fixed in size (whether it is running on a 4S or 5). It is the big blue bit in the middle that gets resized.
The status bar is 40 pixels in height, the top bar 128 pixels and the bottom tab bar 98 pixels. That leaves 960-(40+128+98) = 694 pixels (the height of that blue background bit) to show the real application content.
On an iPhone 5, the status bar, top bar and bottom tab bar all remain the same. That leaves 1136-(40+128+98) = 870 pixels to show the real application content.
870 vs 694 is a little over 25% more usable screen real estate.
This explains a lot to me about what is so important about the iPhone 5 being just that little big taller. 25% more usable screen real estate for an App like ours.
I've already re-worked the App auto-layout to at least look on the iPhone 5. Things like the map, tables and lists just automatically work and take advantage of the extra room. But, fixed screens like the Battery and Car will take some work to think about and take advantage of that new usable screen real estate.
Regards, Mark.
<photo.PNG>
OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
Ok mark,
So i'll try to work with the relationships that we know work, to begin with so at least we move ahead and if you find a way to be relative to the centre or an object then thats great
best
/fb
On Sep 24, 2012, at 9:09 AM, Mark Webb-Johnson <mark@webb-johnson.net> wrote:
Felix,
The previous version (App store now) positioned everything relative to the top of the screen. It is letterboxed on iPhone 5.
The new version (submitted last week, and hopefully will appear on App store this week) positions the top stuff relative to the top of the screen, and the bottom stuff relative to the bottom of the screen. It runs full resolution on iPhone 5.
The 'relative position' stuff works well, but it appears you can only set the position relative to the top, bottom or sides. I'm still trying to find an automated way of setting it relative to other objects. In particular, to space things out, we need a 'centering' ability, or way of adjusting the spacing depending on resolution. At the moment, with iPhone 5, we just have a lot more space in the middle.
Regards, Mark.
On 23 Sep, 2012, at 11:15 PM, felix bonnier wrote:
Hi Mark,
I have been thinking about this during the weekend……… Right now, as far as I understand, we are running all the graphics on a FIXED position on the screen……. Could we not run everything RELATIVE positions instead…… So we do not need special graphics depending on which phone you have…….. So on the 5 that would automatically space everything out a little…… This does not mean that I do not have to redo the graphics, on the contrary, I really need to redo them but the way it is done would be different…….. What do you think??
I picked up my 5 in HK during the weekend and the current app looks fine so we are not really in a super rush but we should keep up with the Jonses……. So I would just like to vent, in what direction we want to go.
Have a good sunday night
best
felix b.
On Sep 19, 2012, at 2:40 PM, Mark Webb-Johnson <mark@webb-johnson.net> wrote:
Felix,
I was thinking the same. It is quite crowded, and it may just be better to make things a little bigger and more spaced out on the 5.
Regards, Mark.
On 19 Sep, 2012, at 2:37 PM, felix bonnier wrote:
Do we have any new or "extra" info that would be of interest that the screen has been too crowded for until now? notably the top view screen maybe we can redistribute the info a little on that screen……? I'll try to take a look at that over the weekend
best
felix b.
On Sep 19, 2012, at 2:27 PM, Mark Webb-Johnson <mark@webb-johnson.net> wrote:
I guess the following thoughts may be interesting to others in our community...
I've been looking at our iOS App - as I need to send out a new build anyway (to appease the British in America, and their pesky Celcius vs Miles issue), I had a look at adding support for the new iPhone 5 with its bigger display.
The iPhone 4S has a screen of 960 x 640, and the iPhone 5 has a screen of 1136 x 640. An extra 176 pixels in the vertical orientation.
1136 vs 960 is a little over 18% taller. Not much difference, right?
If the developer does nothing to his App, it gets letter boxed. Two black borders of 88x640 pixels are added to the top and bottom, and the application virtual size of 960 x 640 is maintained - even though it is running on a 1136x640 display.
It turns out by adding one file to the build project (a specially named splash screen at the 1136x640 resolution), you tell the iOS not to letterbox you, but give you the full screen. Doing that I expected to get a little 18% layout problem.
Not so fast.
If you look at the screenshot (from an iPhone 4S) below, you can see the status bar, top bar, and bottom tab bar are all fixed in size (whether it is running on a 4S or 5). It is the big blue bit in the middle that gets resized.
The status bar is 40 pixels in height, the top bar 128 pixels and the bottom tab bar 98 pixels. That leaves 960-(40+128+98) = 694 pixels (the height of that blue background bit) to show the real application content.
On an iPhone 5, the status bar, top bar and bottom tab bar all remain the same. That leaves 1136-(40+128+98) = 870 pixels to show the real application content.
870 vs 694 is a little over 25% more usable screen real estate.
This explains a lot to me about what is so important about the iPhone 5 being just that little big taller. 25% more usable screen real estate for an App like ours.
I've already re-worked the App auto-layout to at least look on the iPhone 5. Things like the map, tables and lists just automatically work and take advantage of the extra room. But, fixed screens like the Battery and Car will take some work to think about and take advantage of that new usable screen real estate.
Regards, Mark.
<photo.PNG>
OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
participants (3)
-
felix bonnier -
Mark Webb-Johnson -
Michael J.A. Eymann