iPad Test Hardware For Location Based Services

This question is for developers who have utilized the location based services APIs in the iOS SDK.

I currently have an iPad 2 64gb Wifi only model that I have a buyer for, so I am upgrading to the new iPad with Retina display. I am trying to decide whether or not to get Wifi only versus the LTE. I have no personal need for LTE. My iPad 2 served me beautifully with just wifi and the occasional tethering to my iPhone. But for development test hardware, I am wondering if the additional hardware components will help with testing.

I will be developing an app designed specifically for the iPad as part of a new venture. I can not rule out location based services being utilized.

If the SDK's are provided such that as a developer you simply ask for location data and iOS determines the data by evaluating what is available (i.e. First checks for GPS, then cell, then wifi), then I imagine it doesn't matter if I get the LTE version or not. But as a developer, if you have direct access to the hardware components, it might be better to have a device that has all of the possible hardware. Hope that makes sense. Based on what I have seen so far, it appears to me that apple abstracts the hardware out so you don't have to worry about what hardware is there... it can either get the location currently, or it can't.

While I will research that area of the SDK more closely soon, I am hoping to decide quickly and I am hoping someone with direct experience can comment.

Quick background...I have been developing for over 20 years and recently started with iOS development. I have built one app so far (not in the app store only because we are considering taking the vision in a different direction). I have NOT built anything utilizing location based services yet.

Thanks for sharing!

Michael

 

Thanks for responding.

I totally understand your premise. I tried to keep details to a minimum to keep the original question shorter. We are serious, but in the early stages of entity formation. It's too soon to just go out and buy multiple devices and properly account for them under the entity. Once everything is formalized, we will procure multiple devices to ensure we can fully test and gauge the applications performance and features across the devices.

It is more of a desire to have my personal device, which is conveniently always there, be a device that I can use to satisfy a large number of test/debug conditions/scenarios if I so desire. Certainly not a requirement as we can account for it with additional hardware down the line, but certainly convenient until then as well as beyond.

Your last question is exactly what I am trying to get an answer to... is there a debugging/troubleshooting advantage to having the additional hardware based on what Apple exposes in the location services APIs. If it does, then, to your point, the $130 is a no brainer. Otherwise, why pay for something you don't need. I know it's $130 and in the long run isn't a major deal... but like everyone, I have a family budget I like to stick to : )

It is not a major deal. In fact, I already ordered the Wifi only model... but after doing so, wondered if the extra $130 might actually prove useful. So, before I cancel and re-order, I figured to tackle this two ways... research myself... and ask those with experience.

Thanks again for the response!

Michael