It appears you don't have support to open PDFs in this web browser. To view this file, Open with your PDF reader
Abstract
The metaverse industry, which has recently become a hot topic, has endless growth potential. Zepato and Roblox, which belong to the virtual world type of Metaverse, have something in common that users can actively participate in content as participantsproducers on the platform with a high degree of freedom by creating avatars in the virtual world. However, the direction of Zepeto, which has a social media-based character, and Roblox, which is growing into social media based on game content, are clearly different. What the two companies have in common is that they create UGC-based communities and platforms produced by users. In the long run, in order to create an ecosystem in which users autonomously and smoothly produce and supply content, the service must perform well as an operator, an intermediate bridge between suppliers and consumers. This case study with Zepato and Roblox recommends success factors of managing the metaverse platform.
You have requested "on-the-fly" machine translation of selected content from our databases. This functionality is provided solely for your convenience and is in no way intended to replace human translation. Show full disclaimer
Neither ProQuest nor its licensors make any representations or warranties with respect to the translations. The translations are automatically generated "AS IS" and "AS AVAILABLE" and are not retained in our systems. PROQUEST AND ITS LICENSORS SPECIFICALLY DISCLAIM ANY AND ALL EXPRESS OR IMPLIED WARRANTIES, INCLUDING WITHOUT LIMITATION, ANY WARRANTIES FOR AVAILABILITY, ACCURACY, TIMELINESS, COMPLETENESS, NON-INFRINGMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Your use of the translations is subject to all use restrictions contained in your Electronic Products License Agreement and by using the translation functionality you agree to forgo any and all claims against ProQuest or its licensors for your use of the translation functionality and any output derived there from. Hide full disclaimer