The Onboarding Process
When you begin working with Big Fish Games, you will be paired with a producer who will walk you through our onboarding process. There are two onboarding components:
- Onboarding your people - i.e. developers, producers, etc
- Onboarding your game code and artifacts into our systems
Developer Onboarding
Each developer in the partner studios will be assigned a Big Fish user account, which will be used to access all of Big Fish systems. Once your account is set up, you can access all developer applications through our Okta interface.
You will have access to one or more of the following applications:
| Application | Description |
|---|---|
| Slack | Message-based communication platform |
| GitHub | Cloud-based service for software development and version control |
| Confluence | Wiki and documentation tool |
| Jira | Bug tracking, issue tracking and agile project management tool |
| Jenkins | Automation server used to build, test, and deploy software |
| Google Cloud Platform | |
| Nexus | Stored build artifacts |
| AppsFlyer | Marketing analytics and attribution platform |
| Snowflake | Data storage and analytics service |
| Looker | Enterprise platform for BI, data applications, and embedded analytics |
| Leanplum | User engagement tool |
| brainCloud | Backend service for cloud data, in-app purchases, inventory management, and more |
Game Onboarding
Once a contract is signed, we will begin the game onboarding process. During this time, your game will be:
- Assigned a “code name” and bundle ID
- Added to our Jenkins build pipeline
- Uploaded to Nexus
- Added to the Google Play, Apple App, Facebook and/or Amazon stores
- Configured in our Rave authentication system
This will complete the initial setup and configuration for your game.