@adam. With the upgrade to 0.9.21 I had also an issue with ng-click inside a ng-repeat element.
I made a test with:
http://code.ionicframework.com/nightly/js/ionic-angular.js
http://code.ionicframework.com/nightly/js/ionic.js
I tried on iOS simulator and chrome (with emulate touch screen) .
For both, it fixed the touch/click issue.
Thanks 
Touch stuff does seem to be better with this build for me as well. I’m having other issues but I believe they are caused by PhoneGap Build having trouble at the moment.
@adam I too have just tested touches/clicks on the latest version 0.22 alpha and its “fixed” the fact that it now registers taps.
However the performance is extremely slow for page navigation and it actually crashes after a few back-and-forths. Memory increases 20Mb per transition whether its backwards or forwards.
@gregorypratt I’m glad you brought up performance. On my iPhone 5S, there is no performance issue. It works really well. On my iPhone 4S, it is much slower. I was thinking it was just the phone. I don’t really use it much anymore and just assumed the 5S was much faster. However, on an iPad 4th Gen, it is also a bit slower than I remember.
And yes, memory is creeping up quite a bit. On prior releases, I was staying under 35MB generally, now I’m up in the high 50s.
@gregorypratt, @Calendee, thanks for the information on this! We are looking into it this very second. We’ll post more info when we have it. Feel free to keep sharing what you find, it really helps!
I’ve managed to figure out my memory issue. Apologies but I believe it was a custom directive I had on the page.
So current situation is that taps are now being registered and memory is behaving however the performance is what I’d call unresponsive, i.e. all navigational related taps feel like clicks (300ms wait). Again modal and tab tapping seems very fast, its just navigational tapping and response.
Thank you for your efforts on this btw!
Thanks for letting us know and testing out the latest code, all of you have been extremely helpful!
For the navigational related taps, I’d imagine it has to do with the ui-router, and the animations taking place. That’s no excuse though, we’ll keep digging into it and try to speed it up more. If you find anything else please let us know, thanks.
@adam, ionic already created the app for us with his meta tag, and still we have 300ms delay (testing on android 2.3)