Re: EULA presentation requirements?
Re: EULA presentation requirements?
- Subject: Re: EULA presentation requirements?
- From: SevenBits <email@hidden>
- Date: Mon, 10 Feb 2014 20:20:37 -0500
On Monday, February 10, 2014, Rick Mann <email@hidden> wrote:
> Does anyone have any references for the need to present a custom EULA when
> our app launches (after the user has downloaded it)? I know that Apple and
> the App Store provide a mechanism for providing a custom EULA, but people
> in my company are considering requiring the user to agree to it when the
> app launches. I'd really like to avoid this annoying user experience.
My opinion is, while it may be annoying, it puts the user upfront with your
EULA. In some other installation methods, like installers on Windows or OS
X's own Installer.app, the user can easily skip the EULA to actually get to
the important part, the install. In my opinion, this is worse than simply
displaying a pop up box prompting the user to agree to the EULA. At least
this way you make it clear that this is important as opposed to just
another install step that can be skipped.
>
> I tried googling, but found very little in the way of advice or common
> practice.
>
> What do you guys do?
I use either an EULA supplied by the App Store or I present it to the user
during install or first launch. Another thing I do sometimes is license
under widely known terms (I.e BSD license) and then say, "this software is
under the BSD license, go look it up if you want to read it". This is
simple, straightforward, and the user doesn't need to do anything if
they're already familiar with the terms of the license.
>
> --
> Rick
>
>
>
>
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden