Hi Scott! I've raised this question internally for you - someone should be posting back soon.
Any update on this?
What type of contribution is the app-view? If its a Tab style (Profile/Place/Canvas), then you should be able to use clean-urls, and pass any context you want in after the # sign in the URL. You'll need to manage the parsing of that information, but that should be able to get you the ability to load the context.
- When logged in, this will load the place tab, and all the information for that user.
- Does the same as the first, but the view can look at the opener URI and use it pass in a context.
This is much cleaner that some of the OpenSocial internal screens...which really only apply for the inner iframe, where-as this can give you a marketable link to promote and/or use as a callback that is actually shown in the browser.
I know that Nils Heuer does this very well in SmarterPath, so maybe its worth a look =)
This is for a !App. In this case, it doesn't seem to be using clean urls. Any idea if in the context of a !App this is doable?
I'll have a quick look at SmarterPath as well.