Oh, Objective C is certainly more dynamic. It uses a message passing mechanism. You can do this in Objective C without a compile error (note "id" is a generic object type)
id anObject = Do some initialization; [anObject passSomeMessage];
The closest in Java would be:
Object anObject = new SomeClass(); anObject.callSomeMethod();
Which wouldn't compile.
(Please note I haven't used Objective C nor Java in a while. Please excuse any errors.)
Can Phonealyzr and the BB SDK do that?
And judging by the number if people I see using their BB when they are not at work - I think there is a huge market for a networked entertainment diversion.
But I have a question - do you have some bug tracker, where your users can put bugs and suggestions? I would like to suggest to split the minutes in usage summary by the direction, incoming and outcoming calls separately (in addition to weekdays/weekends as it is now).
At my day job I use python and js to do web development while this is my spare-time project and to be honest, Java isn't so bad. Yes, it's tiresomely verbose, but Eclipse and the Android plug-in are an awesome IDE and since you're dealing only with the mobile-specific SDK, you don't have to contend with issues that make Java bad in other contexts (heavy frameworks, endless XML config files, etc). Perhaps someone with experience in both can clue me in, but I doubt Objective C is less verbose or more dynamic than Java.
But I think you're right in that people might be missing an opportunity by focusing so heavily on the iPhone. The BB SDK is more powerful than the iPhone's, there's more than twice as many BB users than iPhone users and I don't think anyone will argue that they're any less affluent than iPhone users.
Mostly, I think, it'll depend on how RIM promotes the app store and the kind of deals it manages to get the carriers to accept. I worked for RIM a few years ago and saw how incredibly difficult and demanding it is to work with carriers, as they are the actual manufacturer's "customers" and their interests are frequently at odds with those of users.