Background

Currently, the product is

• using logo and brand identity indistinguishable from the project.
• is hosted on a subdomain of the joystream project: play.joystream.org

but at the same time we refer to it as Atlas both internally, on the website and in announcements, social media, newsletters and other communication. This leads to people being a bit confused about what it is, whether it is itself Joystream, and
this lack of distinction has some costs.

1. It becomes less clear that it is intended to be one among many products that people can build on the platform.
2. Confusion in general just lowers clarity of marketing, word of mouth and buyin to the future.
3. Creators will be less clear about who exactly they are giving their content to and who can use it, and under what constraints. Are the terms and conditions with the DAO or Jsgenesis?

As it stands, its clear that there is ample room for Jsgenesis to keep making a very wide range of improvements in the Atlas product post launch, stuff like

• Orion v2
• Youtube-synch
• Shared data layer
• Creator token?
• Creator analytics
• Fiat onboarding

, etc. Some of these things may go live before mainnet, but executing and iterating on them well will clearly go beyond that milestone. This means these costs (1-3) are going to increase, because this implies that the time horizon for Jsgensis being involved in developing Atlas is clearly expanding, and it may end up becoming an important first application for creators to get involved for a longer period of time than I initially imagined.

Proposal

Here is a very humble low effort set of changes we can make to put us on a better path in terms of addressing these costs:

• Put app on separate top level domain, independent from Joystream.
• Give separate logo.
• Consider a name change if it makes sense?

┆Issue is synchronized with this Asana task by Unito