MemoryVault is designed to preserve personal memories, photos, videos, and messages for the people who matter most. Because the platform handles personal and sometimes sensitive information, it must do more than work technically. Users must also understand what is happening and feel confident that their memories are being handled safely.
That is why we tested MemoryVault with people from its target audience. During this session, we examined which parts felt natural, where confusion occurred, and how the app could be made clearer and more accessible.
Who tested MemoryVault?
Three older adults and Annemarie Kort from Stichting Sociaal Collectief SWF tested version 1.0.0 of MemoryVault.
Annemarie participated as a target-group expert. Her experience working with older adults meant she could assess the app from her own perspective while also identifying possible barriers for people with different levels of digital experience.
The participants used both mobile phones and a laptop. This allowed us to observe how MemoryVault was experienced across different devices.
What did we want to learn?
During the session, we focused on several questions:
- Do users understand what MemoryVault is?
- Can they navigate through the app independently?
- Is it clear how to add a loved one?
- Can users add a memory without assistance?
- Do they understand the purpose of a trusted contact?
- Does MemoryVault feel safe and trustworthy?
- Which parts cause confusion?
- Would they consider using the app themselves?
The goal was not only to check whether the features worked technically. We mainly wanted to understand how new users experience MemoryVault when they open it for the first time.
How did the testing session work?
At the start of the session, I briefly explained what MemoryVault is and how the test would be conducted. The participants then received several tasks which they were asked to complete as independently as possible.
They first explored the website and tried to understand what MemoryVault does. They then created an account and completed the introduction inside the app.
After that, they were asked to:
- add a loved one;
- add a memory;
- set up a trusted contact;
- explore the app independently;
- identify which parts were clear or unclear.
While the participants completed the tasks, I tried to provide as little assistance as possible. I only stepped in when someone was genuinely unable to continue. This showed which parts were self-explanatory and where additional guidance was needed.
At the end of the session, we discussed their experiences, questions, and suggestions together.
The first impression was positive
The overall first impression of MemoryVault was positive. Participants understood that the app is intended to preserve memories and connect them to loved ones.
Some people immediately clicked through from the website to the app, while others first scrolled through the page to read more information. Both groups were able to get started without major difficulties.
The website and app felt trustworthy. However, participants wanted more information about what MemoryVault does, how their data is handled, and how their memories are protected.
This is particularly important for a platform such as MemoryVault. Users should not only understand which features are available. They should also understand why they can trust the platform.
Navigating the app generally went well
Participants were able to navigate through the main parts of MemoryVault independently. The pages for memories and loved ones were easy to find.
However, there were several elements whose appearance did not match their behaviour. For example, participants expected the dashboard cards showing totals to be clickable. Because these elements looked like buttons, users tried to select them.
Some mobile buttons were also less clear because they only displayed an icon. Adding text beside these icons would make it easier to understand what each action does.
The help button in the bottom-right corner was hardly noticed. The introduction and help system were also not clear enough on mobile devices.
Adding a loved one was straightforward
Adding a loved one worked well. Participants understood what information they needed to enter and completed the process independently.
The session did reveal that this step should appear earlier in the user journey. Some participants began by creating a memory before adding a loved one.
This later caused confusion about groups and about who would receive the memory.
By asking users to add a loved one first, the rest of the app gains more context. It then becomes easier to understand how memories can be connected to individual people or groups.
Groups caused confusion
When creating a memory, users were able to select a group. However, new users did not yet understand what these groups represented.
Participants asked questions such as:
- Who is included in this group?
- What is a group used for?
- Who will receive the memory?
- Do I already need to select a group?
The feature appeared before participants had added enough loved ones for groups to be useful.
One possible improvement is to explain groups more clearly or only show the option after a user has added several loved ones. This prevents new users from being confronted with a feature they do not yet need.
Problems when uploading photos
Several participants encountered problems when uploading a photo. They received a message explaining that the file was too large.
It was not clear to users how large a photo could be or why it was rejected. Participants also asked why MemoryVault did not automatically reduce the image size, as some messaging apps do.
Several improvements can be explored:
- clearly display the maximum file size before uploading;
- provide a more understandable error message;
- increase the maximum file size;
- automatically resize or compress images.
The quality of the original image must also be considered. A photo stored in MemoryVault may have significant emotional value, so users may not want it to be heavily compressed automatically.
Deleting a memory required too many steps
Deleting a memory felt unnecessarily complicated. Participants had to click several times before a memory was actually removed.
A confirmation remains important because users should not accidentally delete a valuable photo or message. However, the process should not become frustrating.
A better solution would be one clear delete action followed by a single confirmation. This still protects the user without adding unnecessary steps.
Trusted contacts were often skipped
Setting up a trusted contact is an important part of MemoryVault. This person helps determine what should happen when the owner of the Vault does not respond for an extended period.
During the session, almost all participants thought they had finished setting up their account even though they had not added a trusted contact. This happened despite warnings being displayed in the app.
When the feature was discussed, participants asked questions such as:
- What exactly does a trusted contact do?
- When does this person receive an email?
- Can a trusted contact view my memories?
- What happens when I do not respond?
- When will my memories be shared?
This showed that a warning alone is not enough. The feature needs a clearer explanation and should become a recognisable part of the initial setup process.
The test also revealed several technical issues. Some emails were still written in English, and accepting an invitation sometimes incorrectly displayed a message saying that the link had expired.
Trust and security
Participants said MemoryVault felt safe and trustworthy. They could imagine using it to preserve notes and photos for their children or other loved ones.
At the same time, they would not immediately store highly valuable or business-related documents in the platform. For those kinds of files, they wanted more information about privacy, storage, and security.
This shows that a trustworthy appearance is important, but it is not enough. Users also want to understand why a service is secure.
MemoryVault should therefore clearly explain:
- how information is stored;
- who can access the information;
- when memories are shared;
- what a trusted contact can and cannot do;
- which security measures are used;
- how much control the user retains.
What already worked well?
Although the session revealed several improvements, it also showed that the foundation of MemoryVault is easy to understand.
Participants:
- understood the general purpose of MemoryVault;
- could navigate through the app independently;
- could easily add a loved one;
- found the visual design trustworthy;
- understood that memories can be preserved for different people;
- said they could imagine using MemoryVault themselves.
The most important improvements therefore do not require completely changing the concept. The focus should be on explaining features more clearly and improving the order in which users encounter them.
Which improvements came from the test?
Several improvements were identified based on the testing session.
A clearer introduction
The website and onboarding should explain more clearly what MemoryVault does, how information is protected, and when memories are shared.
Add a loved one first
New users should add a loved one before creating a memory. This gives groups and recipients an immediate context.
Explain groups more clearly
Groups should receive a clearer explanation or only appear after a user has added several loved ones.
Make trusted contacts more visible
Setting up a trusted contact should become a clear part of the initial setup and should be displayed more prominently on the dashboard.
Improve the mobile experience
Buttons should include text where necessary. The help button, introduction, and mobile navigation also need to become more visible and understandable.
Clearer photo uploads
Users should be able to see the permitted file size before uploading. Error messages should be improved, and options for automatically processing larger images should be investigated.
Fewer steps when deleting
Deleting a memory should become simpler, with one clear confirmation step.
More information about privacy and security
Users should be able to easily find information about how MemoryVault handles their data and what control they retain.
Why testing with real users matters
As the creator of a product, you already know how it is supposed to work. You know where every function is located, why each button exists, and which steps someone is expected to follow.
A new user does not have that knowledge.
During this session, for example, adding a loved one worked well, but groups became confusing when no loved one had been added yet. The trusted-contact feature was present, but users still frequently skipped it.
Insights such as these only become visible when people use the app independently. User testing is therefore not simply a final check. It is an important part of developing MemoryVault.
Continuing to improve MemoryVault together
The session showed that participants understood the basic idea behind MemoryVault and that the app felt trustworthy. At the same time, it became clear where more explanation, guidance, and simplicity are needed.
Combining the experiences of three older adults with the knowledge of a target-group expert helped us evaluate MemoryVault from several perspectives. This means improvements can be based not only on technical decisions, but also on what users actually experience and need.
MemoryVault will continue to develop step by step. This means adding new features, but also making the existing experience clearer, more accessible, and more trustworthy.