the simulator will run with the performance and memory of your workstation, this is NOT a realistic test of your app.
Have seen many devs that run into showstopper memory/or speed problems once they switched to on device debugging
( always test on the device !! )
Moreover you have subtle api inconsistencies, some calls work on the simulator that fail hard on the device ..
stuff life location , rotation , storekit , etc are different ( but that should be rather well understood )
so if you develop on a fast workstation and not a underpowered laptop then you should always prefer a native simulator ...
( my experience is based on working with iphone,j2me,and android emulators )
the simulator will run with the performance and memory of your workstation, this is NOT a realistic test of your app. Have seen many devs that run into showstopper memory/or speed problems once they switched to on device debugging ( always test on the device !! )
Moreover you have subtle api inconsistencies, some calls work on the simulator that fail hard on the device ..
stuff life location , rotation , storekit , etc are different ( but that should be rather well understood )
so if you develop on a fast workstation and not a underpowered laptop then you should always prefer a native simulator ...
( my experience is based on working with iphone,j2me,and android emulators )