When the playbook was launched by Blackberry we saw the raw potential the device had. In fact many called it as a real tough competitor to the Apple iPad. the real time multi tasking and things such as a very handy 7 inch screen size made for a very interesting tablet. However, with RIM pretty much stalling the
developments and its in ability to add new stuff, Playbook has become rather frustrating. Recently we saw RIM add official support for android applications but that has failed to bring the sort of response RIM thought it would.
So, some of the developers have now started to take things into their own hands. one of such developers called Businesscat2000 has ported and run iOS applications on the Playbook. This is first of its kinds, and here is how it works in the developers own words:
“It works very similarly to how WINE works to run Windows applications on Linux. The app binary is mapped into memory and imports are resolved to point to my own implementation of the various APIs needed. iOS actually uses a few open APIs already, which Playbook supports just as well (GL ES, and OpenAL). The bulk of the work has been in implementing all of the objective C classes that are required. The ARM code of the applications run as-is – the armv6/v7 support on PB/iDevices are pretty much identical, and the code is designed to run in USR mode”
You can watch the playbook in action here:
developments and its in ability to add new stuff, Playbook has become rather frustrating. Recently we saw RIM add official support for android applications but that has failed to bring the sort of response RIM thought it would.
So, some of the developers have now started to take things into their own hands. one of such developers called Businesscat2000 has ported and run iOS applications on the Playbook. This is first of its kinds, and here is how it works in the developers own words:
“It works very similarly to how WINE works to run Windows applications on Linux. The app binary is mapped into memory and imports are resolved to point to my own implementation of the various APIs needed. iOS actually uses a few open APIs already, which Playbook supports just as well (GL ES, and OpenAL). The bulk of the work has been in implementing all of the objective C classes that are required. The ARM code of the applications run as-is – the armv6/v7 support on PB/iDevices are pretty much identical, and the code is designed to run in USR mode”
You can watch the playbook in action here:
