The SGP was born from a deep understanding of the unique requirements of wireless. Competitors' solutions fall prey to substantial development flaws:

• A failure to distinguish the unique needs of wireless devices from those of high-speed network computers
• A desire to create "one size fits all" solutions for all wireless devices
• Unnecessary framework constraints that make it less flexible and expandable, use less of devices' capabilities, and add page rendering and network overhead

In contrast, the SGP takes a fundamentally different approach. It treats each type of device differently from a development and delivery standpoint. It uses the different communication protocols and programming methodologies that are best supported by each device. For example, devices built with the SGP improve delivery by having static data validation logic reside on the client's local persistent storage while dynamic logic is pulled from the server via stream based data sets. Simple #ifdef-like statements dictate how release builds are generated based on device definition sets, for example Series 60 vs. UIQ vs. BlackBerry®. The result? A more functional and rewarding end-user experience and a much more efficient data-delivery mechanism.

In addition, this client-server approach makes possible a "push and pull" effect with pervasive devices such as the RIM BlackBerry®. For example, alerts can be "pushed" to a device, informing a stockbroker that a stock has hit a certain level or informing a horse racing customer of the scratch of a horse d, while vital real-time account information can be accessed very quickly from a user request. To learn more about the Sona Wireless Platform or read our Technical White Paper please email us at: info@sonamobile.com. For more information, contact Sona Mobile at support@sonamobile.com