Every PalmOS programmer should be familiar with the concept of creator IDs and also on how to obtain them!

Registering creator IDs is a fast process - and many of us push it to the time when the RC is under test. The logic behind is simple - a program can exist without a creator ID, but not vice versa. This is OK, but…

Beta testing can get painful.

Applications that share creator IDs can duke it out among one another in the most impressive fashions. They can bust each other’s notification registrations. They can garble up one another’s preferences and databases. Hunting those errors down is a major pain in the hide…

Blocked creator IDs cause an extra build.

Usually, an application’s creator IDs are stored in a common header file. Changing them usually triggers a full compile that can put all kinds of crap into the output! Our column about The Art of Beta Testing just ended a few days ago - and one of the core points made was that untested compilations are dangerous and must not be released! This can give you a nice delay…

So, to cut a long story short: get your creator IDs early! It may not pay out immediately, but can save you and your beta testing team loads of work!

What do you think?

TamsPalm - The Palm OS Blog is a great source for reviews, exclusive screenshots, and updates on all the new, 21st Century mobile technology as soon as it’s news to us!

[tags]beta test,creator id,mobile development,common header file,full compile[/tags]