We had an app working on Ionic 2 Beta 6 using the @RouteConfig example as described here: http://blog.ng-book.com/basic-routing-in-angular-2/. The resulting URL’s had the hash-style routing such as http://myserver.com/index.html/#/route.
We just updated to Ionic 2 Beta 7, which includes NG 2 RC1, which has changed routing significantly and moved the @RouteConfig to a different library (deprecated router).
We’re on a similar time frame of deploying an Ionic 2 app as a web-based application and so looking forward to figuring this out. I’ll let you know as we have an example that we can share.
One of the significant changes with routing seems to be the LocationStrategy and whether to take an HTML5 approach (fine for IE11 and higher) or a hash location strategy. This thread has some useful background: Ionic2 and routing and hotlinking.
Angular seems to be recommending HTML5 approach to allow for server-side rendering (e.g. through Angular Universal / NodeJS), as the hash strategy only works once the user has downloaded the app. Even using the “Ionic build --release” approach, we’re still seeing app bundles of 1.4MB, which seems pretty heavy. Getting Ionic 2 to work with Angular Universal is another area that seems important for using Ionic 2 in a Progressive Web App scenario.