3 ms·

What Jamil7 commented.. I stopped/dropped my iOS dev efforts. I had an app on Apple Store, and eventually pulled it because of the constant updates demanded by

What Jamil7 commented.. I stopped/dropped my iOS dev efforts. I had an app on Apple Store, and eventually pulled it because of the constant updates demanded by Xcode. Yes things were still working, but unless someone is willing to dedicate 'many' days every 3-6-9-12 months to catch-up on new requirements, it's just not worth it. For someone who does dev for a living, it's game on, for others who may want this as a side hustle, it can be overwhelming (keeping up with Apple). I don't blame them, this cat&mouse just didn't work for me. It could as well work just fine for the other part-time/hobby devs.

lordnacho 6y ago
Same here, iOS was never my main thing, but I did write a couple of apps for it. I can't remember the specifics, but it seems way too common for them to change an API that ought to be already settled, for lack of a better term. This just means that every time they change something, the devs have to rebuild, with an unknown amount of time spent. It might be as easy as just changing a couple of lines, or they changed the API so much you have to rethink your code. And this is for apps that aren't using anything new, it's the old APIs that are changing under them.
msh 6y ago
What constant updates demanded? I recently pulled it but I had a ios app since 2010, nothing advanced and was only updated every couple of years. There was only twice I had to do a update because of iOS updates. Once a crashing bug and once to look nice on large screen devices.
- HenryBemis 6y ago
  You are "lucky" that your code was not affected/impacted from the changes throughout the decade. I have written my first app in the winter of 2017, and because of the functionality/libraries/code I used, every update has been a pain in the butt. Not impossible, but I did it as a hobby, not as a profession/income. I understand the need to progress and develop/create/evolve the programming languages, techniques, environments, it's just not fit for a hobby (in my case)(YMMV).
  - valuearb 6y ago
    What has forced you to update? iOS has not changed how core APIs work in a decade.
valuearb 6y ago
I have Apps from 2013 and 2014 that have never needed updates. What has forced you to do them?

lordnacho 6y ago

Same here, iOS was never my main thing, but I did write a couple of apps for it. I can't remember the specifics, but it seems way too common for them to change an API that ought to be already settled, for lack of a better term. This just means that every time they change something, the devs have to rebuild, with an unknown amount of time spent. It might be as easy as just changing a couple of lines, or they changed the API so much you have to rethink your code. And this is for apps that aren't using anything new, it's the old APIs that are changing under them.

msh 6y ago

What constant updates demanded? I recently pulled it but I had a ios app since 2010, nothing advanced and was only updated every couple of years. There was only twice I had to do a update because of iOS updates. Once a crashing bug and once to look nice on large screen devices.

HenryBemis 6y ago
You are "lucky" that your code was not affected/impacted from the changes throughout the decade. I have written my first app in the winter of 2017, and because of the functionality/libraries/code I used, every update has been a pain in the butt. Not impossible, but I did it as a hobby, not as a profession/income. I understand the need to progress and develop/create/evolve the programming languages, techniques, environments, it's just not fit for a hobby (in my case)(YMMV).
- valuearb 6y ago
  What has forced you to update? iOS has not changed how core APIs work in a decade.

valuearb 6y ago

I have Apps from 2013 and 2014 that have never needed updates. What has forced you to do them?