Hello everyone.

This semester at uni I’m taking a course which requires me and my group to create a complete software project. Out of the available topics we chose to make an airline ticket booking app, much like skyscanner.com. It is my responsibility to handle the majority of the coding aspect of the project, so I would like your advice.

I would like your thoughts and recommendations on what frameworks/languages/technologies you recommend we use to implement the project. I would like to avoid anything complicated that will take a long time to learn, as I only have a limited number of weeks to deliver. However we do need to be able to have a decent looking frontend, a backend that will allow users to login either as passengers or administrators (them being the ones who manage flights and handle passenger accounts etc.), and passengers should be able to at the very least input a departure city and time, and arrival city and time and get a list of available flights back (the flights don’t need to be real-world flights, we can generate that data to simulate the app).

I’ve checked out pythons flask, but (correct me if I’m wrong) while simple it seems too much so. I would need to handle user authentication, creating and connecting any databases etc. all manually from pretty much scratch. I’m interested in finding that middle ground of simple enough to get up and running with quickly, while not so simple where I need to learn 1000 other things just to get a prototype up and running.

Thanks in advance for your suggestions!

Edit: I asked my professor for advice and as he suggested I decided to go with bootstrap and sqlite. Im still open on suggestions to do the authentications though :)

  • bamboo@lemm.ee
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    What are you using on the server side? Last I knew bootstrap was just a (albeit good) front end framework. SQLite is just a db.

    • promitheas@iusearchlinux.fyiOP
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      We don’t need to go as far as actually setting up a server. Isn’t that something sqlite solves in this situation? Meaning, I don’t need to actually set up a server but can simulate what would be going on with the frontend and the actual database in an actual server? I don’t know if I’ve got it mixed up or not.

      If that’s not the case, what should I use for serverside stuff?

      • bamboo@lemm.ee
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        If you are forgoing a backend entirely you don’t need SQLite. If you need a server that can respond to http requests, that’s where you would need something like Django or flask, and they would store their data in SQLite. If your data is all fake and you don’t need it to sync between different browsers you can just fake it all using the web storage api and a static site.

        • promitheas@iusearchlinux.fyiOP
          link
          fedilink
          arrow-up
          2
          ·
          1 year ago

          I looked into the web storage api and while interesting I do need to have something more than that for the project. I cant go full easy mode sadly xD

      • Miaou@jlai.lu
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        1 year ago

        The backend is the layer between your frontend and your database (ignoring the option of using the database itself as your backend but that’s terrible please don’t do this). Without a proper backend, you cannot have a database