Cod app and library can be for different platform versions?

I am writing an application that must run on a wide range of versions of the device. Some of the application contains code depending on the version, but a little is independent of the version. Are there problems or special considerations for structuring an application as a main .cod file compiled for a specific platform version and a .cod of library which contains functions of "lowest common denominator" compiled for, say, 4.2.1?

What you propose works OK for us.

The library is developed in a different project and workspace, the "interface" between the use of the application and the library is the jar file, which is imported into dependent projects.  This means that the two become completely independent, and it is possible to exchange the library for a later version on the device, without changing the main cod.

The biggest problem is multiple applications with the same shared library requiring different versions of this library.  This section of the shared library has been discussed widely in the DevCon, so I hope that Rim will contribute to this requirement in some way in the future.

Tags: BlackBerry Developers

Similar Questions

Maybe you are looking for