Links

3. Mission and Vision

1. Mission

Our mission is to provide a way for people to build, own, monetize, and socialize in immersive and decentralized virtual spaces. We also want to bring many different NFT projects that exist today to have their community fully connected; play, shop, work, and socialize in metaverse — in short, do the things humans like to do together in real life.
Players and NFT projects can use the features below (for free, of course, XD )
  • Turning 2D NFTs into a wearable T-Shirt for your avatar
  • Limiting your metaverse to "NFT owners only"
  • Customize the metaverse to fit your NFT project world
  • Place 2D & 3D NFTs in metaverse

2. Vision and Dream

2.1 Metaverse

We vision metaverse as a place to live in the near future (not mars, sorry Elon). We want to build metaverse to enable users to protect digital tokens and assets in virtual reality. We think we can build a fully functioning decentralized economy using cryptocurrencies and NFTs, and believe some of today's centralized metaverse is incomplete because of the shortcomings of a centralized managing system. All the lands owner can build P2E games in the future, meaning players can also work there.

2.2 Marketplace

Our 3D marketplace is currently used only for Zoa. However, we vision one day to make the marketplace where people can buy and sell not only Zoa assets but also assets that can be used in other metaverses that will emerge in the future. The reason for this is that existing 3D files come in many formats (Ex. .vrb, .fbx, .obj, .blender, .glb), and different services use different formats, which puts a border on UGC expansion.

2.3 Hardware

Metaverse has two influential components; software and hardware. While we are currently building software, we are also going to build the hardware part too. We know that current VR HMDs are not the ones we believe people can get immersive, and we are willing to invest in a device that inputs directly into the brain, aiming for close coexistence between humans and virtual reality through a direct brain interface.
Good to know: depending on the product you're building, it can be useful to explicitly document use cases. Got a product that can be used by a bunch of people in different ways? Maybe consider splitting it out!