**Background**
The Android team was responsible for the Image Recommendations MVP. Our roadmap included learning from the Growth team's V1 implementation of image recommendations. Now that V1 is complete and the team is exploring section images, the Android team is interested in bringing the Image Recommendations task into the app. We are determining the best course of action for API use and if we should follow the same path as Growth of adding images to articles that do not have images and a separate task for adding images in sections or a system that adds images to articles generally. Before we determine our approach we need to explore APIs.
**Task**
Explore possibility of using GrowthExperiments as a proxy as explained by @kostajh and affirmed by @Bpirkle in task T306349#8311919
**Ideal State**
With 9.2% of logged in users from a 60 day sample making cross platform edits, the solution will ideally honor the following user story:
As an Android device user who completed GrowthExperiments Image Recommendations on Mobile Web, and someone that completes Suggested Edits in the Android app, I would like the progress I've made on the Image Recommendations task to carry over to the Image Recommendations task in the Android app and those contributions to be recognized across platform, so that I can have an accurate representation of how many tasks I've completed for topic areas I care about.
**Acceptable Alternative**
If we can not have parity, the following user story will work:
As an Android device user who completed GrowthExperiments Image Recommendations on Mobile Web, and someone that completes Suggested Edits in the Android app, I want to the Android app image recommendations suggested edits feature to be clearly distinct than the mobile web version, so that I can know when to use the mobile web version and when to use the Android app version.