Development update 3

The development of the Opus player is going according to plan. There has been a lot of DevOps and programming work.

We have established our environment for deployment, source version controlling, continuous integration and system backup. Our developers have updated and tested the interoperability between components of our development stack for MVP phase. Current stack includes: Node.js as an application server multithreaded layer, StrongLoop as a middleware which interacts with transactional database layer currently based on PostgreSQL, IPFS as decentralized file storage, Ethereum for financials, agreements, and transparency; and React, which works well as an objective presentation layer.
Git, WebStorm, DataGrip, Bash and Truffle have formed our every-day integrated development environment.

We have completed our very first use-case: an artist can now upload a track to the platform, onto IPFS and the blockchain, and can now see the progress bar for the upload. The track then appears on the list of available tracks and upon clicking on it, the track is played and statistics regarding the number of times it is streamed is stored in our database.

The UX is currently in the intensive creation phase, and we are starting to have a clearer idea of what the final player will look like from the user’s perspective.

Over the next two weeks, we are planning to perform stress tests of IPFS and we will continue with backend programming which includes perfecting the database model and expanding the business logic layer of API.

We will publish our next Q&A on Wednesday and our next development update in two weeks’ time, on the 8th January 2018. Be sure to follow us on Facebook, Twitter, and join us on Discord, Telegram and WeChat.