LogoLogo
PAO DocsCommunity DocsInfrastructure DocsPeerplays.com
  • Developer Documentation
  • API Reference
    • Peerplays Core API
      • Popular API Calls
      • Account History
      • Asset API
      • Block API
      • Crypto API
      • Database API
      • Network Broadcast API
      • Network Nodes API
      • Orders API
    • Wallet API
      • Account Calls
      • Asset Calls
      • Blockchain Inspection
      • General Calls
      • Governance
      • Privacy Mode
      • Trading Calls
      • Transaction Builder
      • Wallet Calls
    • Bookie API
      • General Calls
      • Listeners
      • Tournaments
  • Peerplays API Libraries
    • Python Peerplays
      • Installation
      • Creating an Account
      • Creating a Peerplays Wallet
      • NFT API
      • Marketplace API
      • Role Based Permissions API
  • Development Guides
    • Creating User Issued Assets
    • Introduction to Permissions
    • NFT Minting
    • Calculating Costs
  • The Cookbook
    • NFTs for Staking Creator Tokens
  • Tools and Integrations
    • PeerID
      • 1.0.0
        • Infrastructure
          • Deployment on a Linux Serve
          • Deployment to AWS ECS
            • Building the Docker Images
            • Storing Secrets in Amazon Parameter Store to use in ECS
            • Creating the Task Definition
            • Creating the Cluster
            • Creating the Service
        • Development
          • How does PeerID work without storing the keys ?
          • Authentication with PeerID
          • Brain Storming
          • Software Requirements
      • Authentication with PeerID
      • Requirements Specification
    • Random Number Generator
      • RNG Technical Summary
      • RNG API
  • Supporting & Reference Docs
    • Peerplays Development FAQs
    • Sidechain Operator Node (SON) Development
      • Generic Sidechain Docs
        • Quick joining GLADIATOR
        • Changes to Peerplaysjs-lib
        • Requirements Specification
        • Low Level Designs
          • bitcoin-deposit-handling-lld
          • bitcoin-operations-draft
          • bitcoin-sidechain-handler-lld
          • bitcoin-sidechain-multisig-bitcoin-wallet-and-bitcoin-addresses-pw
          • bitcoin-withdrawal-handling-lld
          • btc-address-scripting-mechanism
          • comparison-between-scenarios-for-handling-deposits-and-withdrawals
          • exchange-rate-list
          • generic-sidechain-deposit-hld
          • generic-sidechain-high-level-design
          • generic-sidechain-listener-hld
          • generic-sidechain-withdrawal-hld
          • refund-btc-mechanism
          • son-configuration
          • son-consensus-communication-and-transaction-signing-on-chain-lld
          • son-de-register-proposals-lld
          • son-objects-and-operators
          • son-rewards-lld
          • son-voting-lld
          • son-wallet-list_sons-lld
          • creation of a multi-sig bitcoin address lld
          • claiming initial son vesting lld
          • changeover and SON maintenance scenarios lld
          • user-sidechain-addresses-mapping
          • wallet-commands-for-son
        • Functional Specs
          • SON Configuration
          • SON rewards
          • SON Voting and Consensus
          • SONs switchover scenarios
          • SON Status Operations & Monitoring
          • Proposals
          • SON Smart Contracts
      • Bitcoin Sidechain Docs
        • Functional Specs
          • btc-refunds
          • voting-and-consensus
          • son-switchover
          • son-rewards
          • son-proposals
          • son-configuration
          • heartbeat-monitoring
          • BTC Transaction Processing & Signing
          • Bitcoin Withdrawal Handling
          • Bitcoin Deposit Handling
          • SON Multisig Bitcoin Wallet
      • Hive Sidechain Docs
        • Functional Specs
          • HIVE Deposit Handling
          • HIVE Withdrawal Handling
    • Peerplays DEX Development
      • Peerplays NEX
        • Functional Specifications
          • NEX-FS01 Dashboard Page
            • NEX-FS12 ETH-SONs Deposit/Withdraw Functionality
          • NEX-FS02 Login and Account Creation
          • NEX-FS03 Menus and Nav
          • NEX-FS04 Notifications
          • NEX-FS05a Market Page (alpha)
          • NEX-FS05 Market Page
          • NEX-FS06 Profile Page
          • NEX-FS07 Wallet Functions
          • NEX-FS08 App Settings
          • NEX-FS09 Blockchain Page
          • NEX-FS10 GPOS Page
          • NEX-FS11 WhaleVault Integration
      • Requirements Specification
      • Functional Specs
        • Asset Info Page and Asset Lists
        • Dashboard
        • Exchange Page
        • Login and Account Creation
        • User Account Page
        • Voting Page
    • SPK Network
      • Functional Specs
        • Claimdrop Snapshot Functional Specification
        • Initial Claimdrop Functional Specification
    • NFT Development
      • NFT Store
        • NFT Store User Stories
        • NFT Store UI HLD
        • NFT Store Requirements Specification
        • Functional Specifications
          • APP-FS01 App Header
          • APP-FS02 App Body
          • APP-FS03 App Footer
          • APP-FS04 App Navigation
          • APP-FS05 Wallet Functions
          • APP-FS06 App Home Page
          • APP-FS07 Account Page
          • APP-FS08 Browse View
        • App Page List
        • Requirement Traceability Matrix
    • Operation IDs List
    • Sidechain Flow Diagram (HIVE coin)
    • Sidechain Flow Diagram (Bitcoin)
    • Sidechain Flow Diagram (Ethereum coin)
    • TradeHands Explorer
      • User Personas
      • User stories
      • APP-FS01 Detailed View
      • Draft: APP-FS02 Front Page
      • APP-FS03 Collection Details Page
    • Grafana
      • Grafana Installation
      • Install Grafana Behind reverse proxy
      • Loki Installation
      • Promtail agent Installation
      • Grafana Explorer
    • NEX Deployment & Configuration
      • NEX Deployment
      • NEX - Blockchain API configuration
      • Deploying NEX in a HA scenario
    • API Node
      • MarketCap API
    • TOTO Application
      • FS-Subscription Plan
      • FS-Achievements
  • Development Workflow Docs
    • Development Workflow
  • Other Documentation
    • Peerplays Home
    • Community Docs
    • Infrastructure Docs
    • Site Reliability Engineering
Powered by GitBook
On this page
  • 1. Purpose
  • 2. Scope
  • 3. Components
  • 4. Context
  • 5. Wireframe Design
  • A. Settings
  • B. Subscription
  • C. Paid Features
  • 6. Requirements
  • A. Subscription
  • B. Refund
  • C. Future Ideas to enhance TOTO
  • Useful Links:

Was this helpful?

Export as PDF
  1. Supporting & Reference Docs
  2. TOTO Application

FS-Subscription Plan

1. Purpose

The purpose of this document is explain about the subscription plan to be designed for the Toto application. The main focus is to describe the price points, type of subscription, user credits, and the features planned in near future.

2. Scope

The Functional specification document will describe the requirements, components involved, and basic design to be implemented.

3. Components

The proposed configuration, component, and process flow covered in this document includes:

  1. Subscription price points

  2. Subscription plan

  3. User credits

  4. Private group

  5. Achievements

  6. New ideas for future implementation

4. Context

The context of the page must have a proper structure or even template which must provide a consistent User Experience throughout the application. The subscription page will be available under the Profile -> Settings page in the app and provides access to options like subscription plans, buy credits, use credits, and cancel subscription.

5. Wireframe Design

The subscription plan shall have the following pages to categorize the various options such as subscribe/unsubscribe, paid features.

A. Settings

The below representation will help the user to "Subscribe" to the application in order to become a premium member. The list of benefits for the Users will be listed and also shows an option to cancel their subscription.

B. Subscription

Two types of users are possible for an application namely, New user and existing user. The below representation will explain the steps for a new user to subscribe and update the plan.

This representation describes the steps for an existing user to cancel subscription.

C. Paid Features

The User will be given option to "Update the plan" while selecting the subscription.

If the user selects "Buy Credits", then the list of credits and its benefits will be shown as below.

6. Requirements

The below points will describe the requirements specific to the together components.

A. Subscription

  1. The price point for Subscription should offer the following price points for toto customers: a. $20 / Month b. $200 / Year (that’s three months for free) These price point should be configurable for any future updates in price.

  1. There should be a functionality for automatic recurring for the subscribers either Monthly or Annually (based on the User's selection) until the user cancels the subscription from their profile page.

  1. The following benefits should be awarded for the Subscribers

  • (Monthly subscribers) Each month that is paid for, the user shall receive a number of Toto Coins (credits) equivalent to the cost of one letter. (Hence, “One free letter per month”)

  • (Yearly subscribers) Each year that is paid for, the user shall receive a number of Toto Coins equivalent to the cost of twelve letters. (Hence, “One free letter per month”)

  • Create unlimited private groups (Issues) for free Subscribers don't have to pay any toto coins to create a private issue. Unsubscribed User have to pay some toto coins per private issues created.

  • Get a special achievement for becoming a subscriber. (The implementation is in the pipeline and the functionality will be available soon)

Subscribers are welcome to buy more Toto Coins to send more letters whenever they want to.

B. Refund

If the user has spent their toto coins for any activities in the application, then the refund process is not possible. If we have the ability to manage the User's toto coins, then there is a possibility to recall the coins and issue them as a pro-rated refund.

C. Future Ideas to enhance TOTO

The following ideas can be implemented based on the requirements:

  • Schedule follow-up letters function.

  • Access to the experts library for guides on community building and activism.

  • Discounts on Toto Coins.

  • Get a special avatar frame the user can display across the app wherever their avatar appears.

  • Express mailing options.

  • Advanced letter tracking with express mailing options.

  • Priority customer support.

Useful Links:

Figma Dashboard link:

PreviousTOTO ApplicationNextFS-Achievements

Last updated 1 year ago

Was this helpful?

https://www.figma.com/file/KKi8eIqDaHrXMB0t6mL6NQ/Together-%7C-Discovery?type=design&node-id=1636-59353&mode=design&t=5K4iHDnGNFHbuVS2-0