Going to the zoo is a fun family activity, but planning for it can be stressful and confusing. This mobile experience helps a visitor to plan their visit beforehand and also provides a good guide while at the zoo.

Tools Used

InVision Studio, Sketch, Pen and Paper


Design an application to plan a visit to the zoo


  • Mobile-first approach
  • The zoo has records of exhibits, events, and other facilities available for the app to access
  • The zoo can update records on the app when needed


Analyze Problem and Establish Assumptions
Key Factors
Information Architecture and User Flow
Interactive Prototype

Initial Analysis


I interviewed three people who had recently visited a zoo in groups, and one zoo employee. I also looked at current zoo apps and websites to explore their advantages and insufficiencies. I used this research to find trends, needs, and goals, and understand the process of planning a zoo visit.


27 years old
Loves to travel, adventurer
Visiting from out of town
Never been to the zoo
42 years old
Mother of 3
Lives in same city as zoo
Regular zoo visitor

  • Last minute planner
  • Curious
  • Tech fan

  • Meticulous planner
  • Anxious
  • Uses minimal technology

  • Visit zoo with friends
  • Plan details on the way to the zoo/at the zoo
  • Try to see as much as they can in the zoo

  • Plan every detail before visiting
  • Have a stress-free visit to the zoo with kids
  • Plan visit in accordance with petting zoo times
  • Make use of zoo kid-friendly amenities and accessibility features

  • Too much to do, too little time
  • Remotely coordinating with friends
  • On a tight budget

  • Kids’ tantrums

Key Factors

Based on the research I conducted, I mapped out the key factors to design for. I arranged the factors based on a typical user journey, starting from planning in advance to actions to be taken while at the zoo.


Taking into consideration the different factors needed to create a useful application, I then began brainstorming different ideas that could be incorporated into this mobile experience.

User Flows

After deciding on the features that this solution should have, I created user flows to map out the different journeys a user could undertake within the app.

Low Fidelity Sketches

These sketches helped me flesh out the details within each screen and the flow between screens.

High Fidelity Designs


The home screen shows recently made itineraries and a selection of popular exhibits.


Users can browse through exhibits and read details about the animals there.


A traditional search experience allows users to search app-wide for exhibits, itineraries, other facilities, etc.

Interactive Map

An interactive map allows users to navigate through the zoo (with or without an itinerary) and filter exhibits and other facilities.

System-generated Itinerary

1: For first timers or those with a time restriction, the system can generate a tailored itinerary.

The system also checks the weather for that day for the user and provides a warning if it isn’t ideal.

2: This itinerary can later be edited by the user too. After saving this itinerary, users can share it via different channels.

User-generated Itinerary

1: Visitors familiar with the zoo and its exhibits can create their own itinerary from scratch.

The system also checks the weather for that day for the user and provides a warning if it isn’t ideal.

2: After adding all the exhibits they want to view and saving this itinerary, users can share it via different channels.

Navigate using Itinerary

Users can access a previously saved itinerary and navigate the route with an in-app map.

Supplementary Resources

A supplementary menu provides other resources related to the zoo like how to get there, parking, petting zoo timings, etc. This information is grouped together under this menu as it is mostly static information that doesn’t need any input from the user.

Interactive Prototype

I took this opportunity to explore the depths of InVision’s new tool, InVision Studio. The link to the prototype is:

Final Thoughts

I conducted some initial informal user testing while designing and prototyping the screens. But this design would require a few more rounds of user testing and iteration to understand better if it is addressing the users’ needs. With more time, I would work on the visual design of the map, syncing it better with the rest of the design. I would also incorporate a more detailed version of ‘planning a visit’ solely through a map interface.

Finally, through this exercise, I got to explore the many features and capabilities of InVision Studio in its early release stage. In the future, I see all-encompassing UI design+prototyping tools becoming more commonplace and with a few more updates I think InVision Studio could be up top there.