At 3:27 PM +0100 5-01-00, Daniel McCarty wrote:
> It sounds to me like it would be much more useful from the
>corporate side than from a single-developer end of things.
Exactly!
What Jesse didn't mention is our guideline for using this new feature. We
added this because there are a few cases where it's a really good thing to
do, and it seemed like an important capability. We expect that the vast
majority of apps will NOT specify a default category.
To clarify:
You should probably use a default category if your app goes in one of the
built in categories. e.g. Games.
You should probably use a default category if/when a whole bunch of people
agree that there should be a common category for these things. "Docs" or
"Hacks" might be good examples where more discussion is required.
You should definitely NOT use a default category just to get your name in
lights. That is, don't do what every Windoze developer does and create a
new 'start' menu category with your company name. That's both gratuitous
and annoying. Instead, just let your app go in unfiled. (If you're
excited about seeing your name in lights, create a really whizzy splash
screen or about box instead.)
If you're doing some kind of vertical market app, or creating a whole suite
of custom apps that go together for a custom solution, then you might
consider creating a custom category.
If you're doing a turn-key solution for an industry and need absolute
control over the apps on the device and want to make it easy to take a
device out of the box and turn it into one of 'your' devices, then custom
categories might help.
--Bob
P.S. Yes, this does sound a lot like a Newton feature. And I'm sure it
will be abused occasionally, just like it was on the Newton. <sigh> We'll
have to use peer pressure and public ridicule to stop this.
