gomobile.mobile 0.0.2

Features

Note: GoMobile is still under development. Some of these features might require extra work to be enabled in your configuration.

• Automatically reformat pages and images suitable for mobile consumption.

• Degenerate gracefully when viewing the pages on less powerful mobile phones (other than webkit based browser)

• Manage web and mobile content from the same user interface.

• Mobile phone preview option for pages in the admin interface.

• Categorize site sections belonging to web, mobile or both (gomobile.convergence product)

• Possible to use same URLs for web and mobile content. This way pages are displayed correctly whether the user opens them from his web browser or mobile browser. Very handy for outgoing links in email.

• Big folder navigation and link buttons for touch screen displays to make the mobile site finger friendly.

• Superious handset database support, sourcing information from multiple handset databases.

• Enable and disable site features depending on whether the handset supports them (location based services, downloadable ringtones, downloadable widgets).

• Plone ecosystem has dozens of well maintained add-ons which can be dropped in to your mobile sites: forums, form editors, blogs, ecommerce.

• Built on Plone and Zope component architecture to make the product extensible, configurable and future proof.

• Upload video files and they will be automatically transcoded suitable for different web and mobile platforms (commercial add on service)

Feel it

Please visit Plone community mobile site to see the product in action.

The site achieves near perfect score in mobiReady industry standard test how well pages work across different mobile phones.

Requirements

• Experience or will to learn how to install and maintain Plone sites

• Plone 3.3 or later

Installation

• You need to install Plone CMS first.

127.0.0.1 mobi.localhost web.localhost preview.localhost

# Add additional eggs here
eggs =
        archetypes.schemaextender
        gomobile.imageinfo
        gomobile.mobile
        gomobile.convergence

# These are direct SVN trunk checkouts
develop =
        ../workspace/gomobile/gomobile.imageinfo
        ../workspace/gomobile/gomobile.mobile
        ../workspace/gomobile/gomobile.convergence

# If you want to register ZCML slugs for any packages, list them here.
# e.g. zcml = my.package my.other.package
zcml =
        archetypes.schemaextender
        gomobile.imageinfo
        gomobile.mobile
        gomobile.convergence

Mobile support

The product has been tested with

• iPhone

• Various Nokia Series 40 (non-webkit browsers)

• Various Nokia Series 60 models

• BlackPerry models

• Android

• Opera Mini

Usage

To view web site version, go http://web.localhost.

To view mobile site version, go http://mobi.localhost.

Portlets

The following new portlets are available:

• Mobile preview portlet: render the current page in mobile phone mock up. This generates preview request to the site in pop-up iframe.

• Content medias portlet: allow to choose in which medias the content appears: web, mobile, both or use the parent folder setting.

Sitemap

Sitemap has been enhanced to show content media and content language for the site administrators.

User agent sniffing

To achieve the maximum usability mobile pages must be tailored for each handset individually. This means

• Resizing images suitable for the handset small or big screen resolution

• Serving correct video files depending on the handset support (RTSP, 3G, iPhone MP4 progressive download and such)

• Change link and button sizes depending whether the handset is touchscreen based or keypad based

• Disable site features depending on whether the handset supports them (downloadable map locations, ringtones, wallpapers)

• Use location based information when available

State of the art mobile.sniffer library is used in this project. It is an generic middleware supporting several different handset databases. To make the sniffing more accurate, sniffing can source information from multiple databases once.

Traffic analyzing

Traffic analyzing can be either

• internal: you record page hits your own database

• external: hidden image loaded from the tracker server is used to keep track of the loaded pages and the visitor data is hosted elsewhere

The former is more visitor friendly, since there is no hidden images increasing mobile bandwidth usage. The latter is more easier for the site administrators.

Supported tracking backends:

• SQL and cookie based tracking (not released yet)

• Bango

Performance

archetypes.schemaextender has performance issues.

If this is an issue please install archetypes.schematuning package.

Unit tests

Unit tests are available for all packages.

Roadmap

• gomobile.mobile theme will be rewritten based on plonecommunity.mobi

• Launch GoMobile community in GetPaid fashion

• Recruit sponsors/clients

• Build the best mobile content management system in the world

History

This project started as an internal Twinapex effort and was test-driven on few sites before becoming public. To embrace the open source and make this product a great success we decided to spin off it.

Authors

The project is hosted at Google Code project repository.

Currently project is maintained by`Twinapex Research <http://www.twinapex.com>`_ team and friends. Email: mikko.ohtamaa@twinapex.com.

Twinapex Research - high quality Python and mobile hackers for hire. We have 50+ years of mobile site expertise and 10+ years of Plone expertise.

0.0.1 - 0.0.2

• Migrated to Plone 3.3

• Created plonecommunity.mobi demo site

• Increased mobiready.com score to to near perfect by fixing template quirks: http://plonecommunity.mobi/readiness.png

• Added Bango support

0.0.1

• Source code liberation