I am implementing a message that informs the user that the app is out of date and if the user chooses to not update, the app will close when he clicks No.
A friend mentioned that the only way an app should close is by clicking on the Home button of the device and that Apple may reject your application if you try to do it from a button in your app.
Hm, I think there's a risk that your application gets rejected. Maybe it's better when you write a warning message to the user that the app will quit now.
You could instead show a blank view stating that the app cannot continue its execution unless the user updates clicking a button... You don't need to quit, you just leave the option to the user, either click to update or hit the Home button to quit.
Personally I'd say the best way to deal with this situation would be to inform the user that the app is out of date and need to be updated, then provide them with a button that will take them to the app store.
That way if the user doesn't want to update they can simply tap the home button to quit the app.
I would imagine Apple should approve of this.
You could instead show a blank view stating that the app cannot continue its execution unless the user updates clicking a button... You don't need to quit, you just leave the option to the user, either click to update or hit the Home button to quit.
Quote:
Originally Posted by ChrisMayer
Personally I'd say the best way to deal with this situation would be to inform the user that the app is out of date and need to be updated, then provide them with a button that will take them to the app store.
That way if the user doesn't want to update they can simply tap the home button to quit the app.
I would imagine Apple should approve of this.
I think these two came up with the best idea for your situation.
Apps can be allowed that call exit(0); but I would imagine apple can be particular about the reasons for letting you call it.
I think these two came up with the best idea for your situation.
Apps can be allowed that call exit(0); but I would imagine apple can be particular about the reasons for letting you call it.
Well, I personally wouldn't be happy if my application wouldn't work just because there is a new version around.
I think that the user paid that application and therefore you should leave him using it.
Imagine if the user is somewhere where there is no data connection (or is abroad and do not want to activate roaming data) and cannot use the application he has paid for.
Well, I personally wouldn't be happy if my application wouldn't work just because there is a new version around.
I think that the user paid that application and therefore you should leave him using it.
Imagine if the user is somewhere where there is no data connection (or is abroad and do not want to activate roaming data) and cannot use the application he has paid for.
Just my 2c
That was my thought as well... last time I was abroad, I signed up for a one month international data package; something like 50MB for a month for about $60. It would suck having to use a significant chunk of that just to download a forced app update! And even more so if no special international data plan had been purchased (in which case I think AT&T charges more like $10/MB... or maybe it was $20/MB?).
__________________ Recall It!Tag your notes. Tag your photos. Tag your thoughts. Tag your life.
Close an app with code. Acceptable practice?
Linear Mode
