Blackberry, iphone issue

[agashi]

Hi,

whether liberator (streaming) can work well on the Blackberry and the iPhone browser? or just working in pc only?

What minimum requirement for pc or another client console?



Thanks.

[Min]

We are currently in the process of building up a framework for our technology for usage on smartphones, which include Blackberry devices. However, this is currently at a very early stage of the development process.

The minimum spec is totally dependant on how much data you want to subscribe to and how fast it updates.

Hope this helps.

[agashi]

If I makes streaming website page with liberator with simple UI (not application version just website page), Can users accessing the web site pages with streaming data throught browser in smartphones (BB & iPhone etc) ? what effects will occur?


Thanks

[Min]

Streaming web pages can be written for an iPhone using the Liberator. In fact some of my colleagues have written test pages that worked equally well on an Android phone too. The Streaming connection recovered pretty well even when moving from a wireless connection to a 3G connection to an Edge connection and so on. The only problem encountered on the iPhone was the fact that when reconnecting, Safari occasionally pops up an alert saying that the page could not be loaded. An option of reloading or closing the browser is presented even though after a few seconds the streaming connection is re-established in the background. Annoyingly the alert cannot be dismissed.

I have asked a couple of my colleagues to post their experiences of using a streaming page on a Blackberry.

[harry]

We didn’t get streaming data working on the blackberry over rttp.
Blackberry has it’s own rudimentary web-browser with widely varying versions
and capabilities across differing phones.

We did however push trade events from a trading datasource to the blackberry
using email delivery (which could be changed to Blackberry push notifications).

These were picked up by a native app (PhoneGap with our modifications) and displayed in an browser
Component embedded in the app.