You can deliver an application package to a user’s Smartphone device in a number of ways, including ActiveSync, a web download, an e-mail attachment, Service Indication (SI) SMS (Short Messaging Service) or Service Loading (SL) SMS, or storage cards. The SMS methods for application package delivery take advantage of commonly used text messaging services to send a download URL as a text message to a user. Visual Studio 2005 does not provide a simple solution to application delivery. It is up to the developer or the mobile network operator to select which method to use. The following is a summary of these methods:

• ActiveSync. A user’s Smartphone can be connected (docked in a cradle) to a desktop computer via a USB or serial port. Once a partnership relationship is established via the ActiveSync program, the Smartphone can synchronize e-mail, contacts, calendars, pictures, and so on with the desktop computer. Usually an application’s CAB file is further packaged using an installation setup tool such as InstallShield. To transfer the setup package of an application to the Smartphone, a user needs to run a setup program of the application on a desktop computer, which performs some compatibility checking and copies the CAB file to the Smartphone device. Continue Reading →

  Popularity: 79% [?]

Accessibility and Ergonomic Guidelines: To create an accessible user interface, apply the following guidelines:

• Avoid using fixed font sizes and small font sizes.
• Enable accessibility options such as font size and idle time settings.
• Ensure that the user interface elements are clearly visible in low light.
• Ensure effective and easy-to-read color combinations.
• Group related objects on the screen.
• Ensure that the user interface is predictable. For example, pressing the HOME hardware button should always display the Home screen.
• For Windows Mobile-based Pocket PCs, ensure that the tap region and size of the user interface element are ergonomic.

Useful Resources:

Popularity: 52% [?]

If your device is configured with security turned off, you do not need to install any certificate for signing your applications during development. If you have locked or third-party-signed, two-tier-prompt, or one-tier-prompt devices, you need to install the SDK certificates that you can use during development.

Locked or Third-Party-Signed Device

If you are using a physical device that has the Locked or Third-Party-Signed configuration, the only applications that will run are those applications that have been signed with a certificate in one of the device’s certificate stores. The use of the certificates that are in the certificate stores is controlled completely by the OEM, the mobile operator, or Mobile2Market. Because these certificates are private (that is, their private keys are secret), you cannot use them to sign your application during day-to-day development. Instead, you need to install other certificates in the certificate store, and then sign your application with one of them. Microsoft ships a set of certificates (and private keys) in the Windows Mobile SDK for this purpose. You can find these certificates in the Tools directory and packaged in SdkCerts.cab.
The catch is that only trusted processes can install certificates. Therefore, the device manager (the OEM or mobile operator) must set up a developer program that you can use to install these certificates.
Useful resources:

Continue Reading →

Popularity: 77% [?]