Michael, Jesse,
I use the Ionic framework for 'routing' and agree with Jesse that I also dislike the design choice made BUT routing is not simple however it is necessary or indeed crucial.
Unless you have a trivial app (trivial here means only one or two 'pages', rather than not very complex) you need to maintain some sort of routing state and history. Most apps will have more than one or two 'pages' as the screen estate is not very big and so you simply can't get enough information on one screen. I recognise that tablets with 1920x1080 resolution are challenging this notion, however lets forget that for the moment.
Our app (which we thought was quite simple) has
1 A main screen,
2. A tab menu at the bottom for al the screens.
3. A Left side menu off the main screen
4. A right side menu off the main screen
6. Sub-view of the main screen showing details about a specific traffic disruption
7. Sub-view off the main screen showing the picture from a specific traffic camera
8. Another main screen showing a list traffic routes
9. A sub view showing details of a specific traffic route
10. A settings screen.
We also have push notifications coming in, if the push notifications come in whilst we are in the foreground, we simply store them in a the left side menu. If they come in whilst we are in the background, then we have to navigate from ANY of the above 10 screens to the correct screen AND maintain the navigation and history state. Back buttons need to appear correctly. This is not easy and whilst I don't like the notion of URL routing in Ionic, it does work.
I would very strongly suggest that you study the routing for whatever framework you have chosen and put some time in to getting to understand it properly and to making it sure it works otherwise you will confuse your user.
Rob