What does the UI for the “Recap Reel” feature I added to my travel companion app look like?

Why Read This from an HCI Perspective

This post shows real user feedback surrounding the UI of a playback feature that automatically summarizes travel moments. For HCI practitioners, it’s a useful case for examining how information structure, operability, and terminology choices affect initial adoption. In particular, it’s meaningful to review UX design and evaluation perspectives together, because user experience is shaped not just by the appeal of the feature itself, but by “discoverability” and “learning cost.”

CIT's Commentary

From a CIT perspective, the key in this case is not the “usefulness of the feature,” but the “readability of the structure.” The concept of a recap reel is certainly compelling, but as commenters point out, if export, the timeline, editing cues, and tab states are mixed within a single screen without a clear hierarchy, users can easily miss what they should do first. Especially on mobile, the flow of attention and the path of hand movement need to align; if interaction points are scattered across the left, right, and center, cognitive load rises sharply. Also, video terms like “pan” may be precise for creators, but they don’t imply actions for users, so it’s better to replace them with task-oriented wording. This feature should be designed as an auxiliary function that users will use when it’s available, taking into account discoverability, selective use, and step-by-step learning.

Questions to Consider While Reading

• Q.How can we design the information structure at the feature’s first entry point so users understand as quickly as possible what they can do?
• Q.What would be an appropriate approach for progressive disclosure that increases the discoverability of editing features while still not feeling complex to beginner users?
• Q.When domain terminology (e.g., ‘pan’) conflicts with user-action terminology, what criteria should be used to decide labels and instructional copy?