# Lessons learned from PhoneGap (Cordova) and jQueryMobile on Android

I recently created my first Android app – JustTodo. This is a simple app but took considerable time to finish due many unexpected problems. Google wasn’t too helpful either. Here is a list of issues I faced and their solutions I discovered.

# General tips

## Zooming and Scaling

I presume that you have already encountered suggestions over the net that you should use meta tag in your html page. So, that your page is scaled to, maybe, take the exact device width. For example you may use…

<meta name="viewport" content="width=device-width, initial-scale=1.0">


width=device-width will make sure that your page’s width is equal to the device’s width. Of course, for any device, the width differs based on if it is in landscape or portrait orientation.

initial-scale=1 will hint the mobile browser to not zoom out the pages. Mobile browsers typically zoom out the whole page when it is initially loaded, so that the whole page fits on the screen. This way the user can tap anywhere to zoom into that exact location. You do not want that to happen to your apps.

However, in spite of the above setting, the browser may still scale your page. This is because a web page designed for iPhone 3G will look half its size on iPhone 5, since iPhone 5 has twice the pixel density. To prevent the webpages from breaking on high DPI devices, the devices usually scale them by a fixed percent to make them look like they would on MDPI (Medium Dots Per Inch) devices. Webpages can read the value of window.devicePixelRatio to know the factor by which they have been scaled. This is 1 for MDPI devices.

# jQueryMobile tips

## Do not minify jqm structure css!

I don’t know the reason or the root cause for this. When I use the jquery.mobile.structure css minified by Yahoo UI compressor, the fixed header stops resizing on orientation change! The solution is simple. Always use the official minified version.

## tap event gets fired when swipe is fired

If on an element if you are listenning for both tap and swipe events, then it would be better to replace tap by vclick. This is because tap is fired before swipe. However, in case of vclick, it waits for about 200 – 300ms to check if any other event is fired. If not then it fires that. This way you can prevent user accidentally clicking an element while trying to swipe it.

## Better swipe event detection

Jqm sets swipe horizontal distance threshold to 30px and time threshold to 1s. Which means to successfully swipe an element the user needs to drag his finger at least 30px horizontally within 1s. I usually set the time threshold to 2.5s. However, due to scaling on high density bigger phones and tablets the physical distance covered by 30px on a MDPI and a XHDPI might vary by a lot. This would force the users to drag their fingers for longer distance in the same duration. So, the trick is to change the distance threshold, such that it covers the same physical distance on all devices.

I wrote the following Javascript function for that.

function getLenInCurrDevice(len) {
var refernecDPI = 192.2960680247461, // Ref device is Sony Xperia Mini Pro - SK17i.
pRatio = window.devicePixelRatio, // Ratio of current device DPI on a square inch to that of a MDPI.
currDPI = refernecDPI * Math.sqrt(pRatio),
originalWInInch = len / refernecDPI;
return (originalWInInch / pRatio) * currDPI;
}


For a given distance in px the above function will return a new distance in px on the current device, such that, the distances cover the same physcial length on the current and the reference devices. In this case the reference device is Sony Xperia Mini Pro Sk17i, which has DPI of about 192.3 and devicePixelRatio of 1.

If you want to accurately calculate the DPI of your device you can use the DPI Calculator here.

# Cordova tips

## Caution when using Proguard

Build files created for an Android project which allows you to enable Proguard on your project. Proguard analysis the Java files and removes all which are not used. However, it also strips out the Cordova plugin classes, since it does see them referenced in any Java classes. (They are referenced from the cordova.js file.) So, you need to add the following to your Proguard config.

-keep class org.apache.cordova.** { *; }


## Minimum plugins needed

This is not documented anywhere and it seems the minimum plugins needed are – App and Device. Frankly, I did not try removing them ever. So, maybe even they too are needed. Just try it and let me know. 😉

Although I must mention that if you remove NetworkStatus plugin then occasionally you might see error related to that in the console. Other than that there is no adverse effect of that. In my app I have kept this disabled, so that I can create an app which requires no special permissions. 🙂

## Remove junk files and folders

Be sure to delete assets/www/res, assets/www/specs and assets/www/specs.html files and folders. The first one might be about 7MB! Actually the only file needed is cordova.js and the cordova.jar file.

## Show native Android context menu

In JustTodo the user when long presses an item in the list it programmatically shows the context menu from the JS. There are two parts to this problem. First is adding the code which allows the JS to open the context menu. Second is to prevent WebView from automatically opening the context menu. More on this later.

First step is creating the context menu xml. Below is an example.

res/menu/example_ctx_menu.xml. The xml’s name can be of your choosing.

<?xml version="1.0" encoding="utf-8"?>
<item android:id="@+id/edit"
android:title="@string/edit"/>
<item android:id="@+id/delete"
android:title="@string/delete" />


res/values/strings.xml. This maps the key we used in menu xml to the actual string which is displayed to the user.

<?xml version='1.0' encoding='utf-8'?>
<resources>
<string name="edit">Edit</string>
<string name="delete">Delete</string>
</resources>


The official way we should be implementing this is using Cordova Plugins. However, I find the technique described here to be simpler. You be your best judge.

NativeContextMenu.java

public class NativeContextMenu {
private WebView mAppView;
private DroidGap mGap;

public NativeContextMenu(DroidGap gap, WebView view) {
mAppView = view;
mGap = gap;
}

@JavascriptInterface
@Override
public void run() {
}
});
}

private void raiseJSEvent(String event) {
mGap.sendJavascript("$(document).trigger('" + event + "');"); } boolean onContextItemSelected(MenuItem item) { switch (item.getItemId()) { case R.id.edit: raiseJSEvent("menu.item.edit"); return true; case R.id.delete: raiseJSEvent("menu.item.delete"); return true; } return false; } void onCreateContextMenu(ContextMenu menu, View v, ContextMenuInfo menuInfo) { mGap.getMenuInflater().inflate(R.menu.todo_ctxmenu, menu); raiseJSEvent("menu.opened"); } void onContextMenuClosed(Menu menu) { raiseJSEvent("menu.closed"); } }  YourCordovaActivity.java public class YourCordovaActivity extends DroidGap { private NativeContextMenu ctxMenu; @Override public void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); super.loadUrl(Config.getStartUrl()); ctxMenu = new NativeContextMenu(this, appView); appView.addJavascriptInterface(ctxMenu, "ContextMenu"); } @Override public boolean onContextItemSelected(MenuItem item) { return ctxMenu.onContextItemSelected(item) ? true : super.onContextItemSelected(item); } @Override public void onContextMenuClosed(Menu menu) { super.onContextMenuClosed(menu); ctxMenu.onContextMenuClosed(menu); } @Override public void onCreateContextMenu(ContextMenu menu, View v, ContextMenuInfo menuInfo) { super.onCreateContextMenu(menu, v, menuInfo); ctxMenu.onCreateContextMenu(menu, v, menuInfo); } }  Now ContextMenu.showCtxMenu() would be available to you in Javascript. example.js $('element').on('taphold', function  () { // taphold event is defined by jqm
// Also the user will get a haptic feedback.
});

$(document).on('menu.item.edit', function () { console.log('Edit option was selected.'); });  ### Preventing WebView from automatically opening the context menu The big problem you will face here that when you long press, the context menu will open twice. One by your call in JS code, and another by WebView. WebView has a method setLongClickable() which even if you set after calling registerForContextMenu() does not seem to have any effect. WebView directly calls performLongClick() without checking if isLongClickable(). So the other way to do this is make NativeContextMenu also implement OnLongClickListener. Changed codes. NativeContextMenu.java public class NativeContextMenu implements OnLongClickListener { // <--- private WebView mAppView; private DroidGap mGap; public NativeContextMenu(DroidGap gap, WebView view) { mAppView = view; mGap = gap; mGap.registerForContextMenu(mAppView); mAppView.setOnLongClickListener(this); // <--- } @JavascriptInterface public void showCtxMenu() { mGap.runOnUiThread(new Runnable() { @Override public void run() { mGap.openContextMenu(mAppView); } }); } private void raiseJSEvent(String event) { mGap.sendJavascript("$(document).trigger('" + event + "');");
}

switch (item.getItemId()) {
case R.id.edit:
return true;
case R.id.delete:
return true;
}
return false;
}

}

}

@Override
public boolean onLongClick(View v) {  //<---
return true; // We return true, to let performLongClick() know that we handled the long press.
}
}


The only side effect of the above code is that whenever the user long presses and you do not show a context menu, the user will still get the haptic feedback. The only way to circumvent that is by sub-classing CordovaWebView and overriding performLongClick().

5 Responses to “Lessons learned from PhoneGap (Cordova) and jQueryMobile on Android”
1. Purusothaman says:

Dear Bro,

Hope you doing good.

I am just starting with Cordova/Phonegap.

I am just trying to create menus in my app.. would you point me to a simple and easy cordova way of doing it?

I saw that you explained about menu in this post.. As you have done Android specific ways, will that work when I build to other platforms using Adobe Phonegap build?

• Android specific won’t port to other platforms, since they are Android specific. I find it easier to directly create native apps when you intend to make your app look and behave like native ones.

Anyway to answer your question, if portability is your main concern then you should create a div with li tags and style it like a menu. There are thousands of tuts which describe how to create menu in html. You can now use Cordova APIs to present your custom HTML menu when the user presses the menu hard key on the phone.

2. Purusothaman says:

Hi,

Thanks for response.

Do you mean “menubutton” event of cordova/phonegap? If so as per the document, this event works only for Android.

Any other idea? Or I am wrong? If so please point me to the correct document.

3. The “menubutton” is ofcourse an Android feature since iPhones or iPads do not have menu buttons. My point was that you could create a HTML menu and (if you want) you can also trigger it from Android’s menu button.

4. Atul says:

Hi Nirupam ,

I have created a chat application using cordova + ionic + angular. Now i have list of messages, i need a context menu for each messages like in whatsapp on long press of messages. i tried https://github.com/mwbrooks/cordova-plugin-menu but having some installation issue. Please guide me on this.