As mentioned above what is the target resolution for the Apple TV? For example like the iPhone 5 was 640x1136, and the iPad was 768x1024. I know that TVs vary in size so there is no definitive size. But maybe a recommended size would work to have a starting point. Like having a fixed height and adjusting the width of the app to fit the tv.
The Apple TV standard resolutions for a modern 16:9 television are:
1920 x 1080 (1080p Full HD, preferred if supported)
1280 x 720 (720p for a HD Ready television)
858 x 480 (480p SD)
The new Apple TV runs apps at a standard 1920x1080 resolution at a 1x scale. This means that, when building tvOS apps, the screen size, in points, that you must use when building your interface is also 1920x1080.
Have a look here: http://code.tutsplus.com/tutorials/an-introduction-to-tvos-development--cms-24848
Related
What does the word native means here? What aspect ratio will be set if I choose native aspect ratio?
Native aspect ratio means that your game will always be rendered on the native (natural) resolution of the device. For example, an iPhone 6S Plus has a native resolution of 1920 x 1080, meanwhile an iPad Pro has a resolution of 2224 x 1668. If you choose native resolution and build for iOS, the resolution will be different between devices with different resolutions.
I am not sure but i think it means that you can either set your custom resolution for every device or native resolution i.e. the resolution that is available on the device.
I have a developer working on a game for me for ios for iPhone 5. He stated the resolution we must use for the game is 320 x 568, but the iphone 5 has a resolution of 640 x 1136 and he stated that this is the resolution for the graphics and not the game leveling design. The game is a 2D maze game.
I am still learning, so any help would be greatly appreciated. Which resolution is the correct resolution? Why is it half of what apple states?
Thanks in advance
Here's the story. When Apple introduced the iPhone 4, it introduced the "Retina Display". That is, the iPhone 4 had a screen with twice as many pixels on it than the previous iPhones. So to compensate, Apple came up with the screen points system. It works like this:
-On non-retina devices, 1 point = 1 pixel
-On retina devices, 1 point = 2 pixels
-On any device, the programmer's coordinates are done in points.
-On any device, the art assets should be done using pixels
Example: I have a 200x200 pixel image used on retina devices. When I load the image into a view, the size of the view is 100x100 points.
In order to make sure your image is loaded properly, you have to use the #2x suffix. If you have a 200x200 pixel image "myImage.png", it will be loaded as 200x200 points and will be scaled up on retina devices. If instead you name the image "myImage#2x.png", instead it will interpret the image as 100x100 points, and will scaled down on non-retina devices. You can also have two versions of an image (Apple recommends 2 images although it isn't strictly necessary). If you have both 100x100 pixel "myImage.png" and 200x200 pixel "myImage#2x.png", it will interpret them as two versions of the same image, and will use the #2x one on retina devices and the other one on non-retina devices. In both cases, the image will be interpreted as 100x100 points.
You might also want to take a look at Apple's High Resolution Guide.
I'm designing an app that creates graphics for retina displays. One of the benefits I want to offer to the users is that the graphics designed the iPad app would look exactly the same on the iPhone.
However, by eyeballing the results, it seems to me that the physical pixels of iPhone retina display are about 20% smaller smaller than the iPad's one. So the 57x57 pixel space displayed on iPhone and iPad retina displays side by side would appear to have different shape - iPad would be larger.
I'm interested if there is really a difference in the physical dimensions of retina display pixels, or if it is a bug in my code.
Retina display on iPhone 5:
1136x640-pixel resolution at 326 ppi
Ipad (retina):
2048x1536 resolution at 264 pixels per inch (ppi)
So as you can see the density is higher on the iPhone than the Ipad. From this I would say you are correct.
They are not the same. Those devices use different displays that have different pixels/inch.
iPhone Retina: 326 PPI
iPad Retina: 264 PPI
http://en.wikipedia.org/wiki/List_of_displays_by_pixel_density#Apple
Am a newbie to iOS App development and to design. I was wondering about these 2 questions:
can I create a high-resolution image & use it for all the devices (be it retina or non-retina)? (why should one create a low-resolution image intentionally for a non-retina device? why can't everything be simply high-resolution?) ... I hope it isn't a dumb question!
And what do we exactly mean by 'high-resolution' here? '1024pixels X 1024pixels' ? how high is 'high'' really for a retina display?
Any help please?
"High Resolution" means twice the pixels in each dimension on iOS (and OSX). So if you have an image that is 23x10 pixels on a non-retina display, the high resolution version of it must be 46x20 pixels in size.
If you name your high resolution images like this: lowResImageName#2x.png, the system will automatically choose the high res image on retina devices.
As others have said, you use special low-res images to maximize quality (because you can choose to leave fine details out of a low-res image, etc.) and minimize memory footprint (because the non-retina variants have had half the RAM of the retina versions so far).
It also helps to think in non-retina pixels, because one non-retina pixel equals one "display point", the unit in which iOS measures sizes.
iOS devices' resolution is as follows:
standard retina
iPhone, iPod Touch 320 x 480 640 x 960
iPad 768 x 1024 1536 x 2048
iPhone 5 - 640 x 1136
Why create a low-resolution image? Because it will automagically be used on non-retina devices, saving memory.
For some images that will work just fine, but for certain ones (if your image has some fine text for example), they will come out looking jagged or distorted when scaled down automatically. There may also be cases when you want something displayed differently(I've had occasional images with cool gradient effects that just don't look right on a low res device, so I've had to remove some detail in the low res image to make it look okay).
The other answer is also correct in that if you allow for both cases, low res devices will only load the low res images into memory, so the app will be using less memory. This is only an optimization for those cases, but it is still helpful since typically you can assume that the low res devices will have less memory to begin with since they are older.
Retina graphics, the high resolution graphics you are mentioning, should be double the point values for width and height. What I mean by that is, on all iPhone-sized devices, the size of the screen is 320 points by 480 points. On non-retina devices, translates to 320 pixels by 480 pixels. On retina devices, this translates into 640 pixels by 960 pixels. Everything is double in both the horizontal and vertical directions.
What this means, is you should have two versions of all your image assets. So if you have image that you want on the screen that is 44 points wide by 44 points tall, you should have two images ... Image.png which will be 44 pixels by 44 pixels, and Image#2x.png which will be 88 pixels by 88 pixels (for retina devices, this is what the #2x represents).
Why have two versions, and not just the high rez version? Because it takes processing power to 'compress' the larger version into a smaller version. It's much easier to just already have the lower resolution version, and you are saving valuable memory.
The first question was answered by H2CO3. You safe memory on old devices (think of iPhone 3G, many current Apps are terribly slow, yet well-coded apps still work fine)
What does high-resolution mean?
E.g. on a non-retina device you can show some example.png of 300x200 pixels using [UIImage imageNamed:"example.png"].
High-res would mean, you had an additional example#2x.png of 600x400 pixels, i.e. double size. Then you're app size is bigger, both devices have appropriate graphics but you save memory on the old device (Which would have to allocate 4 times the memory with no added improvement for the user, because it still has only a 300x200 pixel-display-space for a 600x400 pixel image).
I am building an iPhone app interface and I know the dpi has to be 163, but when it comes to the size of the file, I was looking through all the recommendations and found 2 different answers...
Does anyone know what size should i set the Photoshop file at? The answers I have so far are:
"The screen on the iPhone is 480×320, minus the 20-pixel status bar (making a 460×320 working screen size). The screen shots on the App Store should not include the status bar."
"400 x 320 or
960 x 640 (iPhone 4)
You must also consider the landscape mode (320 x 400 and 640 x 960)"
I would really appreciate the answer. Thanks!
You can forget about DPI, the resolution is what is important for you.
So the answer is...
320 x 480 pixels for iPhone - iPhone 3GS (and iPod Touch, first -> third gen)
640 x 960 pixels for iPhone 4 and iPod Touch 4th gen
This is for full screen apps. This will help you a lot, when designing UIs for iDevices.
SD resolution (link)
Retina, HD resolution (link)
That's it...
Designing an app, you just need to use the right resolution.
So it is display resolution - top bar:
640x920 (retina without the top bar)
320x460 (iphone up to 3gs)
The Official Answer is in Apple's iTunes Connect Developer Guide, which you can download from iTunes Connect after logging in.