Filed under: Analysis / Opinion, OS, Switchers, Developer
The confusing art of installing apps
John Gruber of Daring Fireball recently wrote an essay about quirks and user confusion around the application install process on Mac OS X. He had read a post from Alexander Limi's blog about the Firefox install experience, and decided to address it as a system-wide discussion. After this, Andy Kim posted the methods The Hit List follows for installation -- when it's run from a non-standard location, the app asks if it should move itself to the Applications folder. Andy has placed his code for moving the app into the public domain so that other developers can take advantage of it.
With so many ideas around application install strategies, we wanted to take the time to examine the current app installation structure and propose an idea for how it could be better. You could ask, "Why does it matter where my app is installed?" OR "What if I don't want my applications in Applications?" If you're asking the first question, we suggest that you read on. If you're asking the second question, you're probably pretty obsessive about app organization and this post will be covering old ground for you.
What installation methods exist at the moment? The majority of Mac app installations would fall into these categories:
- Disk image installers
- Disk image drag-and-drop
- Archive drag-and-drop
Who can 
All sorts of interesting iPhone apps have sprouted up these past few weeks, but unless you're checking out our own Erica Sadun's 
The Mac web
is buzzing with the news of Boot Camp, the new software from Apple that will allow users of Intel Macs to easily install
Windows XP (this will be a built-in feature of Leopard), creating a dual-boot system. Earlier today, 
![TUAW [Cafepress]](http://www.blogsmithmedia.com/www.tuaw.com/media/tuaw-cafepress-promo.png)
