Google Nexus 10: 2560x1600, 300ppi, 10" PLS Display, Exynos 5250 (Cortex-A15), Android 4.2 - Page 10

Amazon charges state sales tax now and not every seller can do prime shipping. I was in the same boat as you about where I thought I could buy a nexus. I guess Google sold a bunch to retailers before the holidays so there would be more availability for consumers. I think most people were under the same impression and because of that Walmart had a good stock of them.

Or the lack of a product that meets the price they pay...

You may be able to get USB OTG up and running in 10 minutes, but it's still not as convenient as sticking in a little Micro SD card. Also better in what way? The Nexus 10 is sharper, but the iPad 4 has superior contrast, black levels, and colour accuracy. The way Android works, all apps should support the Nexus 10's resolution... no?

You're a bit out of date in regard to Apple. A developer can update an iPhone app to include the iPad version as well. There are many "universal" apps on the App Store. Also it doesn't matter that Apple has "hardcoded" the app resolution in iOS, since it's easily changed, and all iPhones until the recent iPhone 5 have used the same base resolution. There's never been anything in place to stop developers from coding their apps to support multiple resolutions and aspect ratios, it's just it's never been necessary until the last couple of years.
No need to belittle our choice in a smartphone.

Of course they aren't...They have never had the option of having one in their device, therefore do not know what they are missing out on. Apple doesn't put an SD slot in theirs because they would rather you pay an extra $100 for the next level device for more storage instead of buying the cheapest and then dropping a 32 gig SD card in it for 30 bucks...

I guess they could always do what Sony did and make a special SD card like they did for the Vita that only works with the Vita cause of the special size...That would be the Apple thing to do.

They should in theory but an example of an app that need to be updated to support devices with a screen size larger that 7" would be flipboard.

This is true to an extent but not in the way that android handles it. To quote from Apple’s Drawing and Printing Guide for iOS:

So while apps may work across non retina displays and retina dislpays they are not truly taking advantage of the higher ppi found on the retina display. When the iPhone 5 was introduced this system no longer solved the issues for developers because the resolution was not being doubled in both directions like it was when the retina display was introduced, but instead the vertical margin was increased from 960 pixels to 1136 pixels. Correct me if i am wrong but this means that unless apps are remade specifically for the iPhone 5 they are displayed with black bars above and below the app frame on screen. This would make the large screen size only useful in the sense that you can fit another row of apps on each home screen. Since iOS apps have always be programmed to a specific resolution (hard coded) this is also the reason why the iPad mini, being a new screen size for the iOS line, has the same resolution as an iPad 2. To me this seems like a poorly thought out tactic that just limits innovation.

Also I apologize if I offended you with my iSheep comment. That was not my intention. I would just like encourage current iOS users to consider their options before they blindly go out and buy whatever Apple decides to slap their logo on. If you are buying you devices purely as a status statement then you would be making the right choice with an Apple product. But if you want a device that has higher performance at a lower cost and the ability to customize your phone to how you use it then go out and buy an android device as you next phone or tablet. If you really dislike it you can always return it.

I see. That's not true. They are benefiting from the pixel density -- everything becomes much sharper. it's just it isn't gaining any more workspace. This system made it almost effortless for developers to support the Retina displays -- all that was needed was higher resolution graphics. With the iPhone 5 -- you only need to provide an 1136x640 start up image to enable your app to work with the iPhone 5's size. Yes it would mean they have black bars until updated, only to make sure that developers have made sure their app is going to work properly with the iPhone 5.

Developers don't necessarily hardcode their apps -- for example if I was to place a button at the bottom right of the screen, I would ask for the iPhone's resolution and use those values, not assume it was 480x320. If I have coded my app like that, then there should be relatively little changes to make to my app to get it working perfectly with the 5.

It isn't difficult for Apple to change the resolution of iOS.Up until recently it's always been the same because they've always released devices with the same resolution, and it's not limiting at all -- it's a good idea because it reduces fragmentation. If I want to develop an app for iOS all I need to think about is three different possible workspaces: 480x320, 536x320 (which is very similar to the former) and 1024x768. For the Retina displays I need only provide higher resolution assets. You didn't, don't worry. I'm not in anyway unhappy with my iDevices, but I'm invested in Apple's ecosystem so Apple would have to screw up severely for me to switch. The droids may have higher performance, but the iPhone 5 is still faster in a lot of tests and often smoother too. I also prefer the App Store to Google Play.

I think you are missing what this actually means. An app that runs on a non retina display will work on a retina disply with no issues because the resolution is exactly double in both dimensions. So 1 pixel on a non retina display becomes 4 identical pixels on a retina display. This means would apps would look exactly the same on both screens with no added clarity on the retina display. The only way to improve clarity is to remake the app specifically for a retina display. As for being invested in the apple ecosystem I can see why you are so attached. Did the introduction of the lightning port force you to reinvest in a slew of new devices? For me personally the only thing extra that I have invested in for my android devices was a $0.99 usb host cable (USB OTG). This allowed me to not only hook up my existing 3 3TB external drives to any of my android devices but also allowed the use of a usb keyboard and mouse, wireless xbox 360 controller and external wifi adapter for extend wifi range. I can also use that cord to connect to my Canon T1i and use my tablet and phone as a remote that can control every aspect of my camera including Live View mode. And then of course the fact that I can just plug and hdmi cord into almost any display in my house for obvious reasons. So in reality you would not have to invest any money in android other than the device itself.

As for these tests you claim iDevices beat android in my nexus 10 after loading a custom rom and kernel beat every benchmark of the iPad 4 and iPhone 5. But you should also know that benchmarks serve no purpose other than bragging rights because they do not reflect much real world performance.
Edited by Holy Chicken - 1/1/13 at 2:06pm

Also if you don't want to take my word for the image quality on a retina display read this: http://forums.macrumors.com/showpost.php?p=15057933&postcount=75

Actually this isn't what happens at all. The developer doesn't have to "remake" the app for the Retina display -- the app is resolution independent, and iOS automatically renders it at the higher resolution. That's why the only work developers need to do to support the Retina display is provide double resolution assets -- no reworking of the code is required to make it work with the Retina display. (Though of course you may need to fix some bugs depending on how well you've written your app.)

This is because of the point coordinate system that iOS uses. An app is defined as 480x320 points, and a point can be any number of pixels -- and in the case of current Retina displays, it is 2.

Let's say you've designed an app and you've placed a button with the dimensions 10, 12, 60, 30 (x, y, w, h). When this app runs on an iPhone 3GS -- which has a 480x320 resolution -- that button's dimensions translates into 10, 12, 60, 30 pixels, but when run on an iPhone 4 -- which has a 960x640 resolution -- that button's dimensions translates into 20, 24, 120, 60 pixels. So the actual rendering of the button is being spread across four times as many pixels, resulting in a much sharper quality. It is not simply being stretched (duplicated pixels), it is being drawn across more pixels. I'm not referring to accessories, I have very few of them. The one I do own and care about would work if I bought the adaptor from Apple but it would be cheaper to just buy that cable again since I really only have that accessory.

It's apps, music, movies, books, tv shows, etc., which I'm invested in through Apple. My whole family uses iDevices and Macs, and we all use the same account, so everything we buy either on the iOS App Store or the Mac App Store is available to all our devices. So we are quite invested. All our iDevices, Macs and our Apple TV (box) work together seamlessly too. There's nothing Android offers which would entice me to switch, and even if it did the benefits of it would have to outweigh losing everything I have with Apple. That depends on the benchmark. GeekBench and the like, yes. But more real world tests like SunSpider, Octane, Kraken, and similar, etc., all carry some weight. Also there are graphics benchmarks which are important, and battery life benchmarks too -- the Nexus 10 is no slouch in either of those departments, but the iPad 4 does pull ahead.
This is talking about how the Retina display works in OS X on the Mac, not on iOS. The two shouldn't be confused. On iOS all you need to do is compile your app against iOS 4 and it will run as a "Retina-app" on a Retina device, with or without code changes -- though if you've coded it poorly (or lazily) you'll obviously need to fix any bugs. On the Mac it's more complicated as the OS is much more complicated and you aren't forced to only get apps through the Mac App Store. Though I'm not thoroughly versed in how much work is needed to get a Retina app on the Mac up and running, I do know it is more, and that they are simply upscaled until updated to support it. Again this process shouldn't be compared against the process on iOS.