You don't believe me? Go on and try to stream a video on a Android 1.6 VM.
BTW: I'm developing a iPhone App in my spare times and a Android at work.
11–20 of 51 posts
You don't believe me? Go on and try to stream a video on a Android 1.6 VM.
BTW: I'm developing a iPhone App in my spare times and a Android at work.
-------- http://bit.ly/eTAvV5 --------
-------- http://bit.ly/eTAvV5 --------
-------- http://bit.ly/eTAvV5 --------
-------- http://bit.ly/eTAvV5 --------
-------- http://bit.ly/eTAvV5 --------
Gold autumn, personality Men’s clothing Shoes, Travel bag that grabs an eye coat Chao packet Free transport
-------- http://bit.ly/eTAvV5 --------
-------- http://bit.ly/eTAvV5 --------
-------- http://bit.ly/eTAvV5 --------
-------- http://bit.ly/eTAvV5 --------
-------- http://bit.ly/eTAvV5 --------
-------- http://bit.ly/eTAvV5 --------
Earlier quoted context omitted.
So initially there were problems with the code and afterwards with his development process. I fail to see what this got to do with iPhone vs. Android. It could have happened with both platforms.
His point is that Android made it easy to test multiple platforms, and Apple did not.
It just isn't possible to make the case that this aspect of android doesn't make things harder and still retain any semblance of honesty or credibility.
Earlier quoted context omitted.
> The Simulator is always running the latest version. Actually this appears to be false now. I just fired up my iOS Simulator, and in the "Hardware" menu I can select which OS version I want, either 3.2, 4.0.2, 4.1, or 4.2.
That's right you can select all those versions accept 3.1.3 and that is the problem.
Just install Xcode 3.2.2, which does include support for the Simulator 3.1.3.
You can get it from http://connect.apple.com/ - select Developer Tools, find 3.2.2. in the page, download it, and install it to a directory other than the default /Developer, so your existing tools won't be affected. You might want to skip the installation of the developer utilities, since the ones from the current Xcode will be more up to date.
But you still are missing an important point. The Simulator is not an emulator. It does not run the same instruction set as the device itself. So the best way to test is still with actual devices running the versions of the OS you are interested in testing.
Instead of testing on 5+ devices for Android, you just have to buy an old iPod touch with 3.1.3 on it. Is it too costly for you?
You can create AVDs (Android Virtual Device) that have different hardware capabilities (RAM, Camera, SDCard, Screen Sizes etc.) and run different versions of Android - 1.6 to 2.3 as of now. This makes testing your app very easy - you just set a minimum SDK version and if your app doesn't do weird things (uses features that don't work on a version of Android and declares support for that version)- most times it works very well.
API Levels - API changes are mostly additive and old APIs are carried forward as-is. http://developer.android.com/guide/appendix/api-levels.html
More than anything though - the developer can just push a beta in the Market and receive excellent feedback from users - user submitted stack traces, device info, feedback etc. can be very valuable in identifying and fixing compat issues.
Instead of testing on 5+ devices for Android, you just have to buy an old iPod touch with 3.1.3 on it. Is it too costly for you?
Earlier quoted context omitted.
That's right you can select all those versions accept 3.1.3 and that is the problem.
Why is that the problem? Just install Xcode 3.2.2, which does include support for the Simulator 3.1.3. You can get it from http://connect.apple.com/ - select Developer Tools, find 3.2.2. in the page, download it, and install it to a directory other than the default /Developer, so your existing tools won't be affected. You might want to skip the installation of the developer utilities, since the ones from the current…
However the bugs I had would have been picked up in the simulator.
Thanks for the pointer for the older version of Xcode. That would have been great but at this point I may as well do my 3.1.3 testing on the device.