[Windows Mobile Apps and Games] quicksite:
Breaking with convention: iFonz does not install like other apps.

Here's a partial answer: iFonz' author, ssj5trunks, about 4 or 5 releases ago of earlier iFonz versions, decided not to have iFonz install AT ALL on your phone. Many versions ago, iFonz was packaged in a .cab file that followed the expected installation conventions of most Windows Mobile apps: The .CAB file unpacks the various executable files, etc, and registers itself, and then shows up as a Program in the expected place -- either on your device or on an SD Card.

ssj5trunks is a mysterious guy, and I never understood why he chose the newer method that he uses on all CURRENT versions of iFonz: There is NO installation process at all. The file is downloaded as a ZIP, then moved to your phone, then you unzip the file, it becomes an iFonz FOLDER, and inside that folder are the executables and everything else associated with the app.

And he says: Place that folder anywhere. It doesn't matter where at all. You launch the iFonz.exe file and it opens wherever that folder may be. It doesn't show up under "Remove Programs" -- because it was never "installed".

This is the confusion! It is a normal expectation that any new app that's installed shows up in the Programs folder of the device, or the SD card, and thus is recognized as a program by any "show all programs" kind of action on your phone.

SOLUTION: You have to create a shortcut manually, and then drop that shortcut into the START FOLDER of the Windows Directory. And of course then it is seen in any of the "browse programs" lists.

The .dat files I believe also reside in that iFonz folder, which again could be anywhere on your phone.

I'm an information designer, and I disagree strongly with ssj5trunks' decision to use this non-standard process. I am sure his intentions were to SIMPLIFY things, and not have iFonz install anything at all into Windows directory, so that it really is completely standalone.

The problem of course is that when you break with convention -- even if you can argue that it is a simpler and better process, nevertheless, in the end it is generally more of a "curse" than a "blessing" for the end-user because it creates all sorts of confusions that would not arise if the standard were followed. Kind of like HDTV... :)

My unsolicited advice to simo: Return to the standard installation process of a .CAB file. This is an example of people not wanting to THINK "where should I place this folder?" ... Instead of it being a liberating feeling, it is just the opposite. It requires yet another decision, which is more of a drag. Not to mention it breaks the convention, having a ripple effect all down the line... such as when you update to a newer version, "how do I do that?"

It is actually comforting to a user to see a .CAB installation process detect "you have an earlier version of iFonz on your device. It will be removed in this process and replaced by the new version" ... and let the .CAB handle all the .DAT and other settings and theme files. It is also comforting to a user to be able to see the app under the REMOVE APPS list, because then there is no question at all from a user: If I "remove program" this way, I can be sure it is done correctly, without leaving scattered little .dll files throughout Windows.

This is one of the greatest reasons for a standard: so that people feel confident is following the procedures, since they are consistent across app to app to app.

(and now I will wait for simo to get pissed off by this post ! )