Sorry to hear about your experience with directCanvas thus far. We do support sound (polyphonic even), and touch events are translated right into the directCanvas layer, so there should be no delay. If you are getting jokingly bad performance, that is coming from not optimizing your game for mobile (If your game is lagging the whole device that may also be the reason for your slow touch inputs). I'm not as fluent with Construct 2 as I am other engines, but if you want to debug your DC game, Ken or I would be glad to walk through your code and see what may be going wrong.
If you don't mind me asking, what device and OS version were you testing on?
Thanks for your cooperation, the most important thing is to make appMobi is useful, otherwise appMobi isn't especially for mobile games, just for common apps.
The direct canvas, you may check .capx i've sent to tap you will notice the differences between phone browser and direct Canvas, the annoying issue when you touch screen, it delays the callback, VERY SLOW, also i don't get why directcanvas looks bad sampling image.
Phone browser is still superior than direct Canvas. If is impossible to update as total change, i wouldn't use appMobi again.
I've tested on iOS 6 and iPod Touch 4