Personas and scenarios

Personas

Marieke, 42, parent of two. Manages the family’s contacts. Wants school parents to have her mobile and the children’s birthdays, family to have the home address and everyone’s birthdays including years, and nobody at work to see any of it. Uses an iPhone and an iPad; the family shares a Google account for contacts.

Tom, 35, freelance designer. Has a work phone number, a private number, a business address and a home address. Wants clients (Work circle) to see the work number and business address only, and to switch a client to Friends when they become one. Android phone, Google Contacts.

Opa Henk, 71. Uses an Android tablet with large text. Wants birthdays and addresses of his grandchildren to be right and to be told when something changes. Does not want to learn about “types” and “scopes”; his daughter sets most of it up as a managed profile? No: Henk has his own account, but Marieke can help by adding him as a connection in Family.

Sanne, 16. Has no account. Her mother Marieke keeps a managed profile for her so that family and the parents of Sanne’s friends receive her details. When Sanne turns 18 the profile can be converted to her own account (design keeps profiles.account_id movable; the flow itself is deferred).

Scenarios (used as acceptance walkthroughs)

1. Marieke moves house. She edits the home address in her profile. Family and Friends receive the new address; Work receives nothing because the address is not shared with Work. Opa Henk gets a push notification “Marieke updated her details” and, since he connected his tablet’s contacts, the address in his address book is updated at the next sync. Her managed profile for Sanne also has a home address; she edits that separately (or copies it with one tap: “Same as my home address”).

2. Tom meets a new client. He searches by the client’s e-mail address (the client had made their work e-mail searchable). He sends an invitation with circle Work and no relation. The client accepts and places Tom in their own “Suppliers” circle. Each sees the other’s work details. A year later Tom moves the client to Friends; the client now also sees Tom’s private number, and Tom’s Google Contacts gets the update.

3. Henk gets a new phone. He signs in on the new tablet; all connections, circles and details are there. He connects “Device contacts”, chooses Family only, and the app fills his empty address book with his family’s cards.

4. Marieke connects Google Contacts and cross-references. The app hashes the e-mails and phone numbers of her 300 Google contacts and finds 12 already on Incico; she invites 9 of them in one go, choosing a circle per person. The other 288 stay in the “to invite” bucket; she can hide the ones she does not want to see again.

5. A birthday without the year. Tom shares his birthday’s day and month with Work, and the year only with Family. A colleague’s card shows “14 March”; his sister’s card shows “14 March 1991”.

6. Someone unpleasant. A stranger who knows Tom’s public work e-mail finds him and sends an invitation. Tom declines and blocks. The stranger can no longer find or invite him, and any existing connection is removed.

7. Leaving. Tom deletes his account. His card disappears from all his connections’ contact lists at their next refresh; connected services delete or keep the address-book entries depending on each connection’s “allow delete” setting; his photos are removed from storage; the confirmation e-mail arrives; within 30 days backups no longer contain him.