Designing KidLinks: Connecting with the Parents of Your Kids' Friends

Discover

The problem appears at birthday-party speed.

The spark was simple: inviting kids to my child's birthday party, while realizing that I did not have all the parent contact info. Some kids were from playdates, some from last year's class, and others were new friends I had only heard about at the dinner table.

I could visualize the web of adults around these kids: parents saved as “Ivy's friend Sam's Dad,” parents connected through old classroom lists, and families that had not quite exchanged contact information yet.

Define

A lightweight relationship layer, not a new network.

The core user is any parent trying to navigate third-hand connections: parent to kid, kid to friend, friend to parent. The job is not to build a social graph for its own sake. It is to help a parent answer, “How do I know this person, and how can I contact them?”

• Keep the app simple enough to use during real parent life.
• Avoid accounts and heavy contact permissions.
• Make unknown information representable instead of blocking entry.
• Hand off to the phone's default contact app once the right person is found.

Develop

The alternatives were either too ad hoc or too heavy.

Today, parents often solve this with notes in their contacts app, hacked company fields, names like “Ivy's friend Sam's Dad,” or memory. I considered writing KidLinks data directly into contact notes, but that would require more permissions and would be less flexible.

School directories used to fill some of this space, but they are less common now. Facebook can technically connect adults, but it carries too much social baggage for a quick, practical parent-to-parent connection.

• Relationship-first, not contact-first.
• Support the dinner-table clue before the full contact record exists.
• Remember how we know someone without creating a dossier.