BlackBerry client

In UA 8.0 you can deploy mobile applications directly from Mobile Web Studio to the BlackBerry device, including over the air (OTA). Unwired Accelerator does not require the BES server to operate, but some functionality, such as push synchronization, requires Internet and e-mail service. Optionally, you can set up the UA client for direct TCP/IP connection through your carriers that support it.

The method are available for deploying mobile applications from Mobile Web Studio to BlackBerry devices:

Offline mode – make sure the “Make available for disconnected mobile devices” box is selected in the Properties Editor in Application Builder. To use offline mode, the UA offline BlackBerry client must be available on the BlackBerry device.
Online mode – use pages and page groups to create a container for the mobile application. See the Unwired Accelerator Developer’s Guide for more information.

Two BlackBerry clients are available for running mobile applications on the mobile device:

UA offline client – provides access to mobile applications developed in UA and deployed to the mobile device. UA Server stores the list of applications marked “Make available for disconnected mobile devices”. The BlackBerry offline client sends a Refresh Apps request to the UA Server for the list of applications that has the “Make available for disconnected mobile devices” attribute turned on. You select an application from the list, and Sync the application. The mobile application is cached in memory on the mobile device.
BlackBerry browser – provides real-time access to mobile applications and data. If an application cannot be opened in UA offline client, the BlackBerry browser is used.

Table 6-1 describes the advantages and disadvantages for using UA offline client and BlackBerry browsers. Use the information to troubleshoot mobile application problems.

**Table 6-1: UA client versus BlackBerry browser**
Option	Advantages	Disadvantages
UA offline client	Has better table UI support. BlackBerry browser does not support tables. Has list/detailed view of records. We can control the columns in the list/detail view. Provides offline access to data. The application data is stored in device memory. Access content quicker since data is stored in memory.	Not live application content. Requires network connection to sync. Memory limits on mobile devices.
BlackBerry browser	Real time access to data. Application data is always up-to-date because it is always online. No need to sync.	Cannot access application content if you are out of range (no network connection). Need to be always connected. Lack of table UI support. Columns are wrapped to the next line.