Personal website

In this post you can read all about the setlist maker project!

The idea of the project came about when a friend of mine made a custom setlist of what he hoped would be the official setlist coldplay is going to use this year when they are on tour. He realised it was a lot of fun making the setlist and saw an opportunity for a cool webapp. The webapp would be a setlist maker using which you could easily build a personal setlist with some additional features.

The main focus of the project was on the editor stage of the app. In this stage a lot of quality-of-life features where implemented like the auto suggest for song names and adding custom effects to a song using the extra options.

The editor overall is good to use on mobile (which is our main focus) and desktop with some consideration for drag and drop but in the end we decided it would be a bit too cramped and not very user friendly to implement drag and drop so we opted for good control over the song order using the arrow buttons and with a feedback animation on the moved song.

When you are done creating your own setlist you get to the share stage where we render the created setlist on an html5 canvas. When finished rendering you are able to share the image directly to social media using the 

Here are some images of the final version:

In the end although I did not have as much time spent on the project as I wanted (when do we ever have enough time) I learned a lot about working together in a small team and had a lot of fun!

Setlist maker

Pakket

Although the platform is still a work-in-progress, here are some images of the platform!

Starboard with web - from messages to memories

Sparkle

The idea for filewarp.io came from the pain of transferring files to one other over the internet. Me and a friend of me wanted to tackle this issue using webrtc data channels so we built a proof of concept.

The proof of concept turned out to be a success so we built a frontend for the solution using react with redux on vitejs.

Sadly, due to a lack of positive re-enforcement caused by the lack of similarity between browsers implementation of webrtc. We decided it was best to cut off the project early and not release it since the weird issues which kept happening were way to painful to deal with.

Although we never finished the project I'm very happy we started it. I learned a lot about networking, hole punching and webrtc. It's sad the browsers do not comply with each other and we hope the webrtc spec will be solidified over the years, And maybe try again one day!

Until then here are some images of the frontend built in react:

Filewarp.io

The Idea

The Problem

Conclusion