Home - Take434/Appollon GitHub Wiki


Appollon Logo, created by Tim

This wiki aims to explain Appollon, a project which was developed in the context of a course at the university. It will give an overview over the project, cover the target audience, discuss the prototyping / design choices and explain some of the more interesting technical details.

What is Appollon

This project was developed to visualize a users Musical Preferences.
In order to achieve this, it utilizes the Spotify API, meaning that a Spotify account is required for the app to function.
Currently the following features are implemented:

  • login with your Spotify account
  • view the playlists on your account
    • analyze these playlists, showing the average features of the songs in it

The following will be implemented in the near future:

  • View your personal stats from a specified time span

There are more things that need implementation before the app can move on from pre-release stage, these will be discussed in the Conclusion.

Scope of the University Project

The Project took place over the span of approximately 4 months, therefore the focus was not on creating a finished product. Instead the task was pretty open and let the students choose in which aspects of the project they wanted to invest more time.
In the case of Appollon the focus is prototyping as well as actual implementation and deployment. Because of this, the market analysis is less detailed and no beta testing or studies were conducted.

Workload distribution

Appollon is implemented by two students, Jonas (HappyChickenESL on Github) and Tim (Take434). Very detailed information about the division of work concerning implementation can be viewed in this repo, but that does not include graphics, prototyping and research. The following is an estimate.

  • idea generation / brainstorming (both)
  • market analysis (Jonas)
  • Prototyping (Tim)
  • Implementation
    • Backend (Jonas)
      • Database
      • Spotify API Communication
    • Frontend (Tim)
      • Data Visualization
      • implementing the prototype with Next.js
  • Deployment (Tim)