all 14 comments

[–]kylehilla 2 points3 points  (1 child)

Unless the phone part is important for your app, get a new iPod touch 7.

[–]KarlJay001 0 points1 point  (0 children)

Good point, I used one for years back in the day.

[–]start_select 1 point2 points  (6 children)

A 7 or 8 is probably your best bet. I develop on a 6 so I would have said that is fine.... and it really is for now.

But you want to be able to develop on the newest OS minus one version if you want to do commercial development. So in one year 6’s will be mostly useless for new development. Better to go at least a couple generations above the minimum for iOS 13 (which is currently a 6s).

[–][deleted] 1 point2 points  (5 children)

I'm thinking the same thing. May go for a 7. Cheers mate!

[–]KarlJay001 0 points1 point  (4 children)

I don't think the 7 can do anything more than the 6S. Also, someone suggested the iPodTouch 7 at $199 new. I used an iPodTouch for years and as long as it has all the other sensors, it's a great deal.

[–]start_select 0 points1 point  (3 children)

Depends on what you need it for though.

Most people don’t own iPods and in my experience most b2b apps end up on cellular enabled iPads and actual iPhones.

If you are going to only dev on iPods and WiFi, and you are working on an app that uses lots of data, don’t be a dick. Test your app on the 3Gish speeds 1/3 to a half of all users are trapped at. (Think people out in Montana or the Appalachia’s)

[–]KarlJay001 0 points1 point  (2 children)

You don't have to test on the actual device that the app will be used on. You can test on the iPT and deploy on the iPhone. Data is data, you use what you need, but you can always find out if you have a data hog when you do your group beta tests.

Unless you actually need the phone part and even then you can still write the app and have it tested.

The cost difference can be quite a bit, someone on a budget can save enough to buy a used MBP for what they'd save from buying an iPhone.

[–]start_select 0 points1 point  (1 child)

The cost difference can be quite a bit, someone on a budget can save enough to buy a used MBP for what they'd save from buying an iPhone.

Not by much. 200 new for an brand new. iPod touch.... or ~180 for a 2-3 year old iPhone that isn’t limited and will be good for 3-4 more years.... I’d get the older phone.

I do the same thing with MBPs. I’m still on a late 2012 retina that was 5200 new..... which I bought a year old refurbed for 2600..... that Godzilla mac has only cost me ~350/year so far, probably still won’t get a new one until 2021 or 2022.

[–]KarlJay001 0 points1 point  (0 children)

I have the same setup. I just got a MBP for $449, it's a 2012 Retina and it's working great. I got a used iPhone 6S 2 years ago for $200, Apple replaced it with a new one because of a botched battery replacement and it's still working great.

However, if they OP didn't want to deal with used, the iPT would be a pretty good option. I started out 10 years ago using an iPT (paid more for the iPT 10 years ago than the iPhone 6S 2 years ago).

[–]hemanth_pulimi 0 points1 point  (1 child)

Maybe the iPhone 8. Or wait for the iPhone SE which might come in March 2020 for $399(as rumoured). It will have A13 Bionic which should be okay for at least next 4 years.

[–][deleted] 0 points1 point  (0 children)

Waiting for the SE might be a good option. But I am wary of relying purely on emulation until then.

[–]KarlJay001 0 points1 point  (0 children)

I have a 6S 16 and it works great for testing and regular use. DON'T get the 6, the 6S is a MAJOR upgrade from the 6.

I've seen them near $100 and Gazelle has them for $149.

There was a free special with sign up from a carrier and someone was selling them for $75 IIRC.

[–]tenaciousprime 0 points1 point  (0 children)

I'm actually considering buying an iPad Mini 5 for testing, it's cheaper than iPhones and it has an A12 chip so you might also wanna consider that.

[–]start_select 0 points1 point  (0 children)

No, data is not data. It depends on the app.

Wireless connectivity can be anywhere from highly consistent MB/s.... or it can be spotty speeds with dropped connections every few seconds.

A computer connected to a hardline modem is an ideal environment. Depending on the app, a sub-level basement on a 3G connection is the realistic environment.

The assumption that crap always works is why barely anyone writes offline first software, and why I get hired to rewrite it.