Sportshero

Get Started. It's Free
or sign up with your email address
Sportshero by Mind Map: Sportshero

1. Cost

1.1. Microsoft Azure - $3500

1.1.1. DB-prod

1.1.1.1. $1133

1.1.2. DB-dev

1.1.2.1. $380

1.1.3. Enet-service

1.1.3.1. $356

1.1.4. Redis-server

1.1.4.1. $67

1.1.5. Web-prod

1.1.5.1. $476 - #714

1.1.6. Web-dev

1.1.6.1. $476

1.1.7. Admin-panel-web

1.1.7.1. $59

1.1.8. Cosmos DB

1.1.8.1. $62

1.1.9. Right now is payed by Tradehero

1.1.9.1. Should be moved to our own account

1.2. other 3rd party services - $5800

1.2.1. EnetPulse - $3300

1.2.2. Urbanairship - $1499

1.2.3. PagerDuty - $204

1.2.4. Quickblox - $219

1.2.5. Loggly - $225

1.2.6. Mailchimp - $20

1.2.7. Bugsnag - $29

1.2.8. Jira - $110

1.2.9. Github - $168

1.2.10. Appsflyer - $700

1.3. In-app prizes - $4250

1.3.1. MOTD - $3750

1.3.2. Championship competition - $500

1.3.3. Lucky8 - hard to tell

2. Server

2.1. Microsoft Azure based

2.1.1. SQL Server Database

2.1.1.1. Production server - Standard A7 (8 Cores, 56 GB memory)

2.1.1.2. Development server - Standard DS11 v2 (2 cores, 14 GB memory)

2.1.2. Cloud service

2.1.2.1. Prod/staging/Dev env

2.1.2.2. Auto scale role

2.1.2.2.1. Avg CPU >80% to increase

2.1.2.2.2. Avg CPU < 60% to decrease

2.1.2.2.3. Minimum 2 instances

2.1.3. Redis

2.1.3.1. Service cache layer

2.1.3.2. Standard A1 (1 Core, 1.75 GB memory)

2.1.4. Azure Storage

2.1.4.1. Store user profile images

2.1.4.2. Store team jersey images

2.1.4.3. Group chat profile images

2.1.4.4. All kinds static hot deploy configuration files

2.1.4.5. CDN support

2.1.5. Service bus

2.1.5.1. Queue based task excutor

2.1.5.2. Send push notifications

2.1.6. CosmosDB

2.1.6.1. User push notification data

2.1.7. Application insight

2.1.7.1. Service monitoring

2.1.7.1.1. CPU

2.1.7.1.2. Memory

2.1.7.1.3. Request Performance

2.2. C# .Net

2.2.1. Microsoft Entity Framework

2.2.2. Restful web service

2.2.2.1. Api for App

2.2.2.1.1. Login/Registration

2.2.2.1.2. Match list

2.2.2.1.3. Match stats & markets

2.2.2.1.4. Predict a match

2.2.2.1.5. Profile & prediction result/history

2.2.2.1.6. Follow

2.2.2.1.7. Compeition

2.2.2.1.8. Leaderboard

2.2.2.1.9. Team expert

2.2.2.1.10. MOTD

2.2.2.1.11. Lucky8

2.2.2.1.12. Spin-the-wheel

2.2.2.1.13. etc

2.2.2.2. Facebook integration

2.2.2.3. Wechat integtation

2.2.2.4. Apple Pay integration

2.2.2.5. Google Pay integration

2.2.2.6. Paypal integtaion

2.2.3. Admin Panel Web Application

2.2.3.1. ASP.NET MVC

2.2.3.2. Ticket audition

2.2.3.2.1. Purchase

2.2.3.2.2. Consume

2.2.3.3. Competition managerment

2.2.3.4. Team expert managerment

2.3. EnetPulse

2.3.1. Sports data receiver service

2.3.1.1. LAMP

2.3.1.1.1. Hosted on Azure - Standard DS11 v2 (2 cores, 14 GB memory)

2.3.1.2. CronJob running to import data

2.3.1.2.1. Game

2.3.1.2.2. Team

2.3.1.2.3. Markets & odds

2.3.1.2.4. Game results

2.3.2. Sports data provider

2.3.2.1. Football

2.3.2.2. Cricket

2.3.2.3. Basketball (to be added)

2.4. 3rd party Services

2.4.1. Log4Net

2.4.1.1. Unhandled exception

2.4.1.2. Logic exception

2.4.2. ApexPing

2.4.2.1. Web service health check

2.4.3. Pagerduty

2.4.3.1. 24 * 7 oncall support

2.4.3.2. Engineer oncall schedule

2.4.4. Mandrill

2.4.4.1. Email service

3. Client

3.1. ReactNative

3.1.1. Cross Platform mobile framework

3.1.2. Javascript based

3.2. What's good for ReactNative?

3.2.1. Open source by Facebook

3.2.2. 1 team for both iOS and Android

3.2.3. 1 shared codebase

3.2.3.1. Double the work output

3.2.4. Native user experience

3.2.4.1. Much faster than other H5 crossplatform solution

3.2.4.2. Same user experience crossplatform

3.2.5. Hot releaseable

3.2.5.1. No need to wait 1w for Apple approve to fix a bug

3.3. Previous version based on Cocos2dx

3.3.1. Cross Platform framework

3.3.2. Cpp & Lua based

3.3.3. Weak point

3.3.3.1. Render based on OpenGL

3.3.3.2. Too few native component can be used

3.3.3.3. Low in development performance

3.4. Features

3.4.1. Social login

3.4.1.1. Facebook

3.4.1.2. Yuzoo

3.4.1.2.1. Abandoned due to low usage

3.4.1.3. Wechat

3.4.1.3.1. Tech ready, wait for launch in China market

3.4.2. Match prediction

3.4.2.1. Football

3.4.2.2. Cricket

3.4.2.3. Basketball (to be added)

3.4.2.4. By favourite team

3.4.3. Hero follow

3.4.3.1. To follow hero's open prediction

3.4.3.2. 1 ticket required

3.4.3.3. Hero can get 0.25 each follow

3.4.4. Competitions

3.4.4.1. Monthly/Weekly/Overall leader board & price

3.4.4.1.1. Sportshero Championship

3.4.4.1.2. Olympics

3.4.4.1.3. IPL Championship 2017

3.4.4.2. Message boardcast

3.4.5. Leaderboard

3.4.5.1. By Gain

3.4.5.2. By Win Ratio

3.4.5.3. By High score

3.4.6. Mini-games

3.4.6.1. Team expert

3.4.6.2. Match of the Day

3.4.6.3. Lucky8

3.4.6.4. Spin the wheel

3.4.7. Push notification

3.4.8. Message Center

3.4.8.1. 1on1 private chat

3.4.8.2. Group chat (target release end of May)

3.4.8.3. System message (target release end of May)

3.4.8.4. Match discussion (target release end of May)

3.4.8.4.1. Can mention others by push notifications

3.4.9. Chappelli's Corner

3.4.9.1. In-app embedded web browser

3.4.9.2. H5 web page

3.4.9.2.1. 3rd party hosted

3.4.10. Multipule language support

3.4.10.1. English

3.4.10.2. Chinese

3.4.10.3. Bahasa

3.4.10.4. Thai

3.4.10.5. Vietnamese

3.4.11. In-app purchase

3.4.11.1. Apple pay

3.4.11.2. Google pay

3.4.11.3. Paypal pay

3.5. 3rd party Services

3.5.1. Quickblox

3.5.1.1. Chat server host

3.5.2. Pushy

3.5.2.1. Hot release

3.5.3. Bugly

3.5.3.1. Client crashes tracking

3.5.4. Bugsnag

3.5.4.1. Client javascript error log tracking

4. Marketing

4.1. Appsflyer

4.1.1. Install tracking

4.2. Urbanairship

4.2.1. Push notification

4.3. Tongdao

4.3.1. DAU

4.3.2. MAU

4.3.3. Total user

5. Other

5.1. Github

5.2. Jira

5.2.1. Scrum & planning

5.2.2. Bugs tracking

5.3. Naming.com

5.3.1. IP

5.3.2. SSL