The story behind the product · 3 min read
Not just a list of places, but a reason to explore.
City exploration starts with content and continues through missions, proofs, cards and social interaction. Mobile, API and panel carry distinct responsibilities.
01 / Experience
From a mission to a city experience
Explore a place
Country, city and mission screens shape exploration. Maps and visits connect the route to personal history.
Show progress
Proof uploads, history, badges and rankings make exploration trackable.
Connect
Feeds, messaging, cards and notifications create a social layer, accompanied by blocking and reporting flows.
02 / Product structure
What sits behind the screen?
These areas support one experience through different responsibilities, keeping the user-facing flow simpler.
Mobile
Exploration, missions, maps and social screens.
API
Content, proof, message, social and moderation routes.
Panel
Cities, missions, users and card administration.
Content model
Countries, cities, badges and progress.
For the technically curious: code and architecture
The React Native client is organized with an Express/MySQL API and PHP panel. API commits add cards, messages, notifications and social models; mobile history adds password reset, messaging, blocking and reporting. Content operations are distinct from screen development.
03 / Commercial structure
Commercial model and implemented boundaries.
The inspected mobile dependencies do not show an ad or purchase SDK. Cards and social features are product scope, not evidence of paid cards, subscriptions or advertising sales.
04 / Publishing & growth
How does the product reach its audience?
The product record supplies store identity and visuals. Icon and native publishing identity work appear in history. City exploration, missions and badges anchor the presentation, with moderation included as part of the social experience.
05 / Development
From one idea to a product flow.
Initial content structures grow into card/message models, chat, password reset and safety flows. Travel-card administration also evolves. The work makes exploration manageable and interactive rather than simply adding more cities.
Based on reviewed local source, available Git messages and product records. Development features may differ from the store version; where available, screenshots come from the existing store presentation; module cards are explanatory diagrams.