I'm a bit of a novice at this so i'd appreciate some help but if you can keep it lite on the jargon i'd be really grateful

Couple of options come to mind. Easy, 2 minute way is to add text to a splash screen so that when app first opens the user is greeted by a set of T&Cs and by clicking accept they agree and app opens. That would be the quick and easy way. Other option would just be to fire up a notification when the app first loads. Here is an option you could implement to support a T&Cs generation - http://www.touch-code-magazine.com/showing-a-popup-window-in-ios-class-for-download/ Hope some of that helps.

Hi Rob, Welcome to Buzztouch! There are a few ways I could think of doing this (for iPhone mostly): 1. Create a splash screen that has an image which spells out the TOS for the app. I think you can specify how long it stays up before it fades away. 2. Put the same TOS information in the Default*.png image that gets loaded each time your iPhone app gets launched. It stays up for a couple seconds. When you download your source code from Buzztouch, you'll see those black images in BT_Images. 3. Configure your app to use a tabbed layout, and have the first screen be one that displays the TOS. That way, each time the app is launched, people are reminded of the TOS information. Does that help at all? Too technical, or not technical enough? Mark

Ah, dang! MacApple beat me to first response by mere seconds! ;-)

lol. Good stuff, off out my good man! Was just checking forum before I departed. Happy Robert Burns day.

Why not add those terms of use in the App's description before anyone has downloaded it? This could be in addition to the suggestions above. That way, everyone had the opportunity to read and agree before they even downloaded your app.

Good point, @andydahl. You could create a personalized EULA just for that app that spells out the legal stuff. Great idea! Mark

Juts got in and thanks for the input, simple to understand, easy solutions thanks for demystifying this for me, i am getting near the end of the app development stage so sit tight i may need some more help to actually get this thing live. Thanks once again to MacApple, Go Northwest and Andydahl - the help is appreciated and must admit this is the friendliest forum i have ever used R

Have added a splash screen set to -1 for transition time so users have to tap before entering the app - thanks for the help - worked like a treat. R

Happy days.

Unless I missed something, using the splash screen as an agrre to term and conditions screen may not be the best solution. Indeed, this means the users will have to agree to those terms each and every time they fire the app. Personally, I would find that annoying, especially if I were to use the app regularly. To me, a better solution would be the one suggested by MacApple, using a boolean so that the notification is shown only the first time the app is used. Of course, this is just my opinion!

Thanks Aescleah - i got lost at the point you said Boolean (lol), but got the drift - i did look at the article MacApple mentioned downloaded the code and tried to bring it into Xcode but i think this went beyond my technical skills. Thanks for the comment though

Ok, so I'll try to explain :) Basically, a boolean is a value set to YES or NO (also TRUE or FALSE). The idea is to create a boolean that you could call firstlaunch for example, in your appdelegate. Then, when the notification shows up and the user agrees to the terms and conditions by clicking OK, you set the value of this boolean to YES. For the notification not to appear again, you would need to store the value of firstlaunch somewhere (using nsuserdefaults for example), and to do a check in the application:didFinishLaunchingWithOptions part of your appdelegate. If your firstlaunch boolean is set to NO, the notification shows up, if it is set to YES, then you don't show it. This way, users only have to agree once, the very first time they launch the app. I realize this may sound a bit complicated, but it's not as crazy as it seems :) Anyway, I was just giving my opinion about the agreement being necessary each time a user launches the app. You have your app working fine, and that's what matters!

Don't forget, you can customize the EULA when putting the app in the store. Don't know about legalities in all this, but I would feel much more covered with a custom EULA straight from the store, as opposed to a splash screen once I've already downloaded the app.

Thanks for the posts, perhaps the store is the way to go!

Of course the EULA route begs the question of whether anybody actually reads them, and I posit that probably less than 1% of people actually do. So...is having that in existence, whether it gets read or not, sufficient to cover you from a legal perspective? By installing the software, the are acknowledging they have read and agreed to the EULA, whether they have or not. A splash screen or something equally in your face is much more likely to get noticed, and harder to claim you didn't get a chance to read the info. Mark