Polyverse is a mobile product that redefines how Gen Z users explore cities in their fragmented time. By combining a real-time hotspot map with a task-based system, Polyverse helps users quickly discover trending places, plan spontaneous activities, and collect achievements through exploration. The project was designed and developed from research to high-fidelity prototyping, focusing on lowering the barrier to participation while creating a playful and engaging urban experience.

Polyverse was initiated from the observation that Gen Z users often face idle moments in the city without a clear plan. These fragmented periods present an opportunity for spontaneous exploration, yet existing tools rarely support this behavior. The goal of the project is to design a product that transforms such moments into meaningful experiences by lowering the barrier to participation and encouraging playful, real-time discovery.

To define the design direction, I conducted both market research and user research. This process helped me understand existing gaps in the market and uncover user behaviors around fragmented time, ultimately forming the foundation for the product’s design strategy.

1 / Market Research

Many fragmented-time scenarios in daily urban life resemble behaviors seen in travel — moments of waiting, sudden schedule changes, or the need for quick inspiration. To better understand these patterns, I started by analyzing the travel app ecosystem, which highlights how most products emphasize planning and booking while overlooking real-time, lightweight exploration.

I mapped the travel app ecosystem into three phases: before, during, and after the trip. Most platforms—such as Pinterest, Klook, or Tripadvisor—concentrate on inspiration, planning, and sharing. Very few provide support for spontaneous decisions during the trip, which mirrors the gap in fragmented-time exploration for urban life.

After mapping the ecosystem, I conducted a competitive analysis of eight representative platforms. I compared them across dimensions such as core offering, target users, map integration, AI utilization, personalization, and gamification. The findings show that most platforms focus heavily on booking, reviews, or planning. Very few place maps at the center of interaction, and almost none combine real-time hotspot discovery with gamified task systems — leaving a clear gap that defines Polyverse’s opportunity.

The market research revealed three clear problems:
1. Most existing products emphasize planning, booking, or sharing, but provide little support for spontaneous, fragmented-time exploration.
2. Few integrate maps as the core interaction, and almost none combine real-time hotspots with gamified task systems.
3. The shutdown of Zenly left a gap in lightweight, socialized mapping experiences — a demand that continues to grow among Gen Z users.

2 / User Research

To uncover how Gen Z users manage fragmented time and what drives their exploration behavior, I conducted user research combining surveys and interviews. This helped me capture both broad behavioral patterns and deeper personal motivations, forming the foundation for Polyverse.

The survey revealed clear patterns: most users tend to spend short breaks on quick entertainment, but a significant number expressed interest in discovering nearby places or activities. This highlighted both the opportunity to redirect idle time toward exploration and the importance of low-barrier access.

To represent these insights in a tangible way, I created a persona named Danny — a curious and social Gen Z student who often has short breaks between classes and activities. His goals, pain points, and motivations reflect the broader needs uncovered in the research.

Together, the survey and persona revealed that Gen Z users are eager for lightweight, spontaneous ways to turn fragmented time into meaningful exploration. These findings guided the problem definition and shaped the core direction of the design.

3 / Key Insights

The research revealed four key insights. First, both the market and users demand low-barrier and lightweight interactions, as fragmented-time exploration cannot rely on complex planning. Second, there is a clear need for real-time hotspot discovery, especially during short breaks or idle moments. Third, social influence plays a critical role, as users are more motivated to explore when recommendations come from friends or communities. Finally, recognition and achievement systems are essential to sustain engagement, yet they remain largely unsupported in existing solutions.

Based on the market and user research, I defined the core problem that Polyverse needs to address. Existing platforms either focus on planning, booking, or sharing, but rarely support spontaneous exploration in fragmented time. At the same time, Gen Z users expect lightweight, low-barrier interactions, real-time recommendations, and playful mechanisms that keep them engaged.

Problem Statement

How might we help Gen Z users transform fragmented time into meaningful urban exploration through real-time, low-barrier interactions, while sustaining their engagement with social and achievement-driven features?

To move from research insights into concrete design, I first structured the information architecture. This step defined how the product should be organized across its main modules, ensuring that the overall system is intuitive, scalable, and directly aligned with the needs uncovered in research.

Polyverse is organized around four main tabs. City Pulse is the entry point for real-time exploration, where users can browse hotspots on a map or through a feed. Flow functions as a lightweight task manager, allowing activities to be saved, planned, and tracked across three states. Moment offers curated and community content for inspiration and long-term accumulation. Me serves as the personal hub, integrating profiles, Passport achievements, and AI tools.

This architecture connects spontaneous discovery, task execution, content inspiration, and personal recognition into a coherent exploration experience.

To better understand how users interact with Polyverse in real-life contexts, I mapped the user journey. This visualization captures the typical path Gen Z users take when they engage with the product during fragmented time, from their initial motivation to the final sense of achievement.

The journey highlights five key stages — motivation, discovery, decision, action, and reflection — showing how Polyverse connects each step into a seamless exploration experience.

With the research and problem definition in place, I moved into the design process. This stage focused on translating insights into concrete solutions through ideation, iteration, and refinement, ultimately shaping the final experience of Polyverse.

1 / Ideation & Wireframing

To quickly translate ideas into tangible forms, I began with low-fidelity sketches and wireframes. This stage allowed me to explore different layouts and interaction patterns without the distraction of visual details.

2 / Iteration & Prototype

After building the initial wireframes, I moved into iterative prototyping to validate the core interactions and refine the experience. This stage focused on translating early concepts into testable flows, gathering feedback, and improving usability step by step.

Iteration 01: During early prototyping, I found that relying solely on the map view limited efficiency when users needed to make quick decisions. To address this, I introduced a complementary List Mode, allowing users to switch between immersive spatial exploration and fast card-based browsing.

Iteration 02: The Mission system was already represented as a “Current Mission” card on the Explore page, but users still had to switch tabs to view full details. This broke the flow between exploration and task execution. I streamlined this by making the Current Mission card itself clickable, enabling users to continue directly into the full Mission interface from Explore.

3 / Design System

Building on the validated prototypes, I developed high-fidelity designs that refined the visual system and finalized the core interactions. At this stage, the focus was on ensuring clarity and consistency while shaping a distinctive brand identity for Polyverse.

To ensure visual consistency and scalability, I developed a design system that defined the core elements—colors, typography, components, and spacing. This system created a unified language that supported both clarity and flexibility across the product.

4 / IP Character Design

Beyond the core design system, I also created a unique IP character—a New York pigeon styled as a witty urban informant. This character adds personality and storytelling to the product, making the brand more memorable and relatable to users.

5 / Hi-fi Design

Building on the design system, I translated the core user flows into high-fidelity UI screens. These key interfaces showcase how the product comes together—balancing functionality with a clean, engaging visual style tailored for quick, everyday use.

To ensure smooth collaboration between design and engineering, I documented clear specifications, interaction behaviors, and edge case handling for seamless implementation. This section demonstrates how design decisions were translated into actionable handoff materials—bridging visual design with real product development.

My focus was on creating a system that is scalable, consistent, and implementation-ready, so the development team could build with accuracy and speed.

1 / Interaction Specs & States

For every core user flow — including task creation, map interactions, and content publishing — I defined detailed interaction states and micro-behaviors. This covered transitions between active, hover, loading, and completed states, ensuring a clear and intuitive experience across different components. By documenting these specs directly in Figma Dev Mode, I made sure engineers could easily understand how each element should behave, not just how it should look.

2 / Edge & Error States

Beyond ideal flows, I also outlined edge and error scenarios to maintain product reliability under unexpected user actions or network issues. This included empty states, failed submissions, and interrupted map interactions, ensuring the system provides clear guidance and recovery options for users. By addressing these cases early, we reduced ambiguity for engineers and improved the overall UX consistency.

3 / Handoff Notes

All final design deliverables were accompanied by handoff documentation, including component specs, spacing tokens, color variables, and responsive behavior notes. I worked closely with developers to ensure every pixel and interaction had clear references, reducing the need for additional clarifications during development. This process improved handoff efficiency and allowed the engineering team to build faster with fewer rounds of back-and-forth.

To evaluate the effectiveness of the high-fidelity design and uncover potential usability issues, I conducted usability testing with Gen Z participants. The goal was to observe how easily users could navigate key tasks — such as discovering hotspots, adding activities, and tracking progress — and to identify opportunities for refinement.

Case 01: Notification Recommendation

During usability testing, users expressed a common expectation: they wanted the product to provide timely suggestions at the right moments, rather than relying solely on active exploration. Based on this feedback, I introduced an interest- and location-based notification feature, allowing the app to act like a “companion” that proactively recommends nearby places of interest, making the exploration experience more natural and immediate.

Case 02: Automatic Mission Completion

In testing, I observed that users found the manual “check-off” step after completing a mission to be cumbersome and disruptive to their flow. They wanted a smarter and more lightweight way to update their progress. Based on this feedback, I changed the process to automatically mark missions as completed, making the flow smoother and more seamless.

The final outcome brings together all stages of the design process into a cohesive product experience. Polyverse transforms fragmented time into meaningful urban exploration by combining real-time discovery, lightweight task management, inspiring community content, and achievement-driven recognition.

This project was not only about building a functional product but also about refining my design thinking process. From the early low-fidelity iterations, I learned how simple changes—such as introducing a list mode or integrating mission flows directly into the map—could dramatically shift user efficiency and engagement. Through usability testing, I confronted real user pain points and translated feedback into actionable improvements, which guided the hi-fidelity iterations where interface clarity and interaction smoothness became my focus.

Ultimately, Polyverse taught me to balance exploration with structure: creating an experience that feels open and spontaneous, yet grounded in usability and clarity. As a product designer, this journey reinforced the importance of iterative testing, designing with both system logic and emotional resonance in mind, and being willing to reframe solutions when user behavior revealed new insights.