6 ms·
I've got some mixed reactions to their reaction. 1. Yes - great, they replied publicly. While others may have complained before, at least they're finally rep
by mgkimsal 16y ago
I've got some mixed reactions to their reaction.
1. Yes - great, they replied publicly. While others may have complained before, at least they're finally replying in public.
2. "Suggestions like his are critical in helping us improve our products and processes". Why should things ever be as remotely bad to start with as what the OP was describing? Downloading an installer program that just copies an ISO to a folder? SDK and Simulator only available as separate downloads? Repeated data entry on multiple screens? Does no one at RIM sit down before things are released and say "OK, let's test this end to end and see if it really makes sense."?
Again - great that they responded, but having multiple poor experiences rolled up together gives the impression that RIM just really doesn't care that much, and can't be bothered to make the process for developers remotely straightforward.
- delynator 16y ago+1 for mgkimsal. when will businesses learn that developer products (APIs, Appstores, etc) need QA and Ops support and SLAs and regression testing before release -- just like any other product they would put out there?