For the research project, the live coding platform that I picked is Motifn. Motifn enables users to make music using JavaScript. It has 2 modes: a DAW mode and a fun mode. The DAW mode lets users connect their digital audio workstation, like Logic, to the platform, by which a user can orchestrate synths into their DAW using JS. The fun mode on the other hand lets you start producing music in the browser right away. I used the fun mode for the project.

The coolest feature about Motifn is that visualises the music for you. Similar to how we see the selected notes in a MIDI region in Logic, Motifn lays out all the different tracks along with the selected notes underneath the code. This allows the user to better understand the song structure and is an intuitive way to lay out the song which makes it user friendly.

To get started, I started reading the examples on the platform. There is a long list of examples right next to the coding section on the website. All of the examples are interactive, which makes it easier to experiment with different things. Since it is right next to the coding section of the website it is also convenient to try out a lot of examples because there was no need to open different tabs to refer to the documentation. Having an interactive, short, and to-the-point documentation enabled me to experiment with different things Motifn has to offer.

After playing around it for a while, I discovered that the platform let’s you decide the structure of the song before you even finish coding the song itself. So, using the let ss = songStructure ({}), I decided to a song structure.

Motifn has a lot of synth options (some of them made using Tone.js) and I am huge fan of synths. So I started my song with that. Followed by the addition of bass in the first bridge, synth + bass + notes in 2nd chorus, bass + hihats in the 2nd bridge, kicks + snare + hihats + bass + chords in the first and second verse, remove the drums in the third chorus and then bring them back in the next one. After that I just take out thre instruments one by one and the song finishes.

Here is the demo of what I made on Motifn.

There isn’t a lot of information about Motifn online. I was unable to find the year it was developed in or even the founders. I would place this platform somewhere in the middle of live coding and DAW music production. I felt as if there was less flexibility to experiment and make music on the fly as compared to TidalCycles. Motifn seems more structured and intentional. But there are a lot of cool sounds and controls on the platform, like adding groove to instruments making it play either behind (like we read in class) or ahead of the beat by a few ms or modulating the harmonicity of a synth over time. Its integration of JavaScript for music composition makes it accessible to a broad range of users which reflects the live coding community’s values of openness and innovation. Overall, it is a fun platform to use and I am happy with the demo song that I made using Motifn.

In techno, the drum components—particularly the kick drum and hi-hats—are arguably the most foundational elements. They act as a constant foundation, driving the rhythm forward and maintaining momentum.

Groove is highly subjective, but in my opinion, adding microtiming or changing velocity of kick drums or hi hats makes a track sound much better. It introduces subtle variations that prevent the beat from feeling too stiff or mechanical. Robotic rhythms aren’t inherently bad, but over time, they can become predictable or monotonous.

However, microtiming isn’t the only thing that gives electronic music its soul. Another major factor is the emotion it evokes in listeners and the culture: Berlin style underground techno will sound very different from Detroit style underground techno.

For example:

Ambient techno has a different kind of soul—it’s deep, introspective, and atmospheric.
Hardstyle has an intense, energetic soul, built around distortion and high-energy kicks.
Hardgroove brings a driving, hypnotic pulse that feels more tribal and raw.


Each subgenre carries its own emotional weight, and that emotional impact is just as important as rhythmic complexity. While microtiming can enhance the feel of a track, other elements like sound design, harmonic progression, and energy levels also contribute to the overall experience of the record.

Electronic music doesn’t need microtiming to have soul, but it benefits from it—especially in genres where groove is key.

As a computer science student and a DJ, I find live coding to be very intriguing because it will enable me to do something creative around my passion for electronic music with code – something that is typically never used in creative fields like music production.

Live coding allows anyone to see and understand the process of creating music through code. Unlike traditional DJing, where music is often mixed from pre-recorded tracks, live coding enables real-time composition, making each performance unique and dynamic. This improvisatory nature mirrors the spontaneity of live music while using the precision and power of programming.

What appeals to me the most is the deeply human aspect of all this. The algorave scene, where people come together to dance to music generated in real time through live coding, is a perfect example of how tech can serve us rather than the other way around. It’s not just about writing code—it’s about using that code to create shared experiences, to bring people together, and to foster a sense of connection. Seeing live coding facilitate something communal through algoraves, subreddits, and GitHub pages reinforces the idea that code isn’t just about logic, structure, and money. It can also be a powerful tool for expression, emotion, and collective joy.