CODEWITHSUNDEEP
ios
Andrew S
Andrew S

Reputation: 2987

Strategies for Implementing a Disclaimer Screen in IOS

In IOS you are not allowed to exit an app progrgrammatically (which I personally believe is ludicrous).

In my app I intend to display a disclaimer screen with some legal text and a agree and disagree buttons. When the user agrees, the app's main menu is presented. When they disagree, I would like the app to close. I would intend this to display only once when the app was first used and the disclaimer agreed to.

However, you can not close an app programatically because Apple don't like it. So

1) is this not a good reason for developers to need a close feature?

and

2) What usable and graceful alternative do I have?

Upvotes: 1

Views: 2063

Answers (3)

lnafziger
lnafziger

Reputation: 25740

In the Human Interface Guidelines, Apple recommends not to quit programmatically and offers two alternatives:

Don’t Quit Programmatically

Never quit an iOS application programmatically because people tend to interpret this as a crash. However, if external circumstances prevent your application from functioning as intended, you need to tell your users about the situation and explain what they can do about it. Depending on how severe the application malfunction is, you have two choices.

Display an attractive screen that describes the problem and suggests a correction. A screen provides feedback that reassures users that there’s nothing wrong with your application. It puts users in control, letting them decide whether they want to take corrective action and continue using your application or press the Home button and open a different application

If only some of your application's features are not working, display either a screen or an alert when people activate the feature. Display the alert only when people try to access the feature that isn’t functioning.

Therefore, I would go with something that meets the first option, and say "You must accept the terms of this agreement in order to contine."

Upvotes: 2

Anne
Anne

Reputation: 27073

Is this not a good reason for developers to need a close feature?

Yes, but Apple does however think different.
The only thing you can do is accept and find the best alternative

What usable and graceful alternative do I have?

Show:
Disclaimer

In case rejected show:
Disclaimer

Upvotes: 0

Fab1n
Fab1n

Reputation: 2284

If, on a mobile App, this would be a useful case, it would have been implemented.

Generally, it is not a good practice to display screen at the beginning, because suddenly the user gets disappointed, because he doesn't get entertained a little bit from the beginning. On the other side, applications that require to be logged in do the same thing.

Suggests to handle your problem:

  1. Present your screen at the beginning and if the user declines, you can show your app with no representative data and elements and maybe a box that says "sorry, you to precede, you have to accept my rules"
  2. Do this agreement on a web-based service with login credentials and present a login screen a the beginning with the option to register a new account, where registering implements accepting the rules of using your service or app. This gives a more convenient approach, as it is done by many many services.

Hope this helps...

Upvotes: 0

Related Questions