A shared recipe keeps its referral context.
Help shared content lead to a coherent product experience.
Where this work fits
A meal-plan template still needs dates, recipes, and progress before a customer can follow it. People also need to find suitable content, save choices, and turn ingredients into a shopping list.
I built referral-link features that kept useful sharing context connected to the destination. The integration had to preserve where a person was going as well as the context of the referral.
Keep referral context with the destination
A simple vegetable soup.
Attach referral context while keeping the destination intact.
Share the content, keep progress personal.
The original plan and a customer’s copy had different jobs. I modeled personal dates and completion separately, checked membership for premium activation, and handled conflicts such as placing two meals in the same slot. Catalogue filters helped narrow the recipes people could choose from.
The skills behind the work
- API contracts
- Keep the meaning and format of information consistent between communicating systems.
- Mobile deep links
- Keep a shared destination connected to the appropriate place in the product.
- Data modeling
- Give different product concepts clear records and relationships so updates have predictable meaning.
Membership gave customers a plan they could start and follow, with saved choices and progress. Recipe ingredients could become a reusable shopping checklist.