As a platform PM,
I need to capture solutions discussed,
So we can estimate required effort and ensure our solution meets stakeholder needs.
public-facing API for image suggestions data
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | • sdkim | T289582 <Path to Production> Image Suggestions POC | |||
| Resolved | sbassett | T294362 Image Suggestions POC Deprecation & Plan for Production | |||
| Open | None | T340453 [Epic] FY 2023-24 Growth Maintenance Work | |||
| Stalled | None | T314144 Remove MVP image recommendation provider code | |||
| Open | None | T306349 Public-facing API for querying image suggestion recommendations and submitting user feedback | |||
| Resolved | VirginiaPoundstone | T321622 Define scope and requirements for public-facing API for image suggestions data |
Read through all phab, slack, and meeting notes conversations. Consolidated the information in a table at the end of image suggestions meeting notes
Hope that we have come full circle to the original scope of a GET stand alone API on the API Gateway.
Also started the imageSuggestoins_Public Playbook and strategy map
I drafted a imageSuggestions_public API Product Requirements Document that is ready for review by @BPirkle.
I did a back of the napkin timeline estimation which landed us at an end of March launch without instrumentation. Would love to gut check that with you.
Let me know if I missed anything.
This is now deprioritized based on alternate solution T320739: Provide API module in GrowthExperiments to allow querying image suggestion API for titles that meets Android team's timeline and API Platform team's current capacity.