What's the best practices/ suggestions for organizing a Product with 3 platforms (Web/ iOS/ Android)
Asked by Ahmed Badran:

I have a Product with 2 platforms, Android, Web, and Mobile.

My goal is to make the roadmap reflect the progress of the feature delivery across the different platforms so stakeholders can view progress without the need to leave JPD to the Delivery Project.

Currently, I use a Field for the Platform and have a board for grouping the ideas by this field.

what's the best for my case?


Answers:
author: Amina Bouabdallah
body: Hi Ahmed,

Per the others on this thread (thank you for your replies!): if the features are different from platform to platform, what you are doing is correct, i.e. create a field called Platform then grouping by it.

To second [@Ivan Ferreira](/t5/user/viewprofilepage/user-id/5209761), definitely make sure that the Jira Software epics is linked to the right JPD idea. Then display the 'Delivery Progress' field in your Jira Product Discovery views.

Best,

Amina


author: Ivan Ferreira
body: Hello [@Ahmed Badran](/t5/user/viewprofilepage/user-id/5376166) . I would do exactly as you are doing for visual representation. If you want to reflect the progress, use the Progress Delivery field.

Basically, you should create an Epic in a Jira Software project, and link the Epic to JPD using the Progress Delivery field.

For more information, visit:

<https://support.atlassian.com/jira-product-discovery/docs/configure-the-delivery-tab/>


author: Antonio Valle _G2_
body: This is very interesting. How do you solve the fact that (probably) the idea will be developed for Android, web \& mobile in the frontend but probably the backend will be the same for those three platforms?


author: YY Brother
body: Platform could be with multiple values for one of the platforms or for both platforms linked to a JPD idea. Can this method meet with your expectation?

comments: author: Ahmed Badran
body: Here's what I want to do   

* Idea/ Feature -\> use a custom field for platform (Web - Mobile ....)
  * Epic for Web Implementation
  * Epic for iOS
  * Epic for Android

to make the idea the parent, and separate the delivery via epics.

is that better than having the same idea duplicated for each platform?

like that:

* \[Web\] Idea/ Feature
* \[iOS\] Idea/ Feature
* \[Android\] Idea/ Feature


author: YY Brother
body: You want 3 ideas corresponding to the 3 platforms? If you can discover or deliver each platform separately, then you can create 3 ideas separately.

If you need take the idea as a whole to discover, then just an idea and split it into three Epics in your software projects.


author: Dani Lanovyi
body: Yes, I am also using the "Platform" field for it + a link type field I called "Dependency" to display any related or blocking work.


author: Ted
body: I might be missing something, but I think you can easily achieve this by using the "filter" function, and then filtering on the platform as relevant.

You can create an additional roadmap and have that one filtered on the field for platform to show only i.e. web and the other roadmap to show only mobile.

Does that solve it for you?

comments: author: Ahmed Badran
body: I'm thinking of two approaches:

* Idea/ Feature -\> use a custom field for platform (Web - Mobile ....)
  * Epic for Web Implementation
  * Epic for iOS
  * Epic for Android

Instead of

* \[Web\] Idea/ Feature
* \[iOS\] Idea/ Feature
* \[Android\] Idea/ Feature

The concern is the main idea delivery status wouldn't be reflected on the roadmap when for example the feature launched for the mobile and is still in progress for the web