Many developers contact NSTL and ask this question: "I just developed the next ‘killer’ application, what do I do now?"

When answering, we always ask, "What does your application do, what network is it for, and have you tested it on the handsets supported by that network?"

Developers often underestimate the daunting tasks needed to take new applications to market. A few things to consider are:

• Which network operators are targeted and what requirements do they have?
• Which handsets will be supported?
• Which languages will be supported?
• Is there a requirement for getting the application signed?
• Has the application been thoroughly tested?
• Have you budgeted for the cost of any required certification program?

Navigating the Operator Maze

Each network operator has its own requirements and process for getting an application on its deck. Several operators accept industry-standard certifications such as JavaVerified™ or Symbian Signed. A larger set of operators have their own criteria for accepting applications – some of which are based on industry standards. Most operators require developers to have a business arrangement with the operator prior to their accepting an application. The process can be very confusing, especially for developers just entering the marketplace. Each operator has its own list of handsets that need to be supported. Also, some operators have specific requirements for language support. Be sure to check with each operator to find out what steps you will need to take to get onto that operator's deck.

Once you have an operator that will accept your business proposition, you will need to support a wide range of handsets. One of the issues in supporting all these handsets is getting the application ported to the required platforms. This can be outsourced to any of a wide range of companies specializing in porting, but once you have support for the list of handsets, how do you make sure everything works correctly? There are a number of solutions from just buying all the handsets and doing your own testing to using testing services from an independent testing company.

The network operator might also require you to support multiple languages. For example, a particular network operator might require your application to support what is known as EFIGS (International English, French, Italian, German, and Spanish). You should consider discussing language support with a translation and internationalization services company. Doing this upfront will save a lot of time reprogramming your application at a much higher cost later in your development cycle.

You should also learn if the operator or device OEM requires your application to be signed by a signing authority to prove your identity. This can take some time to open your account. Therefore plan for this early in your process.

Test and Test Again

Finally, but certainly not least important, is the consideration of how you will conduct Quality Assurance testing. You should plan to do testing at major milestones throughout your development cycle. Thoroughly testing the application before you begin porting to a variety of handsets is critical. You do not want to port bugs to all the handsets you will support. QA testing can be done on one network or you may want to test your application across a number of networks. This is especially important if your application will be using communication APIs or other network specific resources.

Once you have done a thorough QA pass on your "gold master," you should also consider the level of testing you need on each port. This can be a subset of your QA test plan or a more thorough test if you feel that is required. Often this decision is driven by handset quality and compatibility with your master builds.

Simultaneously you should be performing "pre-certification" test passes if you will be submitting your application to one of the industry standard programs such as JavaVerified, Symbian, TRUE BREW™, or Microsoft Mobile2Market. Each of these programs has a published set of requirements on which to base your testing. You should make sure your applications meet these requirements before submitting to any of these programs. However, the tests conducted for these programs are not a substitute for good QA testing, and generally focus on platform integration tests. The program tests can assure your application meets the requirements of the program but do not in and of themselves connote a level of quality.

Once you are confident your application can meet both operator and program requirements, you are ready to submit to network operators or to one of the industry certification programs. Hopefully, you have done all the upfront preparation and your application will get to market smoothly.

One positive thing you have done already is engage with Motorola and joined in Fast Track. Fast Track presents many excellent resources for developers – one of which is NSTL. NSTL is the Fast Track testing partner; we also provide testing services directly to Motorola, helping them get your applications onto their handsets.

NSTL can assist you at many stages of this process. We are a full service outsource QA facility as well as the only test lab authorized to test for all major certification programs. NSTL has testing facilities in the Americas, Europe, Asia, and India. We have excellent relationships with many network operators and handset OEMs. You can call on NSTL at any time and we will be happy to give you advice. We are pleased to be part of MOTODEV's Fast Track program and look forward to working with its growing developer community.

Information about NSTL can be found at our Fast Track Center. You can also send inquiries to info@nstl.com.