A relationship map that shows a contact book as a network
- Year
- 2026
- Role
- Product · Architecture · Interface
- Stack
- Flutter · Python · FastAPI · PostgreSQL
- 6relationship types
- 10industry filters
- 2graph layouts
Figures counted at source, August 2026.
The problem
An address book tells you who you know; it does not tell you how to reach someone. A contact list is flat, but a network is a graph: the person in between, the shared acquaintance, the two-step path. That information usually lives nowhere but in someone's head — and while it stays there it cannot be searched.
Approach
The contact book is modelled as a network rather than a list: people are nodes, relationships are edges, and every edge carries both a type and a strength. The interface keeps that duality — cards to read, a graph to navigate.
- Network map with force and radial layouts, zoom, and colour by industry
- Path finding: deriving the chain of connections between two people
- Six relationship types: knows, worked with, friends, family, mentor/mentee, business partners
- Four relationship strengths: acquaintance, colleague, mentor, close
- Follow-up surfacing for people who have gone uncontacted
- Filtering across ten industries and location tags
- Natural-language search: an optional layer that opens when an OpenAI key is configured
Outcome
A working interface: hundreds of connections across a sample set, navigable by six relationship types and two layout algorithms. The claim is not how many people it holds but that treating a contact book as a network turns "who do I go through to reach this person" into a question with an answer.
The application is not currently deployed: it is not in a store and not live at an address. What is described here is a working build and the decisions behind it.
Building something?
Say what you want built; a written proposal follows within two business days.