site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com -pmb _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.a... At 1:28 PM +0200 5/12/06, Lieven Cardoen wrote: yes, make a bundle put it on a nicely layouted diskimage, which opens automatically, and leave it to the user to drag the application, where the user considers appropriately. that's the way it is supposed to work on OSX. installers are only necessary, if you want to actually install system services, but an application should simply be a drag and drop install, wherever I like it to live on my HD. I think the average mac user is not only used to that, but also capable of drag installing an app and might even be offended, if you treat him as being too stupid to drag install an application. I'd even go one step further: a simple application, which needs an installer is something, which I usually don't even install, as I think, that it is looking for trouble to run applications, which were made by developers, which don't even know the basics of my OS. It seems Mac-users don't like the idea of an installer. Is this true? I think Mac users prefer simple drag-installable apps. Using a Disk Image is the most direct route, but there's nothing wrong with using a full blown installer if you think your users would be more comfortable with the hand-holding that provides. Even with an 'installer' though, most Mac users will expect that your application can be simply copied from one machine to another and run. Using an installer to scatter auxiliary files all over the system is considered poor form. This email sent to site_archiver@lists.apple.com