09-16-2008 01:59 AM
Solved! Go to Solution.
09-16-2008 03:33 AM
09-16-2008 04:00 AM
thanks. what about testing on handset? As soon as the simulator test is finished, we have to test the software on actual handset. The hardware we need itself costs about 400 USD. What about the activation and service fee. And moreover will we need a BES in the future (to only test the developed software)?
09-16-2008 04:11 AM
09-16-2008 04:50 AM - edited 09-16-2008 05:59 AM
I agree completely with Simon's comments, but just wanted to add that you should not underestimate the marketing costs that you will incur when trying to sell to Blackberry owners.
Unless you can get corporate buy-in to the application you are developing, you will struggle to sell to the large companies, and corporate administrators typically have their user's BlackBerrys locked down so users can't add their own software (no matter how much they want that weather reporting app).
This really leaves the consumer market, and for it, the trick seems to me to making your application visible. Apple have, for me anyway, done a great thing in creating the App Store, which seems to me (and I'm not speaking from any experience, just observation) to make it easier for the smaller guys to get their apps to wider market. There is nothing similar for BlackBerrys that I am aware off, though Handango is mentioned in most dispatches.
09-16-2008 05:18 AM
09-16-2008 08:35 AM
I've used these guys before, provide remote access to real handsets and lets you check a lot
of phones pretty quickly,
I've personally found that if you have a server available, the best thing to do for RIM or more generic apps is
to just write scripts to compile, package, sign, and upload your app and then mail a link to your phone
or those who are willing to help test. Cycle time for a 64k app is maybe a few minutes depending on how long it
takes for your phone to reboot and anyone who can get your link by sms or email can test. Of course, you need some
server infrastructure to dispatch requests to phone-specific targets etc.
Also, instrumenting an app for feedback reports is not hard at least for rim specific stuff but I haven't tried
it more generally. So, the time from getting a bug report (" this option stopped working when I used some other option , what is wrong?") to
debugging can be short too.
09-16-2008 12:04 PM
I've used deviceanywhere.com many times in the past and would recommend them. My last recollection is that they are $200/month/carrier for access to quite a few devices/carrier. One thing to beware of though is that you need to remove any intellectual property from the device when you're done with it otherwise it will be there for whoever gets the device after you. Anyway, this isn't an ad for deviceanywhere; just reporting that they're a good service, especially for things like smoke testing against many devices.
To generally recap others' posts: Developing for RIM is among the cheapest alternatives out there. The $20 for signing keys is the only upfront cost until you need to get on hardware. Many moons ago I bought my own ARM compiler and Verisign certificate to get into BREW development which was around $2K total. Bought an iMac and a Leopard upgrade to get into iPhone which, again, was around $2K. So $20 ain't nothing for development.
Distribution is another matter which only Apple has really addressed (or rather, nailed), but that's another topic.