From bemoko developer wiki

Content Source

Content from a PC Web Site

bemokoLive can transform PC web sites by extracting the appropriate content from the site and using that content to drive the mobile web site.

Example usage:

You have a PC web site and you want to make it ready for mobile.

Advantages:

Low (or zero) impact on the existing PC web site

Limitations:

Overhead on proxying to existing web site and dependent on how fast that web site delivers the pages, although note that non-personalised content can be cached.

Processing of entire web pages, which potentially can have content created by Javascript, is not the most performant way of providing content for a mobile web site.

Content from a Semantically Tuned PC Web Site

If the PC web site follows accessibility best practices and adds semantic information as classes and ids to the markup (cf. Microformats) then it is much easier to extract the appropriate content from the web site to be used in a mobile web site. See Semantically Tuning a PC Web Site for more information.

Example usage:

You have a PC web site and you either have already designed the markup with high accessibility and semantic best practices in mind - or you are able to make these changes to your PC web site.

Advantages:

The use of semantic hooks into your PC web site make it quicker to extract the relevant content and makes the extraction process more robust to changes in the PC web site.

Limitations:

This process still extracts content from a PC web site and, although it may be quicker than a non-semantically tuned way, there are more performant ways to provide content into the mobile web site.

Content from a Data Orientated XML Service

A data orientated XML feed, such as RSS or the Twitter API, provides excellent foundations for driving the content for a mobile web site.

Example usage:

You want a twitter feed on your web site.

Advantages:

Get content from a multitude of both public and protected web service providers.

Limitations:

Not too many - typically XML over HTTP is not as fast a direct API call, but as long as you don't make too many calls for a given page rendering and you cache appropriately, you can make good use of the available content in a highly tuned environment.

Content from a Content Repository

Access to a content repository, RDBMS, CMS or XML files

Example usage:

Deliver content from your CMS

Advantages:

Drive the mobile web site with content managed in your existing CMS

Content from any API

Access to a an existing business function, e.g.

Example usage:

Use an authentication to authenticate a user or a personalisation service to deliver a personalised content

Advantages:

Leverage existing business logic APIs. Think all the benefits of SOA^[1]

References

1. ↑ Service-oriented architecture - http://en.wikipedia.org/wiki/Service-oriented_architecture