Re:The Cost of Building BlackBerry Apps
by spacemanaki on Wednesday December 01, 2010 @04:01PM
(#1959591)
Everything in this post is inline with my experience working on the platform over the past 10 months.
But they miss one of the worst offenses in my opinion: Applications which access certain APIs are required to be signed. If you want to run code on the device you must sign your app, even if it's just for testing during development. The signing process requires connection to THREE different RIM servers, which are notoriously flaky. This results in extreme delays (hours) which are hard to account for while developing. RIM has recently upgraded their servers or otherwise addressed this issue, but it is far from solved
Take a look at the 7-day (the times are mislabeled, I believe) charts on this page, set up by a third party, not RIM, for an example of their uptime: http://isthesigningserverdown.com/beta/
But they miss one of the worst offenses in my opinion: Applications which access certain APIs are required to be signed. If you want to run code on the device you must sign your app, even if it's just for testing during development. The signing process requires connection to THREE different RIM servers, which are notoriously flaky. This results in extreme delays (hours) which are hard to account for while developing. RIM has recently upgraded their servers or otherwise addressed this issue, but it is far from solved
Take a look at the 7-day (the times are mislabeled, I believe) charts on this page, set up by a third party, not RIM, for an example of their uptime: http://isthesigningserverdown.com/beta/