Back to Parent


  • We learned that the many different types of memories often requires different user interface designs. We also managed to navigate the Facebook API and incorporate QuickBlox into our chrome extension to make a working prototype. During this process we realized how complex and personal the entire process needed to be, and we wondered what it would take for the user to express an "emotional response," which is why we worked with different visualizations.
  • Given more time, we would have enjoyed exploring other ways to portray the deleted data, design of the interface, in the context of when and how the memory is chosen and deleted. For example, one idea we had was to be able to associate emotions of different Facebook posts/photos using a physical tracking device, and maybe abstract the memories before they are presented to the user (so that not as many memories are triggered).
  • We were also planning to incorporate a "drag option" which would give the user the ability to send a picture directly into a selected vault as a part of the deletion process. (This would give the user the ability to tangibly drag a digital memory, and give the digital memory some permanence.) We do not only want to develop this feature, we want to go further! We would like to further develop our visualization and possibly animate them, experimenting with which animation is the most impactful and representative of certain emotions and feelings.  We had several other ideas as well and interaction design idea, when considering this project, but due to our limited time we had to find the best short term, most impactful process. Most importantly we wanted to keep the user interaction open and experiment with different digital experiences to make sure that this project has the least amount of restrictions, to maximize creativity.

Content Rating

Is this a good/useful/informative piece of content to include in the project? Have your say!