android - Worklight Foundation V6.2.0 – Flexible application Development -

After reading the Warklett Foundation document on Flexible Application Development ()

I have come to this section:

Easily combine web and basic components in your application

In IBM ® Vertical® Foundation V6.2.0, it is easy to mix web and basic components in your app to allow you to create a hybrid application with any composition with web and basic capabilities. The following enhancements support more flexibility in hybrid app development.

• The architecture of hybrid applications (iOS and Android) now allows you to easily access the original code when the application starts. Before the Vertical Framework is launched, you can add code at the beginning of the application lifecycle, and when there is complete control to start the workflow framework, which is capable of starting it in the background. This flexibility allows you to add a custom splash screen, for example, or to control the default splash screen behavior, and launch an app with a resident screen.

• In addition, you can now navigate between the basics of your app and the web parts, without having to authenticate again, and in any order both native and javascript Can Add WL Client API For example, the following scenario is now possible:

  • Start the application in the Web Watch page, connect to a workaround server, and then log in to access protected resources. You can then switch to a basic view and access the same protected resources without the need to reconstruct.
  • Start the application in a basic page, connect to a workaround server, and then log in to use the secure resources. You can then switch to a web view and access the same protected resources without the need to reconstruct
• A new API has been started, causing you to Easily send action (events) and data between your app's native and web modules. It makes it easy to create applications that combine hybrid and web components, for example:
  • You have an application with a JavaScript communication module and an original presentation layer. You can use the new API to easily send data received at the native level through the communication module, so that you can present it to a user on a basic screen.
  • You can easily trigger using complex basic verbs. Javascript can also call javascript code from the original code without applying the Cordova plugin.
  • Using this API for communication you can easily show original and web components on the same screen.

For further and backward navigation between the original and the web components, no additional programming efforts are required and more applications can provide flexibility. For now, the following scenario is now possible:

• Start the application in the Web Watch page, connect to a workaround server, and then log in to access protected resources. You can then switch to a basic view and access the same protected resources without the need to reconstruct.
• Start the application in a basic page, connect to a workaround server, and then log in to use the secure resources. You can then switch to a web view and access the same protected resources without having to re-certify.

In many instances such examples have been mentioned, where your warkle application will start with an original page but rather than starting with a web page What will be a benefit (s) on starting an application with the original page?

Some examples that come to mind:

1. Speed ​​will be faster than a webwave when a native view controller (in the case of IOS) some load, whatever you want to present to the user as soon as possible .

2. Abilities An original page allows to create end-user experiences that are not yet possible to use web technologies.