Family and consumer apps
Parents and kids vote; each request counts once per family, revenue once per plan.
For consumer apps with shared plans: group members under a family so requests count once per family, revenue is never doubled and parents and kids compare.
Set it up
Send the family as company
Every member’s token carries the same family id. The shared subscription goes on the family, never on each member.
Settings → SSO
{ "id": "u_55", "name": "Maya", "company": { "id": "fam_9", "name": "The Rivera family", "plan": "Family", "mrr": 12, "attributes": { "members": 4, "kids": 2 } }, "attributes": { "role": "kid", "ageBand": "9-12" } }Call them families
Pick Family (or Household) and the dashboard says Families everywhere: navigation, Who asked, insights, Pulse.
Settings → General → Customers
Send roles, not personal data
attributes.role parent or kid lets you split demand by role. For kids, send an id and a first name or nickname; leave out email, photos and exact ages.
Put the board in the app
A modal sheet with the embed URL, signed in, tagged iOS or Android.
https://theyasked.me/embed/northwind?platform=ios&hideHeader=1&token=<sso-token>
What you learn
- Families asking
- Distinct families behind a request, not a pile of individual votes.
- Revenue, once
- A $12 family plan is $12 at stake however many members vote.
- Parents vs kids
- Segment any insight by role.
- Grouping health
- Settings → SSO shows the share of people whose token carried a family.
Who it's for
- Family organisers and chore apps
- Parents and kids on one plan.
- Household finance and streaming
- Shared subscriptions with several profiles.
- Games and communities
- Group by clan or club, even when the product is free.