Hmmm, I'm not Adobe expert, so you'd rather get details from them, but the applications to consider include: Illustrator, Bridge, Photoshop, AfterEffects, Dreamweaver... a whole bunch of them. I'd have to point you to adobe.com instead of listing all of them
Since most of the Adobe apps are extensible, developers like myself, may want to deliver commercial scripts or plugins and install them into predefined locations. Once again, since I am on the free version, I cannot test it, but before installing the product, I'd have to check whether the client has the target application installed. For instance, If I am about to install an Illustrator script, I should test whether a directory [Program Files]/Adobe/[Adobe Illustrator CS#]/Presets/Scripts/ exists. CS# stands for Illustrator version, which is also important to test for, for product compatibility reasons.
If the directory does not exist, user may still want to install the product, but as a developer I would not want to create an artificial directory path, only to mimic Illustrator's buried directory, but I'd rather install the assets into a user-selectable folder, where user can read my product help, release notes and such.
That's how I see it.
Art