I personally think you can do 100% of the nav in the web. The problem is there legitimately weren't native-style navigation tools in web until recently.
Unfortunately, the standard linear history doesn't work for apps that run in a native container. You'll often be managing three or more concurrent navigation stacks (for a 3 tabbed app, for example), and the concept of a browser back button just doesn't make sense in an app like that.
So we've built a lot of that with Ionic. Perhaps at the expense of the mobile web browser app experience.
Don't get me wrong, I'm loving the experience so far and my "simple" comment refers to my skill level.
I did have a couple issues finding answers. Since you've commented, I'll post a couple here but I'll try to add them to the forum.
* Setting webviewbounce, UIWebViewBounce to false in the config.xml doesn't get respected by the framework. You have to manually add the attribute has-bouncing="false" to the ion-content tags to stop the bouncing.
* The helper ionic.Platform.fullScreen(); to hide the status bar initially flickers on first load of a fresh build. I'm currently trying to figure out how to hide the status bar on initial build. http://stackoverflow.com/questions/23553220/how-to-completel...
* I was a little confused using ui-view vs. ion-view. (I think)
WebView bouncing is a vague term and I'm not exactly sure which you are referring to. If you're talking about the entire frame, it's now "DisallowOverscroll" in the Cordova config. If you use the ionic utility you'll get the correct config for a new project.
The issue with the status bar is even using that plugin (which I have working now thanks to the forums) there is a flicker on initial load of the app when it hides. Still can't figure out how to get rid of that.
Thank you for your work on Ionic! I have been using it the last few weeks and really like it. I think the navigation performs well. Honestly, outside of a few minor bugs that got fixed in the last release, the only real problem I have had with it has been learning Angular. But, that will come with work.
I personally think you can do 100% of the nav in the web. The problem is there legitimately weren't native-style navigation tools in web until recently.
Unfortunately, the standard linear history doesn't work for apps that run in a native container. You'll often be managing three or more concurrent navigation stacks (for a 3 tabbed app, for example), and the concept of a browser back button just doesn't make sense in an app like that.
So we've built a lot of that with Ionic. Perhaps at the expense of the mobile web browser app experience.