Publishing Mac Apps

[Graham Samuel]

I agree (from limited experience I admit). The hassle referred to usually includes messages from the OS that many non-tech users will find mysterious, confusing and generally off-putting. Quite a lot of users don’t really understand the requirement to log in just to get some bit of software updated, let alone installed, so the burden then falls to the developer to write an essay explaining what the user has to do and sending it by email etc. Of course we all need security, but the whole thing has got out of hand IMHO. I think maybe Windows is worse, with its insistence on changing passwords after a time even if you’re working on an unconnected machine in the middle of nowhere…

Graham

> On 17 Nov 2020, at 07:02, John Balgenorth via use-livecode <use-livecode at lists.runrev.com> wrote:
> 
> I think that makes it easiest and safest for
> the end user.  If you did  not code sign the
> app they could probably still use it but it
> would be a hassle.
> 
> JB
> 
>> On Nov 16, 2020, at 9:52 PM, Bill Vlahos via use-livecode <use-livecode at lists.runrev.com> wrote:
>> 
>> If I want to distribute Mac apps should I get a $99 Apple Developer account and Notarize them? I don’t anticipate putting apps in the Apple App Store?
>> 
>> Are there other considerations or options to avoid problems as Apple continues to enforce more restrictions?
>> 
>> Thanks,
>> Bill Vlahos
>> _______________________________________________
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
> 
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode