Bighorn Alpha Release: Qchain’s Advertising App Demo is Here

After months of hard work, and a resolute commitment to prove our dedication to our community by releasing a functional product before conducting an ICO, we are excited to announce that our alpha has been deployed. We are proud to be one of the first decentralized advertising apps to release a demo, and the first to release one prior to a token sale.

Check it out here:

demo.qchain.co

Username: demouser
Password: demopassword

Feel free to play around and let us know your thoughts. The demo will be updated regularly, so you can expect to see (and suggest) changes. We are working to develop a beta in Q4.

Our ICO will begin on October 24th, with an official announcement coming shortly.

Below, you’ll find a detailed guide to the Qchain Advertising App alpha.

What to Expect From the Interface

Three main components comprise the advertising app interface: a dashboard, a marketplace, and a ‘create’ space for ad listings. There is also a toggle option available to switch between different user modes (advertiser or publisher) and token types, which are available throughout the app.

Dashboard

The dashboard contains a summary of statistics, showing numbers of impressions, clicks, revenue, and more. Depending on the user mode and token type selected, the view changes to reflect the statistics that make sense for the user.

Dashboard view in Advertiser mode (left) and Publisher mode (right)

For instance, a publisher sees their revenue, RPM, highest performing ad spaces, and highest grossing contracts. On the other hand, the advertiser sees account balance, impressions, clicks, and best performing ads.

Each token type also fetches data related to contracts that were created with that currency type. For example, if the publisher toggles EQC, they will see information for contracts on adspaces corresponding to that token.

Marketplace

The marketplace features a sidebar with fields the user can use to filter and view the ad space and ad listings to find exactly what they’re looking for. In publisher mode, the user will see related ad listings and use the available filters to choose the ad by dimensions, genre, CPC, CPM, and more. In advertiser mode, the user is able to view listings of ad spaces, with filters that allow the advertiser to choose the ad space that best fits their needs.

As with the dashboard, the user can toggle between EQC and XQC tokens, which will alter the interface to only display ad spaces and ad listings that correspond to the chosen token.

Create

This space is primarily for demonstrative purposes, showing what the process of creating ad spaces and ad listings will look like. The “UserMode Toggle” allows the user to switch between creating an ad space or an ad listing. The “Token Type Toggle” allows users to toggle between EQC and XQC tokens based on whether they prefer to use Ethereum or NEM respectively. Both toggles are accessible throughout the app.

This interface will be specialized to allow advertisers and publishers to transact in native ads in particular in the future. We are moving our direct buy application to focus on native advertising because of the demonstrated effectiveness and profitability of native for content publishers, and consequent increase in campaign investment on the advertiser side.

Technical Info

The front end is a single page application that is built using Angular 4, the latest version of a front end Javascript framework that is known for its responsiveness, combined with a simple NodeJS server. It responds quickly and minimizes the need for requesting information from the server for loading various pages. This setup makes it easy and efficient to interface with our blockchain APIs.

The back end consists of a REST API that is built using the Django Rest framework and a Postgresql database. The REST API is the middleman and responds to requests for information from the front end with information from the database.

In the future, because of the way this is set up, it can allow us to easily switch the tech stack of the front end/back end, or migrate to an entirely different database platform with low effort. This could also set allow users to query our API to get information on stats like revenue or impressions (like the Twitter API that allows you to get information regarding tweets, etc.) and integrate that with other applications they build.

-The Qchain Team