Ouch. Particularly on the notification front, this really messes with an existing system.
Even if everything was changed to meet the additional segments in the URL, this part is unsettling:
The URLs will likely change again in the near future with the next round of navigation improvements too.
With notifications, OneSignal for example, the URL sent to from the notification is important as it determines where to go in the app and how to handle the data within it. If the URL it goes to does not match the URL it was sent to, the Data is not retrieved.
So if the notification is sent to http://somedomain.com/home but ends up going to http://somedomain.com/nav/n4/home, then the Data is lost.
Now there may be some ways to handle this - like Changing everything to match this new scheme and then again later when it is ‘improved again’ but come on Ionic - there has got to be a way to turn off this ’ first-class url support’.
I’m hoping this is just a lack of documentation.