SendingNetwork
  • OVERVIEW
    • Getting Started
    • FAQs
  • Network Instructional Articles
    • Basics
      • Introducing the Edge, WatchDog, and Guardian Nodes
      • Overview
      • Messaging Solution
      • Privacy Solution
      • Rich Communication Solution
      • Multi-Platform Solution
      • Decentralized Identity
      • Multiple Chat Modes
      • How It Works
      • Token Utility
      • The Team
    • Key Concepts
      • Decentralized Identity
      • Social Graphs
      • Edge Node
  • SDK Documentation
    • Glossary
    • JavaScript client SDK
      • DID
      • User
      • Message
      • Room
      • Contact
      • Social Graph
    • iOS client SDK
      • Push
      • DID
      • User
      • Message
      • Room
      • Contact
    • Android client SDK
      • User
      • Room
    • Java SDK
      • DID
      • Room
      • Message
    • Node.js SDK
      • DID
      • Room
      • Message
    • Unreal SDK
      • DID
      • User
      • Message
      • Room
    • Unity SDK
      • DID
      • Room
      • Message
    • Website chat widget SDK
      • Customization
      • DID
      • User
      • Room
      • Message
      • Other
    • Bot SDKs
      • Golang Bot SDK
        • DID
        • User
        • Room
        • Message
    • Extensible Message Interface
    • Push Notifications
    • Flutter SDK
      • DID
      • User
      • Message
      • Room
    • PHP SDK
      • DID
      • Room
      • User
    • Developer Key
  • Acquisition Kit
    • Social Boost Development Instructions
  • WatchDog Agent
    • WatchDog Agent Guide
    • WatchDog Agent Deployment Tutorial
      • Linux Deployment Tutorial
    • One-Click Deployment
  • Edge Node
    • Edge Node Deployment Tutorial
    • VPS Setup Guide
      • Google Cloud Platform (GCP)
      • Amazon Web Services (AWS)
      • Contabo
    • Check Node Stats with Auto-Reply Bot in SendingMe App
    • Alpha-3 Testnet FAQs
  • delegation node
    • Delegation Node Deployment Tutorial
  • Private Delegation Node
  • Use Cases
    • Wallet-to-Wallet Messaging
    • Dapp Notifications
    • Identity Verification
    • Gamer Acquisition
    • Cross-platform Trading
Powered by GitBook
On this page
  • Use Case Name
  • Actors
  • Preconditions
  • Basic Flow of Events
  • Post-conditions
  1. Use Cases

Gamer Acquisition

PreviousIdentity VerificationNextCross-platform Trading

Last updated 2 years ago

Sending.Network (SDN) envisions providing stable and secure messaging across platforms. More than that, Sending.Network thrives to help with player acquisition for games. In the web2 scenario, games encourage players to share their in-game accomplishments and status on Twitter or Facebook as a means of attracting new players. The Feeds feature in Sending.Me could cover the blanks in web3 status sharing and provide a place to display this game information to an ordinary user within the player’s social relations.

The below use case describes how Sending.Network and Sending.Me help attract game users from the player’s social relations.

Use Case Name

Game player acquisition.

Actors

  1. A Game

  2. Player Alice

  3. Alice’s friend within her Sending.Network social graph

  4. Sending.Network protocol

Preconditions

  1. The game has integrated the Sending.Network protocol.

Basic Flow of Events

  1. The use case begins when Alice sends her in-game accomplishment to Sending.Me in the game app.

  2. The game calls the messaging API of Sending.Network.

  3. Sending.Me receives and decrypt the message.

  4. Sending.Me places the accomplishment message in the feeds.

  5. Alice’s friends in Sending.Me see her status.

  6. Alice’s friends find the status interesting and try out the game.

  7. The use case ends successfully.

Post-conditions

Alice’s friends see her Sending.Me feeds and try playing the game.

Overview
Flow Chart