roGridScreen can be very fast if it doesn't need to grab much data from the internet. What I ended up doing last time is caching all the graphics, and handling the grid screen itself, and then using a poster screen to display and retrieve content lists. The fewer layers you use, or someone was saying by using multiple cavases, you can make it nearly as responsive as the default screen types, sans button sounds of course. Hopefully the gridscreen gets a few more upgrades/added flexibility in the future. I set the content manually, but I suppose it could just as easily be changed to dynamic and simply transferred before anything is displayed on the screen. Looking over the component spec, I don't think using that feature will allow you to keep up with a .125ms interval on responsiveness, but I'd also be happy to look at an example to see what it is supposed to do in a real life environment.
