Linking to browse page of collection?

No, that wouldn't work. The "navto://relative/parent" is a variation of the Back button, which can either take users back to the page in which they tapped (not swiped) to jump to the current article, or it takes users to the article's browse page. If the parent is a browse page, there's no need to specify "openTo=browsePage." If the parent is an article, an article itself doesn't have a browse page.

I'm not aware of a button that will jump up a level to the article's parent browse page. In iOS apps, swiping from the left side does that automatically (it's an iOS convention).

Te level above the article is always a collection, but we would like to use Content Vew, and not the Browse page on the option "Collection open default". BUT we would like to be able to navigate to the Browse page from all articles.

So if the parent is a collection with Content Vew , would not navto://relative/parent?openTo=browsePage be an option?

The navto://relative/parent link follows the end-users navigation history to bring the user up a level from their current view.

It sounds like you are need some sort of way to trigger the browse page of the current view that is independent of the user's navigation history. Something like showing the browse page as a modal overlay on top of the current article, which you can either close, or tap another article and navigate to it. The viewers don't have that capability.

Then this is something we would like to have :-)

Now I tested this link:

navto://collection/collectionname?openTo=browsePage"

And it is possible with this link to open the browse page of a collection - but not the collection you are inside of. A could trigger it from articles in other collections.

Could a solution be to let us link to our active collection's browse page?

Yes, and that's the feature I mentioned above: Allow links to your current collection's browse page. We would like to add support for that, but there is no way to do it currently.

Neil

Our tests show that "swiping from the left side" is not something that our users intuitively try. (Although once they are taught, it's very nice and easy)

Is there a recommended way to indicate or teach this gesture? (preferably without text since we're working in 13 languages)

Can you still create a one-time "welcome screen" for apps?

Alternatively, is there any approximate timeline for when a button that links to the current collection's browse page might be available?

I read it a few times now and I still don't get it. You mean, that the parent link doesn't go to the parent element in the content structure, but the parent element in navigation history? What is the difference to a back button then?

I would find it just logical if the parent link would follow this structure in the other direction:

http://blogs.adobe.com/digitalpublishing/files/2015/10/Collections-1.png

And this is not the case?

Correct, it follows the navigation history, not the content structure. It can differ if the user uses a bunch of hyperlinks to navigate between articles in the same collection. In that case back would take you through the articles viewed within that collection, and parent would take you up to how you got in the collection in the first place.

Neil