Fliggy App Product Architecture
Reconstructing a travel platform’s hierarchy, task entry points, and information structure from observable interfaces.
- Context
- Product internship assignment
- Role
- Feature inventory, taxonomy, and information architecture
- Scope
- 6 primary modules · Level-one to level-three functions
The project systematically maps observable functions across six primary areas of the Fliggy app: Home, Membership, Messages, Trips, Profile, and Fliggy Qianwen.
Beyond recording buttons
A screen-by-screen inventory can only describe what is visible. This analysis asks what task each entry point serves, and how the platform distributes attention across local recommendations, platform-wide services, content, transactions, trip management, and membership assets.
The Home area is therefore separated into navigation, search, local travel, core services, promotion, and content. Trips are divided into import, planning, memories, recommendations, and subsequent actions.
Evidence boundary
Fliggy Qianwen is mapped only through observable entries such as suggested needs, photo explanation, text input, and voice input. Untested downstream journeys are not invented as deeper functional layers.
Outcome
The final output is a level-one to level-three product architecture with explanatory notes, suitable for both an XMind overview and later report analysis. The real exercise was not maximising the number of categories, but balancing coverage with restraint.