Collections are a very flexible way of organizing your content in an app.
Here are some use cases for collections:
- create a collection with your articles for the day / the week (more or less like a traditional issue)
- divide your content into different sections, each their own collection, so browse pages can then allow you to go a level deeper to another browse page for a particular section
- publish a catalog with each chapter (or sub-chapter) represented by one or more collections
An article-based app will always start with one initial browse page when the app starts, that will be based on the 'root collection'. The root collection will always have to be present and cannot be deleted.
A collection can be set to open in browse mode, but if you want it to automatically navigate to the first article (content item) in the collection, you can set a preference to show in detail mode. A reader can then browse from article to article in the collection by swiping.
Collections can also be offered as In-App Purchases. In that case, make sure your product identifier matches the one in iTunes Connect and/or Google Play.
Special URL schemes for article-based apps
For a complete overview of the different URL schemes that can be used in an article-based app, please refer to this article.