How Should Mac Apps Be Distributed?
daringfireball.net
daringfireball.net
The only reason why Mac application can't be distributed like Windows .exe files is that Mac applications are actually directories. Excluding .pkg installers 99.99% of the time the .dmg file is merely just a container for the single .app directory.
Safari automatically unpacks .zip files by default on download. Where's the mystery here. Why bother with dmg in the first place
The Finder and LaunchServices are the only bits of code that care anyway.
(-:
The main reason they haven't done it on OS X is that it would be completely backwards-incompatible. They should have done it in Snow Leopard (an easy choice if your app uses GC), but if they did they didn't tell anyone. Instead they added optional zip/deflate compression to HFS, and used it for most of the system files.
"Internet-Enabling a Disk Image
Although all disk images can be transported through the Internet, users need to open them, retrieve their contents, and discard them. An Internet-enabled disk image automates this workflow. After a user downloads an Internet-enabled disk image from a network using a web browser, the image is automatically opened, its contents placed at the user’s download location, and discarded (in the Trash). This improves the manual install experience by performing a few tedious tasks for the user. "
Too few devs seems to be aware of this.
Anyway a custom installer for Firefox is a backward idea.
= tmk =
http://en.wikipedia.org/wiki/Apple_Disk_Image
http://en.wikipedia.org/wiki/Mac_OS_X_v10.2
= tmk =
He problem is that the application isn't moved, it is copied. After putting a copy in the Applications folder, she just drags the application from the disk image to the dock. Now she has two copies, and uses the slower one in the disk image. Sometimes she even drags the disk image to the Application folder too. It's all very confusing
I agree that the disk image system is very confusing for the casual user. The zips seem to give a much nicer interface
I'd bet this pattern would be a whole lot more effective if there were text prompting the user to take this action. It seems like most implementations of this pattern focus on bling rather than usability.
Maybe github & sourceforge has a mac repository. So you'd have the default one from apple, plus any open source apps from github & sourceforge. Individual developers who just publish code on github wouldn't need to setup their own repository. In a way, it's kind of how the ruby community distributes their packages.
Fuck debian-legal. I hope their heads fall off.