A beautiful idea: WebViews

No comments
Given the new paradigm of building Web applications to run natively, problems of how to encapsulate these applications and make them available to users in the form of closed and executable packages comes to the spotlight.

For instance, we do not want our application depending directly from a browser to work or, at least, we want to hide it and show only the final application to the user as if it were just an executable. Still, we want to offer our application on Google Play, Apple Store, etc.

For this, we can use the WebView idea: all of the major SDKs can run web applications in a native view. This solution has as a positive point the fact of being general: we could create a WebView for Android, iOS, Windows Phone, etc. And has as a negative point the fact that an application running inside a WebView is usually slightly slower than an application running in a 100% native environment. The scope of this post will not discuss this later fact: please search for the term "webview performance" on Google in order to find many related discussions.

We can build applications with a WebView following two approaches:
  1. The first one is to build a WebView using a crossplatform technology, therefore, once you construct a WebView code in a certainly environment, you will have it working on all platforms.
  2. The other one is to build a WebView for each of the target platforms: Android, iOS, etc.
We will adopt the second strategy because it requires less code to create a WebView so it will not give us a lot of work. And besides that, we can control all of the customization power that each SDK offers us in order to direct access the functions of each device.

We will limit ourselves in this post to build a WebView only for Android. So... first, using the Android SDK, let's create a main Activity, which is responsible for invoking the WebView Activity:

public class MainActivity extends Activity 

 public void onCreate(Bundle savedInstanceState) 
  final Context context = this;
  Intent intent = new Intent(context, WebViewActivity.class);


This code above creates and start an Activity named WebViewActivity using the Intent object. The WebViewActivity code goes on:

public class WebViewActivity extends Activity 
 private WebView webView;

 public void onCreate(Bundle savedInstanceState) 
  webView = (WebView) findViewById(R.id.webView1);


We have three important concerns about this code:

  • Note that the WebView object was instantiated through the file whose id is “webview1”. This file is omitted here, but is nothing more than the XML representation of the WebView created; it also has other minor settings such as the height and width of the page.
  • Another important point to be mentioned here is the use of "setJavaScriptEnabled " function, which is essential to ensure that the WebView to run JavaScript.
  • Finally, we store the static content of our pages in the "assets" folder. In this example we load the index.html home page (welcome page) available in "cruxsite" folder. Our web content is available entirely in the "assets" folder.

With this we can now compile this code and generate an APK application, which can be distributed in GooglePlay. The source code for this example is here.

Finally, here's a key point to decide. As we are building a native application using a WebView, we can think of hybrid applications, that is: we can merge the native code of Android with the JavaScript functions of the application located in "assets" folder. The philosophy we follow at this moment is to use the form of hybrid application only when you really do not have an HTML5 implementation for the native feature which we are trying to access, note that this gap tends to decrease with time, since the HTML5 is gaining more space on the Web. Thus, we can ensure a more simple, unique and therefore more robust code.

Don’t forget, using WebView is a great idea and tends to be the bridge for running Web applications in a native likely way.

No comments :

Post a Comment