Engame Dashboard

engame_dashboard.md

Engame Dashboard Project Analysis

Purpose: For vendors to manage artwork, vouchers and payment gateways (?)

What's Missing

• Design for all the features
• New feature specs (Payment gateway, etc)
• Version control e.g git — easier for other devs to contribute
• * Communication method between Backend and Frontend
  • HTTP (REST API etc)
  • Internally (like what you're doing now)

* this decision will determine the frontend technology to use

Features

Login/Logout

• Access Control List (ACL)
  • Superadmin
  • Vendor
  • Merchant

Home

• Statistics:
  • Completed Game Count
  • Game View Count
  • Total Time Spent per Game
  • Daily Recurring Visit
  • Daily Unique Visit
  • Voucher Redemption Count
  • Voucher Views Count

Voucher

• Search vouchers
• List vouchers
• View voucher detail
• Create vouchers
  • Upload artwork (256x256)
  • View artwork
  • Delete artwork
• Update vouchers

Game

• Game Artwork
  • View
  • Create
  • Update
• Generate unique game links
• Provide embeddable code

CMS

• Tutorials
• FAQ
• Videos

Payment & Subscriptions

• Payment page from website
• i-Serve integration
• Email receipts
• Receipts management
• Refund Management
• Subscription Management

User Profile

• Profile Management
  • Name
  • Email
  • Change password
  • Avatar

Support

• Live chat
• Documentation

What's missing

1. Design for all features & new features - does the flowchart count? Here are the new features
   a) payment gateway - using i-serve, our site will be redirected to their payment interface
   b) game artwork upload (different from voucher artwork) - which merchants are allow to upload their product or brand artwork to us to be displayed in the game (the game client will load the uploaded artwork instead of the original artwork if merchant artwork is present)
   c) tutorials, faqs and videos section - to help merchants on using the dashboard
   d) tech support - filling up forms
   e) renew or stop subscription
   f) generate and display merchant web links - when player loads the game with these link, it will only display the merchant's game and voucher; and merchants can embed these link into their website to feature the game in their website too (backend to be done by our side)

2. Version control - we're not using git for the website, we can set a new one up

3. Communication method - whichever is simpler and quicker at this point, I guess it's internally for now; what advantage does HTTP provides? We might go with this now if we have to switch in the future anyway

4. Login/logout - do we have ACL now? we do have superadmin and vendor/merchant now

5. Statistics
   a) voucher redemption count
   b) voucher views count
   c) complete game count
   d) game view count
   e) total time spend per game
   f) daily recurring visits
   g) daily unique visits

We're using GCP at the moment