03-02-2011 03:08 PM
Please post here concrete things you wold like see RIM provide to ISVs in 2011.
1. Significantly improved communications with and support of developers. (There are signs of good efforts in this area already, but it's been a hit-and-miss affair over the 3 months I've been involved.)
2. Significantly faster/shorter release cycle for SDK and simulator updates. Better than monthly is reasonable and feasible. Be more agile! The single biggest reason we don't have more and better apps yet is the delay in these releases and the opaqueness of any schedule for them.
3. Significantly improved quality in what is released. Regression testing appears to have been ignored, and it's questionable (from our point of view) whether issues were addressed in priority order.
4. Significantly improved documentation. (Professional technical writers should be involved. The current docs seem to be written by the programmers themselves.) To assist with this, implement better web-based tools for the docs, allowing direct feedback from its consumers (that would be us) to you in the form of corrections and comments which are curated by full-time staff at RIM.
03-02-2011 04:43 PM - edited 03-02-2011 06:26 PM
some additional thoughts:
* More examples, tutorials on how to develop AIR applications without Flash Builder. ($600 is a little steep for those just getting into this development environment)
On the AIR webcasts, cost mitigation of Adobe tooling was mentioned as being considered, but I have not seen any developments on this. See this thread for a few idea pitches for how this might be done in a way that is fair to all parties:
RIM - note that being short on cash is not the only reason why someone might balk at the cost. Another perfectly valid reason is just plain investment discipline. Nobody knows how the marketplace is really going to turn out at this point. Many years ago people could actually make money selling PC shareware; these days, not so much.
Edit: And BTW while it can be argued that anyone making a serious effort should be able to recoup the cost of the tools easily - sure that's plausible ... but they are just one expense on the ledger.
03-06-2011 08:51 PM
Coherent, consistent, and timely cross-SDK support of critical API's like e.g. the analytics API.
Such API's need to be architected so that it is not an error-prone, thankless chore for someone at RIM to update the various language bindings when a feature is added or a bug is fixed. Maybe some of them even need to be pure services.
Basically, for critical API's don't make developers wish they were on some other technology stack halfway through a project because the API release was planned for the developer's chosen stack but only executed on a different stack due to avoidable technical issues.
03-06-2011 10:41 PM - edited 03-06-2011 11:45 PM
I think @liangbf may have just posted the animated gif question to the wrong thread. This reply is just to get the subject line back on track for the next person who hits 'reply'.
03-07-2011 10:46 AM
03-08-2011 11:54 AM
@Jtegen - MSOhm addressed this in another post. He says that you can have multiple key registrations on a single computer so long as they are in different user accounts since the relevant files (db, etc) are stored in user directories.