Phase 4: Feature Design

This past week, we worked on identifying feature sets, developing an application sitemap, and diagramming the process flows with respect to our personas.


We focused on brainstorming and developing features of our name recognition application. This process forced us to understand our application from the perspective of people. We noted that our application caters to those with ‘weak ties’, hoping to build to stronger ties. Because of this, our use cases and target user pivoted slightly to focus more on the professional environment.

Features applied to both the wearable portion of our solution, as well as the mobile application interactions. We organized features into three categories: critical, nice-to-have, and out-of-scope.

Core Features

  • exchanges information with a handshake
  • shows a name or short description on handshake
  • ability to edit a person’s information and adding context after meeting them
  • hint system that is very discreet, such as Morse code vibrations, or audio whispers via a wearable headset
  • ability to manage a personal list of acquaintances
  • surfaces an acquaintance’s information when in proximity and in a discrete way
  • reduces information shown about a person over time
  • ability to access personal information from social networks Facebook/LinkedIn
  • tracks number of times you have encountered a person
  • ability to view additional details about a person on a larger display
  • tells you if you appear to forget someone’s name all the time

Nice-to-Have Features

  • suggests future connections based on the context of a meeting
  • records the environment context of a meeting (e.g. time, place, event based on calendar)
  • records the affective context of a meeting (e.g. nervousness inferred via heart rate, temperature, and other bio-metrics)
  • ability to sort contacts based on context
  • ability to create contact groups based on type of event (e.g. professional, casual)
  • ability to set notes/tags for incoming contacts (e.g. I set my watch to put the note “dog” on all people I handshake in X amount of hours)
  • ability to block someone from adding you (i.e. refusing their handshake)
  • colorized profiles based on when you met them last

Application Sitemap

After determining the important features that this would need to implement, we began planning out the application sitemap. We realized during our feature design discussions that just using a smart watch or a smart phone individually had a lot of problems, but utilizing both would let us make up for the weaknesses of the individual parts.

We broke our site map into two separate sections, one for the watch and one for the phone:

Smartphone App Sitemap

The phone serves as a place for interactivity and comprehensive information display. This includes standard smartphone app features such as signup, settings, and profile. Additionally we display a list of the user’s connections as well as useful statistics and data visualization.

Smartwatch App Sitemap

The goal of the smart watch is to provide critical information to the user in a non-obtrusive manner. Notifications about nearby people will be pushed to the watch in a way that does not inhibit your ability to check the time. From that notification, the user will be able to view a quick list of nearby people and swipe for more details or suggested talking points.

Process-Flow Diagrams

Getting surprised by an acquaintance:

During a meeting, surface smart talking points:

Registration and onboarding:

Meeting someone for the first time:

Preparing for an event:

Like what you read? Give Brian Liu Xu a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.