Kyle – Status Post #1 – 10/17/22

For this past week, our group met for 1 hour in the URBN Center lobby, and worked through delegating tasks, as well as doing minor research to figure out how we will build our app.

My Work

New Website

  • We want to build Omni on an actual domain, opposed to a folder on someone’s pre-existing website. To do this, I purchased a domain from bluehost (http://omnimusic.co/), as well as 1 year of hosting.

Code

  • Once the website was purchased and the hosting was confirmed, I logged into an FTP (https://filezilla-project.org/) and cleared all of the pre-existing files from the website.
  • I then downloaded the WordPress installation files () and installed WordPress onto the site, inside of a “blog” subfolder (http://omnimusic.co/blog/). I did this because we only need WordPress for the blog, and I do not feel like dealing with WordPress while building out Omni.
  • I went back a few days after and developed a landing page for Omni to have until the initial state of the application is built (https://github.com/Kdolphin2284/Omni). Click here for the landing page.

Research

  • I have started to research different ways to develop our app, the best way is through the use of React. I don’t know much React, but I understand logic and html/php structuring so that will help me. The alpha will of course be built using html, css, and javascript, but that is not how I want the final product to be built.
  • I also did research on the spotify api (https://developer.spotify.com/documentation/web-api/), as well as allmusic (https://www.allmusic.com/) to try and understand further the requirements of the project. Allmusic doesn’t have a direct api, but they use incremental links to generate artist and genre pages. If we can parse through these links, we can grab the important information we need on artists and genres.

In the Future

  • Will research more into how to create our own api for allmusic.
  • Plan to build out the layout of the Omni screens in the next few weeks so we can worry about grabbing the needed information and displaying it.
  • We need to do more research into data displaying frameworks. D3.js is good, but we still want to look around while we have the time.

Comments

No comments yet. Why don’t you start the discussion?

Leave a Reply

Your email address will not be published.