Topic
  • 1 reply
  • Latest Post - ‏2013-01-20T08:07:41Z by raanan
SystemAdmin
SystemAdmin
2327 Posts

Pinned topic Worklight for static informational sites

‏2013-01-18T08:48:27Z |
all,

i am new to worklight and currently doing proof of concepts to understand the features and strengths of the platform to create mobile web apps, hybrid apps and native apps.

But even after going through a lot of documentation about the platform i am convinced that it doesn't make sense to bring in the complexity of worklight for making the mobile versions of my informational static sites. these sites are better of with HTML5 and CSS3 on htmls (jsp need based) with Content Management System (CMS) at the back end. but i wanted to know the view of the group here.

Will really appreciate your comments/views on this topic.

thanks
~Mb
  • raanan
    raanan
    50 Posts

    Re: Worklight for static informational sites

    ‏2013-01-20T08:07:41Z  
    Hi.

    Even if all you want to do is serve dynamic content form your server to the mobile device there are some advantages to use Worklight, for example by wrapping your site in a hybrid shell you can gain the presence in application stores (Apple iTunes and Google Play).

    You can check "Module 45.1 – Worklight App as a Container For Server Generated Pages" ftp://public.dhe.ibm.com/software/mobile-solutions/worklight/docs/v505/Module_45_1_-_Worklight_App_as_a_Container_for_Server_Generated_Pages.pdf for more information about how to do it.

    If you will not use your static site as the resource of the content but will use the Worklight application you will have a few advantages
    1) Will work offline
    2) Faster response time (no round trips (HTTP requests) to get the whole HTML, CSS, JavaScript, images)

    At the end of the day Worklight application are for applications, where there is a interaction between backends and the client and usage of device capabilities (like location, camera, etc.) and not only static content.