I'm not sure. To be honest, I was shocked to see my game running at 10-30fps. It has always maintained 60fps during development, and I profiled it very thoroughly to ensure that there were no memory leaks.
Like I said, any game that was doing much of anything experienced slowdown. The most hard-hit one was some game with very nice art where a guy runs along, and you tap to make him jump. Another game where you direct missiles ran pretty well until walls started collapsing and performing physics calculations, then it grinded to a halt.
I'm using fairly efficient collision detection in my game. Upon profiling tonight, I determined that one of my most expensive functions was playing sound...if that's the case, my code can't be that inefficient. Perhaps it is in large part due to the flash implementation on RIM's end. Technically, the PlayBook I tested on was a prototype, and was not running final software. Maybe it will be a different story tomorrow. I certainly hope so, but I also know better than to assume. In any case, if you have a game with pretty much anything moving around constantly, I suggest you take a trip to the store tomorrow and test your app just to be safe. An ounce of prevention, as they say...
Additionally, I recommend profiling your games for memory and performance if you haven't done so already. My whole game was one giant memory leak until I profiled it the final weekend of development.
