Discovering a city through things to do
AlbaPin approaches city discovery through missions and exploration content. The aim is to help users understand what they can explore and what to do next, rather than simply present a list.
Missions are considered alongside proofs and badges to make progress visible. Discovery content becomes a workflow users can follow.
The user-facing features
Cities, missions, proofs, badges and monthly discovery content form the core product areas. Mobile screens present the experience, while the panel supports preparation and editing of content.
A mission description needs to match its completion requirements. When users understand what to do, the content model becomes a meaningful experience.
The roles of mobile, API and panel
PinMobile holds the mobile client, PinWeb the backend API and PinPanel the administration tools. Panel areas cover countries, cities, missions, proofs, users and badges.
This separates content operations from mobile development. Adding content and delivering data to screens have distinct responsibilities while sharing the same product model.
Content is part of the product
A discovery app's quality depends on more than interface design. Clear, maintained content and understandable mission instructions also shape the experience.
AlbaPin addresses this through three parts: mobile presents the experience, the API carries data and the panel manages content. Together they support the discovery flow.