Users would be interested in a visual, emotional trip summary and be motivated to share it.

Verdict: partially confirmed. Interest in a personal summary was clear, but sharing was not the main value for everyone.

• All 3 participants save trip materials and return to them. They value the summary as a personal archive.
• 2 of 3 reacted positively to well-made automatic collections. One said random or blurry frames spoil them. The third valued a structured summary and a convenient archive.
• All 3 want control before sending, through preview, editing, hiding personal details or choosing what to share.
• Sharing habits differ: one participant rarely posts memories publicly, one shares only part of a trip, and one wants to send individual blocks.
• One participant said they like an overview that isn’t too long.
• Personal achievements and statistics got no repeated request, so there is not enough data to treat them as central.

A pattern summary built from the 3 discovery interviews. It is not a description of one real person.

I designed an interactive Figma prototype of the Travel Summary sharing flow. The discovery findings informed it, including Preview, Edit and Privacy. This is the prototype I tested with participants.

• An entry block on the Yandex Travel home screen announcing that the results are ready
• A summary screen with cards for expenses, visited places, trip moments, transport and route
• Editing, with privacy toggles
• A preview
• Sharing through the standard iOS share menu, then a confirmation

1Existing product context

Home screen, existing Yandex Travel

My design decision: the “Итоги готовы” card.

The Yandex Travel home screen as it already exists; I did not redesign it. My design decision is the “Итоги готовы” (Results ready) card in the Cities row, which opens the Travel Summary.

Discovery connection: participants returned to past trips and wanted a quick way back to them.

2My design

Trip summary: “Ваше путешествие готово!”

The generated summary: expenses, number of places, photos and video, duration, transport and route. “Настроить итоги” (Customise summary) leads to editing; “Поделиться” (Share) goes straight to sharing.

Discovery connection: participants wanted a beautiful summary without long manual work.

3My design

Transport tab

Distance by transport type (plane, taxi, metro, walking, bus) with a total of 59 movements. The “Места” (Places) tab sits beside it.

Usability connection: distance labels and route information needed clarification.

4My design

Visited places

Photos and videos for the trip, filtered by “Все / Фото / Видео” (All / Photo / Video) and shown under date-range headings, with a “+20” tile for the rest of each group.

Usability connection: two participants also wanted photos grouped by day or location in the Trip Moments section.

5My design

Edit with privacy settings

The “Редактирование” (Edit) tab. “Настройки приватности” (Privacy settings) has one toggle each for expenses, dates, route and exact locations, with the hint “Switch on the data the recipient will see.” Here all four are on.

Discovery connection: participants wanted control over what another person sees; Edit and Privacy came from that.

6My design

Preview

The “Предпросмотр” (Preview) tab, labelled “This is how the recipient will see your summary.” It is the last check before “Поделиться” (Share).

Usability connection: this is where, in 3 of 4 sessions, data that participants had hidden still appeared. See the central finding below.

7Standard iOS component

iOS share menu

After “Поделиться” the standard iOS share menu opens, with contacts and apps. Its names, title and contacts are sample content from the iOS component, not real data.

Discovery connection: participants shared through messengers and the native share menu.

8My design

Confirmation

“Успешно” (Success): “Ваши воспоминания успешно отправлены” (Your memories have been sent successfully), with a “Готово” (Done) button that closes the flow.

• The main flow works. All 4 participants completed the sharing flow. They found the main sections, returned to the overview, found editing and privacy settings, and chose a sending method without serious difficulty. Where manual expense entry was tested, 3 of 3 participants understood how it works.
• Distance labels and numbers needed clarification. One participant read “500 km” as the distance to a single place, not the total. One participant didn’t immediately understand the places count. For three participants, their understanding of the distances shown next to each transport type could not be confirmed and needed clarification.
• Route: Route discovery was confirmed in two sessions; evidence from the other two was insufficient.
• Photos: two participants wanted photos grouped, one by place and one by day and place.
• Single comments: one participant said they wouldn’t realistically enter every expense during a trip, and one wanted to add restaurants and natural places manually.

These suggestions are based on the observations above. They have not been implemented or retested.