How do I write angular-ui-router code to ensure maximum compatibility with the new angular router?

For a large application, I have to redesign the navigation and routing concept. As far as I know, the new angular router that was announced for 1.4 (and 2.0) is still not production ready. All the information I found about the new router sounds very primitive, but it seems to be outdated, at least in terms of the API. I'm not sure if I should be using the library in such an early state, no documentation.

So I think we are currently better off using ui-router.

Can I use ui-router angular in a way that can be easily replaced in the future?

Should I work with names and nested views? Can I use states in my templates, or is it better for me to link to a URL? Should I be using abstract states? Which of the ui-router options / patterns should I avoid because they are completely incompatible with the new router component concept?