08-17-2011 06:27 PM
My first thought is that this is too good to be true. Can Ripple be trusted as a testing tool in place of the simulator? Could it be that something is simply lost in the packaging upon conversion to .BAR (which I wouldn't notice while using Ripple)? If so, doesn't that mean that if my app doesn't work on the sim, it won't work on the Playbook?
If Ripple is a suitable replacement, is there any reason to use the simulator anymore for testing webworks apps?
Thanks to anyone for comments and info.
Solved! Go to Solution.
08-17-2011 09:41 PM
Ripple is VERY close to the PlayBook today.. We will be updating Ripple in a future release to have more "fedelity rendering" to mobile devices.
Today, the closeer your mobile browser is to Chrome, the better Ripple will be. We will be continuing to improve this fedelity experience as we continue to enhance Ripple.
I personally use Ripple for 90% of my development and then do my final tweaking on the actual sim/device.
08-18-2011 07:55 AM
The main problem with Ripple is that it doesn't support special PlayBook events like swipe gestures, multi-touch or the accelerometer, but for 'standard' features, it's quite reliable.
You also have to bear in mind that the PlayBook is going to be much slower at fetching data and for some animations.
08-18-2011 04:36 PM
Thanks to you both for the responses.
Interfasys mentions that fetching data will be much slower on the actual device. Does this mean fetching data from the Internet, or from memory on the device? My Webworks app uses WebDB.
08-18-2011 04:44 PM - edited 08-18-2011 04:47 PM
You will have no speed issues with WebDB. It can be faster than a desktop, depending on your development environment, because the PlayBook uses flash memory.
I was talking about fetching data from external servers. The WiFi latency will come into play, but there is something else that makes the PlayBook slower.