Landing page for WebApp
What It Does
marco po.io is a travel planner that aims to help in optimizing the process that goes into planning any holiday.
Friends and family often use a plethora of resources to plan their holidays, from sourcing their transport options to scouting for potential attractions at a destination. As a result, planning becomes complex and confusing, with people often finding difficulty in agreeing on what, where, and when to fly, what to see and do.
marco_po.io is the solution, which integrates and streamlines the planning process of an entire trip into a single, simple, sleek webapp. From planning your flight, choosing your accommodation, and even looking out for events held in your dream destination, marco_po.io does it all. Once the travel itinerary is completed, a unique hash code can be generated to share with your friends. Your friends can then view the itinerary that you have planned, and vote for their preferred choices.
How We Built It
The front end user interface is built with the support of Bootstrap and Vue.js framework. Every aspect of the program has utilised multiple APIS to help diversify and generalise our search parameters, allowing a truly global webapp.Our backend is designed with NodeJS and Python, with both short term accelerated processing alongside a personalised database to recursively improve upon our services.
What’s Next for marco po.io
marco po.io is planning to adopt machine learning to help calibrate its suggestions of events and options for our long term customers. We also believes in improving user adoption through the creation of a public forum and community whereby users can share their own trip packages, and receive public feedback on their packages. Finally, marco po.io plans to integrate more complimentary technology from potential partner websites such as booking.com, skyscanner.com, and other 3rd party service providers to help streamline the purchase process, and also increase its profitability and worth as a webapp.
Challenges we ran into
There were many APIs that were not available, especially flight data. Also, there were many obstacles with dealing with the server-side communication due to the many fields of information that had to be transmitted to and fro the front-end and the back-end.