Why should you move to 22.214.171.124?
By Joe Huang on May 03, 2013
It's great to see our engineering team has come through and delivered a bunch of new functionality in just a few month, since the release of ADF Mobile 126.96.36.199 in late October of last year. As Shay blogged about the new features in the previous entry, there are plenty of reasons to move to the new version. Many of developers in the ADF Mobile community has been looking for ways to push real time notification to ADF Mobile applications, or looking for ways to properly display file content on both iOS and Android devices. 188.8.131.52 now provides these functionality.
One great fact about the new push notification support is that native capabilities are used. This means you would leverage Apple Push Notification Service or Google Cloud Messaging Service to push notification to ADF Mobile applications. There is no proprietary or specialized messaging application you would need to implement - you can directly communicate with these push notification services with any backend servers.
File display support is critical for any application that needs to display file content. In the 184.108.40.206 version of ADF Mobile, you would leverage a LocalHTML feature to display files on iOS devices, but there is no solution for Android. If your application needs to display file content such as PDF or Word document, you should migrate to 220.127.116.11.
Another great feature is "Application Archive" support. This is a great re-usability feature for ISV or SI partners - partners can simply create an application archive that includes all application artifacts and re-use the application in different engagements. For each individual customer, the SI partner or customer themselves can extend the application archive with new functionality, and deploy it within their enterprise. This is also needed if the customer needs to sign the application with their own certificates and profiles, as needed by most third party Mobile Application Management packages.
Lastly, there are numerous performance enhancements - for example enhancements around ListView performance.
Instruction for migrating an application to 18.104.22.168 is documented in the Migration Section of the ADF 22.214.171.124 Release Note.
However, there are also a few other important reason to move to 126.96.36.199 now - please review these carefully and see if they apply to you:
- Apple has stated that, as of May 1st, 2013, all apps submitted to the app store must properly support the iPhone 5 form factor. iPhone 5's screen size is 1136x680 pixels with a 16:9 ratio, where as previous iPhone screen size is 960x680 pixels with 4:3 ratio. Similar to all apps developed before iPhone 5 was released, ADF Mobile apps developed using 188.8.131.52 would be displayed in letter-boxed format. This no longer meets the updated Apple UI Guidelines. Therefore, if you are planning to submit an ADF Mobile application to the Apple AppStore, you must move to 184.108.40.206, which has proper support for the iPhone 5 form factor.
- 220.127.116.11 also adds support for iPad mini - allowing you to specify icons and splash screen for iPad Mini.
- If you wish to test using iOS6 simulators that comes with Xcode 4.5 and above, then you must move to 18.104.22.168. There is a known issue with application unable to rotate even if the device is rotated.
- JDeveloper and ADF Mobile 22.214.171.124 have been certified to work with more recent mobile SDKs (i.e. Xcode 4.5/iOS 6 and latest Android development tools/SDK). Therefore, if you wish to use these new SDKs, you should move to 126.96.36.199.
- There are many bugs fixed in 188.8.131.52 - if you are currently encountering any bugs in 184.108.40.206 version of ADF Mobile, check out this list of bug fixed.
On behalf of the entire ADF Mobile development team, we would like to THANK YOU for your continued support of ADF Mobile. We would definitely like to hear from you.