Build alternative spotify frontend and learn modern frontend dev on the way
an invention by mlauhoff
Updated over 2 years ago. No love. 1 follower.

Project Description

I hate finding and playing albums on Spotify. I never find what I want, when I want. Playlists are weird for playing albums.

I would love to have something that is like a whiteboard or diagram software. Perhaps like a visual programming system.

Have cover art blocks. Arranged, piled, scaled, whatnot. Have text, other images, lines, drawings, background.

Possible interactions: Click to play. Draw arrows between the albums to chain play them.

Challenge: Finding a good library to do the heavy lifting frontend work.

Distraction: Spotify API authentication.

Learn: Modern frontend development

Goal for this Hackweek

  • Get an idea how things like Angular, Vue, etc. work. Pick one. Possibly Angular, since that is what the frontend teammates use.
  • Do the tutorial
  • Hack up a prototype
  • Make notes on the way

Looking for hackers with the skills:

angular spotify frontend

This project is part of:

Hack Week 22

Activity

  • almost 3 years ago: mlauhoff added keyword "frontend" to this project.
  • almost 3 years ago: mlauhoff added keyword "angular" to this project.
  • almost 3 years ago: mlauhoff added keyword "spotify" to this project.
  • almost 3 years ago: mlauhoff started this project.
  • almost 3 years ago: mlauhoff originated this project.


    • Comments

    • mlauhoff
      almost 3 years ago by mlauhoff | Reply

      Here's the thing. Bugs here and there, but surprisingly useful: https://github.com/irq0/alpile https://irq0.github.io/alpile/

    • mlauhoff
      over 2 years ago by mlauhoff | Reply

      screenshot

    Similar Projects

    openQA log viewer by mpagot

    Description

    *** Warning: Are You at Risk for VOMIT? ***

    Do you find yourself staring at a screen, your eyes glossing over as thousands of lines of text scroll by? Do you feel a wave of text-based nausea when someone asks you to "just check the logs"?

    You may be suffering from VOMIT (Verbose Output Mental Irritation Toxicity).

    This dangerous, work-induced ailment is triggered by exposure to an overwhelming quantity of log data, especially from parallel systems. The human brain, not designed to mentally process 12 simultaneous autoinst-log.txt files, enters a state of toxic shock. It rejects the "Verbose Output," making it impossible to find the one critical error line buried in a 50,000-line sea of "INFO: doing a thing."

    Before you're forced to rm -rf /var/log in a fit of desperation, we present the digital antacid.

    No panic: The openQA Log Visualizer (Also known as the "VOMIT-B-Gone 9000")

    This is your web-based hazmat suit for handling toxic log environments. It bravely dives into the chaotic, multi-machine mess of your openQA test runs, finds all the related, verbose logs, and force-feeds them into a parser.

    image

    Goals

    Work on the existing POC openqa-log-visualizer and change it to something usable

    Resources

    openqa-log-visualizer