If you use Productboard to manage what functionality you'll add to each of several platforms (e.g. iOS, Android, web app), screens (e.g. iPad, iPhone), or devices (e.g. Acme Consumer, Acme Pro), you'll want a way to keep track of where each feature will be made available.
In many cases, much of the functionality going to each platform, screen, or device will be the same, with only some deviations that need to be tracked.
In this article:
Little overlap in functionality
In cases where there's less overlap in functionality, it's best to use product entities to distinguish functionalities intended for each platform/screen/device.
If a feature will be delivered to one platform only, it can go into that product.
If it will be delivered to all platforms, add it to a generic product. This is usually better than duplicating the feature, which would then require you to manage both versions in different places.
You can filter your board by hierarchy to only show features that belong to certain platforms.
Significant overlap in functionality
Here it's best to use a custom field to indicate where the feature will be made available. The alternative is to duplicate your features, which becomes confusing quickly if there's no other reason to differentiate between them.
You can filter a board by custom field using the same method outlined in the previous section.
To learn how to create custom fields, see Add custom fields to your boards.
Release schedules
If each platform is on a different release schedule, you can manage this with release groups. This allows you to manage different sets of releases out of the same Productboard workspace.