With which technologies FlightsMeet is built

3 min read

I have been building FlightsMeet for almost 7 months now and I am planning make my first ever launch in the following weeks.

The first decision I had to make was which programming languages I am going to use, should I use a different language for the frontend and the backend, should I use the same. Should I use a language I am familiar with for the backend.

When I decided I am going to build my first ever product I had to make technical decisions which were new to me as it was the first time I was building a web app. The first questions I had to find answers were the following:

  1. Which language I am going to use for the backend?
  2. Which language and framework I am going to use for the frontend?

    For the first question there were two possible answers, one to use python which I am familiar with and I know I could build something relative quickly, two use Rust which I want to learn but sacrifice speed and efficiency. Looking at those two options the sane answer is obvious, go with python as learning a new language for the frontend is already a big task that will take a lot of my time. Going with two new languages when you want to build a product will be a huge obstacle in the future. We humans don't always make the most logical decisions though, and me as a human I didn't do it this time. I went with Rust because the main reason I decided to do this whole thing from the start was to learn, also I believe in Rust's memory safety and programming model and think that once I learn it, it will be much easier for me to build other products in the future, which will have less bugs. I know this wasn't the right decision and probably if I had gone with python I would have written the backend's first version in much less time than the 2 and something months it took me to write it.

    For the second question I was thinking whether I should go with Javascript or Typescript. Javascript would allow me to iterate a bit faster but Typescript would help me to catch more bugs shipping as it is statically typed. This time I went with speed and chose Javascript, in retrospect I think I should have gone with Typescript. I might migrate (maybe pay for GPT-4 for that) the codebase to Typescript in the future but we all know that this time consuming and probably won't happen, so I will go with Typescript on my next product.

    As for the framework I went with Next JS. I could say that I chose it to deliver a seamless and responsive user experience, but the truth is I chose it because this is what my friend is using.
iparaskev

© 2025