Blog posts

---

Our predecessor

Weblaunch V2 was built on Angular, Firebase and Tailwind CSS.

We planned to make Weblaunch V2 a fairly complex application. Therefore, Angular was our first choice as it is a robust and heavy framework with many capabilities for expansion. In addition, it was what our developers were most familiar with.

At the time of Weblaunch V2's start, we were missing a decent amount of experience in the back-end side of web development. We chose Firebase because it made us focus on the front-end part of Weblaunch while Firebase took care of the rest.

Our goal was to make Weblaunch V2 good-looking with a simple design. Tailwind CSS was at the time a small, but fast-growing, CSS framework. We saw the potential in Tailwind, such as a better CSS syntax and the ease of creating a responsive app for all screen sizes. We were not the only ones seeing the potential in Tailwind. It is now the 'hottest' CSS framework out there.

WL3

We continued using Angular for Weblaunch 3, for the same reasons as when we chose it for Weblaunch V2. Keep in mind that we have learned a lot from the Weblaunch V2 era, making us able to utilise the framework at a new level.

Weblaunch 3 is a desktop app, and we chose to run the build it using Electron. It gives us the ability to gather our app in all Typescript code, making the entire platform more robust and stable.

By the time we started working on Weblaunch 3, Tailwind v2 was released. Bringing Tailwind into Weblaunch 3 was a simple five-minute job, giving us beautiful results when utilised.

WL-API

We decided to ditch Firebase at once. It was giving us limits to what we could achieve with Weblaunch. Therefore, we started making our custom API from the ground up.

As stated before, we wanted to gather all of our Weblauch 3 code in Typescript. It was natural to choose the classic back-end javascript collection: Node and Express.

We chose Postgresql as our database. It is a classic SQL relational database giving us unlimited possibilities.

Socket.io is operating some additional services, such as the chat and transmit features.

WLL

We could not make the Weblaunch landing page inside Weblaunch 3, as WL3 is a desktop application, not a website. To create a landing page displaying the features and information regarding Weblaunch, we needed a simple and lightweight framework. The result was Next.js paired with Tailwind CSS.