Frequently Asked Questions
- What is the most current version of the Designed for Windows Mobile™ Software Application Handbook?
- Can we send for testing a pre-configured device with the application already installed?
- Our application is designed to work only on a certain model device. Is this acceptable?
- Our application is included as part of the application package on specific devices in-ROM and is not distributed any other way. Is it eligible for the logo?
- Are web-based applications eligible for Windows Mobile logo?
- Do you require an installation manual?
- What is the turnaround time for a test pass?
- Where is the application tested and where is the test process managed from?
- If a nonconforming item is found, what is process for dealing with that?
- My application is available in two versions: one for the 2003SE operating system and one for Windows Mobile 5. Must I test both versions, or can I get logos for both from testing one version?
- Must I retest my application if I make minor bug fixes?
- I have an application that specifically demands a Phone Capable PPC / PDA. Can this be tested under the Designed for Windows Mobile logo program?
- Must the application support both landscape and portrait modes to achieve the Windows Logo certification?
- When WiFi and other similar icons appear on the NavBar, the application name is truncated. Is this acceptable according to the current guidelines?
- The application uses binary files for data storage. Is it mandatory to have custom icons associated with these files?
- Can we submit our programs to you for testing in the same manner as we deliver them to our end users, i.e. cab file?
- Can we put an "OK" button in the NavBar in the main window of the application, or do we have to put an "X" button?
- Do we have to display the name of the current window or dialog box in the client area of the application?
- Does the installation mechanism created in Visual Studio 2003 meet the criteria of certification?
- The title of the application has to be displayed on the NavBar, but is momentarily displaying other information on the NavBar against the requirements for certification? For example, when a new window is being opened, the NavBar displays information with the path of the file. When the new window is loaded, the title of the application is displayed on the NavBar.
- Our application requires a Korean Language pack. Is this a problem?
- Our application requires free disk space of about 850MB and uses an SD or CF flash disk for file storage. Is this acceptable?
- Our product is a client-server product so to fully run it, you'll need to install a Windows 2000 or Windows 2003 server, but we believe you can do all the necessary certification testing using just the mobile client. Is that consistent with other client-server applications you've tested?
- My application will be used by different mobile carriers and must be modified to provide specific access and configuration information for each. Will each carrier's variation require a separate logo test?
- In the Designed for Windows Mobile Software Application Handbook for Smartphone, it states that an ‘Application Must Not Interfere with Incoming Call Functionality’. Our application does block calls while transferring data over the web services. Would this behavior fail the Logo test?
- All of our on screen GUI elements are custom made. Our games also run in full screen mode, therefore no NavBar/TitleBar are visible at all. Is this acceptable?
- What is the most current version of the Designed for Windows Mobile™
Software Application Handbook?
For Windows Mobile 6 applications, May 2007
For Windows Mobile 6 applications, October 2006
For Windows Mobile 2003 SE and earlier, May 2004
- Can we send for testing a pre-configured device with the application
already installed?
If the user is going to have to install the software and perform configuration, then you must provide the product as an installation format (CAB or executable installer). Part of the criteria for the certification is that the installer is operable and we can not grant certification without testing it.
- Our application is designed to work only on a certain model device. Is
this acceptable?
No, a device-specific application is not eligible for the Designed for Windows Mobile logo.
- Our application is included as part of the application package on
specific devices in-ROM and is not distributed any other way. Is it
eligible for the logo?
Yes, this is acceptable and Install/Uninstall requirements are waived. You must send the device to QualityLogic for testing, and include a prepaid return address label. Send the device to:
QualityLogic Inc.
ATTN: Windows Mobile Logo Testing
UPID #___________________________
6148 N. Discovery Way, Ste. 175
Boise, ID 83713 USA
- Are web-based applications eligible for Windows Mobile logo?
If the application does not actually install on the mobile device it cannot be tested. We can test an application that acts like a client to a web-based application.
- Do you require an installation manual?
All documentation should be provided to allow us to effectively test the product.
- What is the turnaround time for a test pass?
Typically, within five business days.
- Where is the application tested and where is the test process managed
from?
Testing and test management are conducted in our Boise, ID office. Business issues are handled by our Moorpark, CA headquarters.
- If a nonconforming item is found, what is process for dealing with
that?
We issue a detailed report of any failures, and we will waive the retest fee ($300) if you resubmit the application for retest within one business day.
- My application is available in two versions: one for the
2003SE operating system and one for Windows Mobile 5. Must I test both
versions, or can I get logos for both from testing one version?
Only the highest version of the application needs to be tested. Earlier application versions can receive the logo as a result of the one test.
- Must I retest my application if I make minor bug fixes?
Application bug fixes, minor enhancements, and correction of spelling errors do not require retest, as long as the base functionality is the same and there are no new features added (so the version would remain the same). Otherwise a test of the new application version would be required.
- I have an application that specifically demands a Phone Capable PPC
/ PDA. Can this be tested under the Designed for Windows Mobile logo
program?
Yes, your application can be tested on a Pocket PC Phone Edition device. It may not, however, require a specific model of brand of Pocket PC Phone Edition device. - Must the application support both landscape and portrait modes to
achieve the Windows Logo certification?
The application will only be tested in landscape mode if that is a stated feature of the program. There is no requirement to make your application landscape-capable to receive the "Designed for Windows Mobile" logo.
- When WiFi and other similar icons appear on the
NavBar, the application name is truncated. Is this acceptable according
to the current guidelines?
No, this is not acceptable. In accordance with guidelines, "The name displayed on the NavBar should be fully visible and may not be truncated."
- The application uses binary files for data storage. Is it mandatory
to have custom icons associated with these files?
This icon requirement principally applies to the application. As you aren't saving 'file types' (like a .doc for Word), this section won't be applicable for anything other than the program itself. This applies if the data you are saving will be in a DAT file (or something similar) and will therefore not be directly opened by the user, but will always be opened indirectly by the application itself.
- Can we submit our programs to you for testing in the same manner as
we deliver them to our end users, i.e. cab file?
Yes, CAB files are totally acceptable. There are only two acceptable formats, MSI Installers or CAB.
- Can we put an "OK" button in the NavBar in the main window
of the application, or do we have to put an "X" button?
The NavBar can contain "OK" but cannot contain any other application specific functionality.
- Do we have to display the name of the current window or dialog box
in the client area of the application?
Titles should be displayed within the client, such as current view, document, etc. The NavBar can only display the application name.
- Does the installation mechanism created in Visual Studio 2003 meet
the criteria of certification?
The installer should either be in the form of an executable or an MSI. It is also necessary to supply a CAB version of the product so that certain tests can be performed. It is acceptable to only supply the CAB file.
- The title of the application has to be displayed on the NavBar, but
is momentarily displaying other information on the NavBar against the
requirements for certification? For example, when a new window is being
opened, the NavBar displays information with the path of the file. When
the new window is loaded, the title of the application is displayed
on the NavBar.
The NavBar should only display the application name. The function described would fall into the category of using the NavBar for application-specific functionality, which would be classified as a failure.
- Our application requires a Korean Language pack. Is this a problem?
We can install the language pack and test the product.
- Our application requires free disk space of about 850MB and uses an SD or CF
flash disk for file storage. Is this acceptable?
From the testing requirements, assumption of external storage is not allowable. If the data on the external storage is not needed to run the application and have it continue with its primary functions and maintain stability, this requirement will be met. All information that will be provided to the user should be provided to QualityLogic.
- Our product is a client-server product so to fully run it, you'll
need to install a Windows 2000 or Windows 2003 server, but we believe
you can do all the necessary certification testing using just the mobile client. Is that consistent with other client-server applications
you've tested?
If possible, we prefer that you provide a simulated or sample server database so we are able to gain access to all of the different application screens, menus, and option dialogs and can verify general functionality.
- My application will be used by different mobile carriers and must
be modified to provide specific access and configuration information
for each. Will each carrier's variation require a separate logo test?
No, this type of modification does not require a test for each variation. As long as the base functionality (name and version) remains the same, only one carrier's variation of the application will require testing. The logo can be applied to all variations of the application.
- In the Designed for Windows Mobile Software Application Handbook for
Smartphone, it states that an ‘Application Must Not Interfere with
Incoming Call Functionality’. Our application does block calls
while transferring data over the web services. Would this behavior fail
the Logo test?
That behavior is acceptable and would not cause a failure. The intent of the requirement is that an application’s user interface must not interfere with the normal call user interface, and it cannot delay the user’s ability to answer an incoming call. Applications that run in full screen mode or always on top must move to the background to allow the incoming call user interface to appear on top.
- All of our on screen GUI elements are custom made. Our games also run in full screen mode, therefore no NavBar/TitleBar are visible at all. Is this acceptable?
That is no cause for concern. The only way NavBar or TitleBar will be checked is if any portion of the software can run in a non full screen mode (a configuration panel for example). In most full screen applications, these are considered "not applicable".
©
2007 QualityLogic Inc. All rights reserved.