Custom Web App for Flight Scheduling
Budget: €100 – €300 EUR
Flight Scheduling Catalog Web App: I want a web application that lets individual travelers schedule their flights. The core of the project is an info flow—search, filter and select in an interface that renders equally well on desktop and mobile browsers.
Key pieces I need:
• A Catalog architecture (probably search index based), which can handle a lot of flight numbers with respective dates plus shows the respective faceted filters of every selection.
• A responsive front-end that automatically adapts to any screen size
• A backend that fetches route data (From, To, Flight Nr., Flight Data) delivered via CSV.
• MVP, I'm fine with NoCode and SaaS software. No focus on design, just functions.
• The data I provide is flight schedule data, that contains only direct flights in March, April and May. You need to create your own transfer flights (man transfer time 30 minutes, max transfer time. You need data for other periods by copying this data.
• Flight schedule data usually needs to be updated once per month. So the application needs a backend to upload a CSV with flight data that is like the one I provide.
• Sophisticated Filtering. It should not be possible to operate filters, if there is no respective data behind. User should not be able to select something where no data is available.
Take a deep look at the attached screenshot, as it shows:
- Filters (especially the period filters might be a bit tricky). Filters on the left side show all filters we have: Only outward flight / outward + return flight, Only direct flight / direct flights & transfer flights, Departing Country, Departure Airport, Arrival Country, Arrival Airport, Period of first flight (Month, week or day), Period of return flight (month, week or day), airline, Price range shown on the date selection (Pink is expensive, yellow is medium, grey is cheap; to generate (fake) price data, just set the flight duration plus add €100 plus give €10 for the day of the date), the green bar on top of the date shows availability of the flight on that day (Please display the amount of flights on the given day, which is not displayed in the screenshot).
- Search on top of filters will search for Departure Airport, Destination Airport, Departure Country and Departure Airport at the same time. Search should works as a Suggest but also as result.
- Search in the “from to” section has dedicated slots for search from and search to. Here search just searches for either country or airport. This is done very good on flightsfrom.com
- Breadcrumb on Route pages and destination pages, which is actually a combination of filters too. Breadcrumb should support following logic (mix of static and dynamic): Departing Country + Departure Airport + Arrival Country + Arrival Airport. If only Departure or arrival is selected, the other part is ignored and not showed.
Flights from Mallorca: Flüge ab Spanien > Flüge ab Mallorca
Flights to Mallorca: Flüge nach Spanien > Flüge nach Mallorca
Pages: We have two types of page designs.
1. Route pages design: Here we show all flight numbers on a given route. Every result has a start time and and time, flight number and days. We could theoretically use the Route page design everywhere.
2. Aggregated design: Here we show a list of routes and the airlines on a selection which is typically not broken down to Start and Destination Airport. It could be country to country or airport to country As we could theoretically use the Route page design everywhere, there could be a toggle to change design from aggregated to Route design.
- Results on Route pages (which contain different results based on the selection)
1. Direct Flights only outbound or outbound and return
2. Transfer Flights only outbound or outbound and return
- Sorting of the results (Hinflug / Rückflug = outbound / return flight)
- Static URLs need to represent the filters like this:
https://flight-schedule-website.xyz/New-York-JFK/Frankfurt-FRA/ (Airport Codes JFK to FRA)
https://flight-schedule-website.xyz/New-York-JFK/Deutschand-DE (Airport Code JFK to Country Code DE)
https://flight-schedule-website.xyz/Flight-to/Deutschand-DE (No departure selected to Country Code DE)
https://flight-schedule-website.xyz/New-York-JFK/Flight-from (Airport Code JFK to no destination selected)
https://flight-schedule-website.xyz/Deutschland-DE/Airline-LH-Lufthansa (Lufthansa Flights from Deutschland)
- Query parameters of URLs: Return flight, Date outbound, Date return,
Suggestion: https://flight-schedule-website.xyz/New-York-JFK/Flight-from/?type=return&outbound=20261220&return=20261230
- Data: I will provide you with
- CSV, which contains flight schedules. This file is only a sample. The usual monthly data upload is more than 200 MB and is replacing all the existing direct flights.
- A CSV for the airport names and countries
- A CSV with terminals
- A CSV with Airline Codes and Names
I’m comfortable with modern established stacks. Nothing that is too special. A SaaS/no-code approach with API integration would be preferred, but if you have an existing app you adjust, it is also OK.
Send a brief outline of your proposed tech stack, a timeline for each milestone, and examples of a responsive project you’ve delivered.
Key pieces I need:
• A Catalog architecture (probably search index based), which can handle a lot of flight numbers with respective dates plus shows the respective faceted filters of every selection.
• A responsive front-end that automatically adapts to any screen size
• A backend that fetches route data (From, To, Flight Nr., Flight Data) delivered via CSV.
• MVP, I'm fine with NoCode and SaaS software. No focus on design, just functions.
• The data I provide is flight schedule data, that contains only direct flights in March, April and May. You need to create your own transfer flights (man transfer time 30 minutes, max transfer time. You need data for other periods by copying this data.
• Flight schedule data usually needs to be updated once per month. So the application needs a backend to upload a CSV with flight data that is like the one I provide.
• Sophisticated Filtering. It should not be possible to operate filters, if there is no respective data behind. User should not be able to select something where no data is available.
Take a deep look at the attached screenshot, as it shows:
- Filters (especially the period filters might be a bit tricky). Filters on the left side show all filters we have: Only outward flight / outward + return flight, Only direct flight / direct flights & transfer flights, Departing Country, Departure Airport, Arrival Country, Arrival Airport, Period of first flight (Month, week or day), Period of return flight (month, week or day), airline, Price range shown on the date selection (Pink is expensive, yellow is medium, grey is cheap; to generate (fake) price data, just set the flight duration plus add €100 plus give €10 for the day of the date), the green bar on top of the date shows availability of the flight on that day (Please display the amount of flights on the given day, which is not displayed in the screenshot).
- Search on top of filters will search for Departure Airport, Destination Airport, Departure Country and Departure Airport at the same time. Search should works as a Suggest but also as result.
- Search in the “from to” section has dedicated slots for search from and search to. Here search just searches for either country or airport. This is done very good on flightsfrom.com
- Breadcrumb on Route pages and destination pages, which is actually a combination of filters too. Breadcrumb should support following logic (mix of static and dynamic): Departing Country + Departure Airport + Arrival Country + Arrival Airport. If only Departure or arrival is selected, the other part is ignored and not showed.
Flights from Mallorca: Flüge ab Spanien > Flüge ab Mallorca
Flights to Mallorca: Flüge nach Spanien > Flüge nach Mallorca
Pages: We have two types of page designs.
1. Route pages design: Here we show all flight numbers on a given route. Every result has a start time and and time, flight number and days. We could theoretically use the Route page design everywhere.
2. Aggregated design: Here we show a list of routes and the airlines on a selection which is typically not broken down to Start and Destination Airport. It could be country to country or airport to country As we could theoretically use the Route page design everywhere, there could be a toggle to change design from aggregated to Route design.
- Results on Route pages (which contain different results based on the selection)
1. Direct Flights only outbound or outbound and return
2. Transfer Flights only outbound or outbound and return
- Sorting of the results (Hinflug / Rückflug = outbound / return flight)
- Static URLs need to represent the filters like this:
https://flight-schedule-website.xyz/New-York-JFK/Frankfurt-FRA/ (Airport Codes JFK to FRA)
https://flight-schedule-website.xyz/New-York-JFK/Deutschand-DE (Airport Code JFK to Country Code DE)
https://flight-schedule-website.xyz/Flight-to/Deutschand-DE (No departure selected to Country Code DE)
https://flight-schedule-website.xyz/New-York-JFK/Flight-from (Airport Code JFK to no destination selected)
https://flight-schedule-website.xyz/Deutschland-DE/Airline-LH-Lufthansa (Lufthansa Flights from Deutschland)
- Query parameters of URLs: Return flight, Date outbound, Date return,
Suggestion: https://flight-schedule-website.xyz/New-York-JFK/Flight-from/?type=return&outbound=20261220&return=20261230
- Data: I will provide you with
- CSV, which contains flight schedules. This file is only a sample. The usual monthly data upload is more than 200 MB and is replacing all the existing direct flights.
- A CSV for the airport names and countries
- A CSV with terminals
- A CSV with Airline Codes and Names
I’m comfortable with modern established stacks. Nothing that is too special. A SaaS/no-code approach with API integration would be preferred, but if you have an existing app you adjust, it is also OK.
Send a brief outline of your proposed tech stack, a timeline for each milestone, and examples of a responsive project you’ve delivered.