Software Development Kit (SDK)

Overview

• For an SDK Edition comparison, see SDK Editions.
• iOS and Android SDK Editions are Apache Licensed, see SDK Editions.
• For BlackBerry Licensing details, pricing, and feature comparison, see BlackBerry SDK Details.
• For general questions, see the FAQ below.

FAQ

What is it?

Metova maintains software development kits for the various platforms to reduce code duplication and increase quality and throughput. Each SDK has significant effort contributed to it each year, and our collective customers benefit greatly.

Do I need to read this if we are focused on iOS and Android only?

Probably not. The iOS and Android SDK is Apache Licensed, and the source is available to customers. Much of the remainder of this document refers to the BlackBerry SDK which is not open sourced for a number of reasons.

Specifically, what is Metova's SDK for BlackBerry?

Metova's SDK for BlackBerry is a vast set of software libraries that are reused across all customer applications. The BlackBerry SDK has millions of dollars invested in it, and the maintenance of the SDK is spread across all of Metova's customers. This provides not only cost savings in effort and a dramatic decrease in total time spent, but yields greater compatibility for all of Metova's customers' applications across the world device population.

A few features:

• Network intelligent roaming
• Guaranteed delivery on the network (queuing)
• Polished User Interface components
• User Interface performance management
• Thread pooling and event dispatching for asynchronous execution
• Theme management and declarative styling of user interface components
• Cross-device/multiple OS capabilities from one source code base
• Internationalization
• One touch, automated build system (Maven plugin)

Do you need to purchase an SDK License in addition to professional services?

No, absolutely not. During all engagements, Metova utilizes the respective SDK. In iOS and Android, this is Apache Licensed, which is a commonly accepted non-viral open source license. In an engagement resulting in a BlackBerry application, you are granted royalty free distribution rights. There is no cost to you and no need to purchase a BlackBerry SDK Developer license unless you want to maintain the application development in-house and wish to access on-going updates and the same development tools. For more information, see SDK Editions.

Must you buy a developer license in order to maintain the application in-house?

No. With Android or iOS, the source code is open to you. With BlackBerry, you may maintain your application with the BlackBerry Free Edition of the SDK. The primary limitation is that you will not receive updates to the SDK on an on-going basis, and will not have access to Metova's development tools or resources. See SDK Editions for a comparison.

Why buy the BlackBerry Enterprise Edition?

Metova provides the BlackBerry SDK Developer program to assist our customers that would like to bring development in-house and would like to continue to receive ongoing maintenance releases as well as use of the advanced developer tools. By purchasing a development license, you may maintain and enhance your software after initial development without the need to use Metova's professional services. In other cases, your team may simply want to work in conjunction with the Metova team and need access to the same development tools and libraries.

Is there a warranty?

No. The SDK is licensed as-is. Functionality built in the SDK may not be hardened for the large variety potential uses our customers may derive. The SDK is constantly maintained and updated as new needs arise during professional services engagements, but Metova makes neither a guarantee nor declaration of fitness for any particular purpose.

What does this mean to you?

The Metova software development kits are not shrink wrapped libraries for widespread adoption and use. Rather, they are tool sets that evolve and change daily to meet the needs Metova encounters in delivering application development. As such, functionality is created or enhanced for a particular purpose without regard for the vast permutations of usage that may be desired by a broad audience.

So what are you paying for with the BlackBerry Enterprise Edition?

You are paying a small fee to access a library that has millions invested in it. In addition to the maintenance and changes Metova makes on behalf of customers during professional services engagements, we must also maintain the build system, package repository and knowledge base that is updated as a part of our normal operations. See SDK Editions and BlackBerry SDK Details for more information.

What if you find a defect or need an enhancement?

In order to fix a defect or make an enhancement that you specifically need, you will need to engage Metova's professional services. Many defects are fixed every day, but the only ones guaranteed to be fixed are those done at the request of a professional services customer under contract. You may wait and see if it is fixed, but there is neither a guarantee that it will be addressed nor a specific time line.

How large is the BlackBerry SDK compared to your project code base?

In Q1 2010, the Metova SDK consisted of approximately 414,141 lines of code. The Maven build plugin consisted of approximately an additional 26,923 lines of code. Small applications for customers start around 12,000 lines of code, average between 25,000 to 50,000 lines of code, with large projects around 80,000 lines of code. Outliers have been as high as 120,000 lines of code. At compile time, the unused lines of code are automatically pruned from the code base making the final binary build as small as possible. Nonetheless, Metova's customers are automatically afforded the advantages of a continuously maintained code base of 414,141+ lines of code.

How do you get access to the BlackBerry SDK?

Ask your Metova contact for BlackBerry SDK access, and they will have an invoice sent to you. Once payment is received, your current credentials will be given access to the Developer Zone, Javadocs, as well as the Maven repository which maintains historical as well as up to the minute releases of the SDK generated from the continuous integration Bamboo server.