In a mobile browser there is a 300ms delay when clicking something before the actual event fires. The rational behind this is that the browser have to wait and see of you did a double tap. 300ms is a noticable delay and it make your app feel sluggish if you don't do anything about it. A common way to deal with this is to create a custom 'tap' event which is fired as soon as the finger is lifted from the screen (we use hammer.js tap these days).
As I already mentioned previously I've been working on a hybrid webapp (one part native mobile, on part HTML/JS/CSS). We are lucky to only be targeting iOS 6+, Android 4+ and Windows Phone 8+. While mobile browsers on these platforms are quite capabable they sure come with a few quirks that we have had to workaround.
I've been quite surprised how well the Windows Phone browser control (Mobile IE10 that is) has been working. There are a few problems of course, one thing we noticed that `MSPointerDown` and `MSPointerUp` events has wrong target (the event.target property).
I've been playing around with a pattern in javascript that would enable private/protected members. While there are many patterns that enable this all come with a different set of forces. Here are some: