I was able to get good performance by taking your code and just updating Hammer.JS. You were running a quite old version Hammer.JS - v1.1.3, I updated it to the latest Hammer.JS - v2.0.6. attached is the project and video showing the performance. This was on an MC40 updated to the latest KitKat​

Hi, I am posting the sample app on behalf of Kishore.  He created a sample app to show the touch issues he was having on MC40 and TC70.  I tried it on the TC70 and MC40 and can see it is had to swipe as well.  The complete source is posted here.  , and ​ can you take a look for any tips you can offer Kishore.

Thanks

Sorry for taking it so long. I was bit busy with other activites.

Here is the small code snippet that will help you understand the issue and the logs.

Code :

-----
var hammertime = new Hammer($($element)[0], {});
-------
hammertime.on("gesture", function(e){
   switch(e.gesture.eventType){
   case 'start':
  ontouchstart(e);
   break;
   case 'move':
  ontouchmove(e);
   break;
   case 'end':
  ontouchend(e);
   break;
   default:
   break;
  }
});

--------
function ontouchstart(e){
     console.log("--------touch started-------");
}
function ontouchmove(e){
     console.log("--------touch moved-------");
}

function ontouchend(e){
     console.log("--------touch end-------");
}

      Android logs :

--------touch started-------
--------touch moved-------
--------touch end-------

I'm still dragging but touch end is fired

IOS logs:

--------touch started-------
(45)--------touch moved-------
--------touch end-------

touch moved is keep logging until I left it and touch end is fired

Any help is greatly appreciated.

This sounds to me like the well known 300ms delay problem. You either have to use a framework like Ionic that has this handled, or include a microlibrary like fastclick.js into your application. Basically, the webview is waiting for touch gesturing