Travel application

Project overview

SQUAGO is an app that helps friends organize their trips without any stress and in the easiest way possible.

Decide on dates, destinations, and budget via votes, share your documents for the trip, upload your incredible photos with everyone on your joint trip, and even more.

Tasks
  • Analyze the idea and explore the market of similar products
  • Create site-map and get an understanding of user flow path
  • Create mobile wireframes and build a completely clickable prototype to test the idea and better form the vision
  • Build a design system in Figma with clear guidelines
  • Create a clickable prototype for two roles Host and Member
Tools
Figma
Figma
Solutions
Outcome

As the result of the work with days of brainstorming, prototyping, and testing we have created an innovative travel app design that covers Host and Member needs for organizing their joint trips.

Solutions

Research

At this stage, we conducted competitors analysis, defined functionality for our future MVP, and based on those results created a sitemap to get a better understanding of our product’s flow.

Research

At this stage, we conducted competitors analysis, defined functionality for our future MVP, and based on those results created a sitemap to get a better understanding of our product’s flow.

Research

At this stage, we conducted competitors analysis, defined functionality for our future MVP, and based on those results created a sitemap to get a better understanding of our product’s flow.

Research

At this stage, we conducted competitors analysis, defined functionality for our future MVP, and based on those results created a sitemap to get a better understanding of our product’s flow.

Research

At this stage, we conducted competitors analysis, defined functionality for our future MVP, and based on those results created a sitemap to get a better understanding of our product’s flow.

Prototype

Based on the user flow, we've created wireframes of the main app screens and made them clickable for both host and member roles. It helped us in validating ideas and getting feedback for future design decisions.

Prototype

Based on the user flow, we've created wireframes of the main app screens and made them clickable for both host and member roles. It helped us in validating ideas and getting feedback for future design decisions.

Prototype

Based on the user flow, we've created wireframes of the main app screens and made them clickable for both host and member roles. It helped us in validating ideas and getting feedback for future design decisions.

Prototype

Based on the user flow, we've created wireframes of the main app screens and made them clickable for both host and member roles. It helped us in validating ideas and getting feedback for future design decisions.

Prototype

Based on the user flow, we've created wireframes of the main app screens and made them clickable for both host and member roles. It helped us in validating ideas and getting feedback for future design decisions.

Design System

We started with the foundations and basic design components, during the design process we were growing the system with new components and modules as well as documenting things for other teammates.

Design System

We started with the foundations and basic design components, during the design process we were growing the system with new components and modules as well as documenting things for other teammates.

Design System

We started with the foundations and basic design components, during the design process we were growing the system with new components and modules as well as documenting things for other teammates.

Design System

We started with the foundations and basic design components, during the design process we were growing the system with new components and modules as well as documenting things for other teammates.

Design System

We started with the foundations and basic design components, during the design process we were growing the system with new components and modules as well as documenting things for other teammates.

Role: Host

We've started from the Host user role since its functionality is noticeably larger and created mobile screens for all possible actions and outcomes. We created a clickable Figma prototype to conduct testing.

Role: Host

We've started from the Host user role since its functionality is noticeably larger and created mobile screens for all possible actions and outcomes. We created a clickable Figma prototype to conduct testing.

Role: Host

We've started from the Host user role since its functionality is noticeably larger and created mobile screens for all possible actions and outcomes. We created a clickable Figma prototype to conduct testing.

Role: Host

We've started from the Host user role since its functionality is noticeably larger and created mobile screens for all possible actions and outcomes. We created a clickable Figma prototype to conduct testing.

Role: Host

We've started from the Host user role since its functionality is noticeably larger and created mobile screens for all possible actions and outcomes. We created a clickable Figma prototype to conduct testing.

Mutual screens

There were also some mutual pages in the app, such as “Explore”, “Trips” and “Chats”, so we designed them based on what different roles of users will need to use.

Mutual screens

There were also some mutual pages in the app, such as “Explore”, “Trips” and “Chats”, so we designed them based on what different roles of users will need to use.

Mutual screens

There were also some mutual pages in the app, such as “Explore”, “Trips” and “Chats”, so we designed them based on what different roles of users will need to use.

Mutual screens

There were also some mutual pages in the app, such as “Explore”, “Trips” and “Chats”, so we designed them based on what different roles of users will need to use.

Mutual screens

There were also some mutual pages in the app, such as “Explore”, “Trips” and “Chats”, so we designed them based on what different roles of users will need to use.

Role: Member

At the next stage of the design process, we focused on the Member role. It has lots of similar screens with the Host’s role, but gets less functionality and gives users a different experience to fit their needs.

Role: Member

At the next stage of the design process, we focused on the Member role. It has lots of similar screens with the Host’s role, but gets less functionality and gives users a different experience to fit their needs.

Role: Member

At the next stage of the design process, we focused on the Member role. It has lots of similar screens with the Host’s role, but gets less functionality and gives users a different experience to fit their needs.

Role: Member

At the next stage of the design process, we focused on the Member role. It has lots of similar screens with the Host’s role, but gets less functionality and gives users a different experience to fit their needs.

Role: Member

At the next stage of the design process, we focused on the Member role. It has lots of similar screens with the Host’s role, but gets less functionality and gives users a different experience to fit their needs.

No items found.

Outcome

As the result of the work with days of brainstorming, prototyping, and testing we have created an innovative travel app design that covers Host and Member needs for organizing their joint trips.

Linkedin

Linkedin

More works

Looking for an expert?

Let's discuss how WebFolks can help!

Contact Us
WebFolks logo outline