Game Server Solution SWOT Analysis by Iridescent Studio

Get Started. It's Free
or sign up with your email address
Rocket clouds
Game Server Solution SWOT Analysis by Iridescent Studio by Mind Map: Game Server Solution SWOT Analysis by Iridescent Studio

1. PUN / PUN+ (Photon Unity Networking)

1.1. Strengths

1.1.1. Platforms: Unity (iOS, Android, & FB w/ WebGL) + More

1.1.2. Continuous Feature Development & Release

1.1.3. Stability & Relative Predictability in Solution Quality

1.1.4. Large & Friendly Community Support

1.1.5. Friendly & Responsive Official Support

1.1.6. Solution Documentation Available & Gets Updated

1.1.7. Predictable Scalability, including Financial Aspects

1.1.8. Availability of Local Software Developers w/ Relevant XP

1.1.9. Solution is Easy to Set up & Running (Numerously)

1.1.10. Solution Decreases Development Time & Efforts

1.2. Weaknesses

1.2.1. Ultimate Bottleneck for Free-to-play Multiplayer Games

1.2.2. Poor Quality of Documentation (Limitedly)

1.2.3. Overhead: Binary Protocol Inefficiency (Numerously)

1.2.4. No Power upon Roadmap for 3-rd Party Developers

1.2.5. Poor Community Insights Quality & Response Time (Limitedly)

1.2.6. Solution is Difficult to Set up & Running (Limitedly)

1.2.7. Cost is Associated w/ CCU Quantity

1.3. Opportunities

1.3.1. Financial Model Change from CCU Dependence to Other

1.3.2. Get Featured by PUN Developers (PR & Marketing)

1.4. Threats

1.4.1. How about Cheating Security Measures?

1.4.2. How about Huge Market Success & Dependence on CCU / Cost?

1.4.3. How about Requirements Significant Change during the Development?

2. SWOT Analysis Theory

2.1. Strengths

2.2. Weaknesses

2.3. Opportunities

2.4. Threats

3. Custom Node.JS

3.1. Strengths

3.1.1. Node.JS Server Code is already Developed

3.1.2. Node.JS Server Code is already Developed Well

3.1.3. Node.JS Server Code has got Documentation

3.2. Weaknesses

3.2.1. Node.JS Server Code still Requires Additional Functionality

3.2.2. Node.JS Server Code / Documentation still Requires Refactoring & Improvement Respectfully

3.2.3. Node.JS Server Code Requires More Time than Implementing, e.g. PUN: ~100 Hours Less for PUN

3.2.4. Node.JS Server Code Requires Time to Investigate

3.3. Opportunities

3.3.1. Node.JS Server Solution to Become Framework for Similar Games

3.3.2. Node.JS Server to Become Popular among Node.JS Developers Globally

3.3.3. Node.JS Server Code is to be Platform Compliant

3.3.4. Node.JS Server Code is to have All Necessary Features

3.3.5. Get "Refund" for Time & Efforts Spent on Node.JS Server Previous Development Round

3.3.6. There is no Need in Looking for Node.JS Developers elsewhere but Iridescent Studio

3.4. Threats

3.4.1. Fail the Server Development within Reasonable Time Frame & Budget

3.4.2. Fail to Document the Server Solution Properly to Support w/ Ease

4. Other Solutions

4.1. UNET by Unity Technologies

4.2. SmartFoxServer by gotoAndPlay()

4.3. DarkRift by NinjaPoke Studios

4.4. Play Games Services by Google

4.5. ElectroServer by ElectroTank

4.6. AppWarp by ShepHertz Technologies

4.7. uLink by MuchDifferent

4.8. Forge Networking by Bearded Man Studios

4.9. www.github.com/jbruening/PNet

4.10. www.tasharen.com/?page_id=4518

4.11. www.photonengine.com/bolt

4.12. www.photonengine.com/turnbased

4.13. www.forum.unity3d.com/threads/badumna-network-suite-unity-version.46365

4.14. www.github.com/jakevn/MassiveNet

4.15. www.kbengine.org

5. Mind Map Legend

5.1. — Research is in Progress

5.2. — Research is Complete

5.3. — Already in Love w/ Solution

5.4. — There are Open Questions

5.5. — Already Eliminated as Choice Option