View Single Post
Old 02-02-2010, 03:14 AM   #4
zacheryjensen
Addict
zacheryjensen has learned how to read e-bookszacheryjensen has learned how to read e-bookszacheryjensen has learned how to read e-bookszacheryjensen has learned how to read e-bookszacheryjensen has learned how to read e-bookszacheryjensen has learned how to read e-bookszacheryjensen has learned how to read e-books
 
Posts: 229
Karma: 887
Join Date: Mar 2009
Location: Utah, USA
Device: iPad, iPhone 4
Quote:
Originally Posted by nikkie View Post
What? Why? Several of my friends develop for the iP* devices and they have already started. They are ready to go.

There is an emulator after all.
Hardware device testing is required for app submission and approval. I'm a developer myself. So unless Apple makes what would be a very foolish concession here, there will be a delay between the first shipments and the first dedicated apps from most developers.

In the past, they definitely have provided early release hardware to star developers though, so I expect the top most popular 50 or so development houses will have day 1 iPad releases. Apple will likely supply hardware to around 50 developers that will commit to a day 1 release of something they know is popular.

Also it's worth noting that what you get in the SDK is not an emulator, it's a simulator, it doesn't run the binaries that run on the real device and therefore can not be trusted as a testing platform. It only exists for the purpose of speeding up the development cycle so not all test runs have to be deployed to hardware. The software running in the simulator will run as fast as the computer it's on, with 3d capabilities that the real device may not support and so on. That's why hardware testing is required.

So while it will result in an annoying delay for a month or so, it is well worth it in the long run to have these policies in place.
zacheryjensen is offline   Reply With Quote