IMHO - reading some of the forum posts on F3 or EPIX threads - one can get a sense that some folks don't like that CIQ looks different from that of native apps. They end up using the native apps or not using the CIQ stuffs at all.
but at least for the app which I'm developing - the progress bar / the save/discard dialog/menu looks 95% close to native.
I noticed that when using a BehaviorDelegate (which derives from InputDelegate) and you use onKeyPressed, then popView doesn't need to be called to exit the app when the back button is pressed. I assume if you're also using onKeyReleased you might need to call popView, depending on which keys you're handling and whether you return true or false.
I switched to onKey and found myself stuck in the app on my actual watch. It has a touch screen, so I was able to use the palm cover gesture to go back to the watch face. What I found is that I either need to check if the back button was pressed and call popView, or only return true for keys it handles and return false by default for any other to have the system handle the default behavior.
I don't know if these things can be said as general truth. I think it depends very much on your app and mostly on the other relevant callbacks in your delegate (when do they return true/false) and probably many other unknown things.
