But, in this case I am referring to other areas such as screen names.
Having the ability to Navigate("screenName", ... would be very helpful.
I'm not suggesting people hard code things...just the opposite - continue reading.
For those not getting it and considering a vote on this but not quite sure...consider this scenario.
For maintainability of an App, often you will have actions that you want to turn on and off. Editing and re-publishing is not for the average user. However, having a simple list (say SharePoint) that has App Actions listed in it with the corresponding Screen Name and am Enable/Disable type logic, you can write your App to turn on and off actions in your app.
That's all good until you need to navigate to one of those screens. Since your ScreenName is in the list, it's just text. In order to navigate properly, you have to put a nasty Switch statement in with all the possible options. NOT the best solution for maintainability and repeatability.
Instead of a nasty long switch statement that still needs maintenance - now I can maintain app functionality in SharePoint list and simply have a statement like Navigate(ThisItem.ScreenName, ...
SO...now that you see the value in this, click vote!