All Collections
Getting Started
Mobile SDK Integration
How can I manage the dev and live environment with Batch?
How can I manage the dev and live environment with Batch?

Here are the best practices to manage both environments

Alexandre avatar
Written by Alexandre
Updated over a week ago

A staging environment refers to a parallel server environment for testing websites and software applications in conditions as close as possible to reality, without compromising the organization's actual data or interrupting its operations.

You should always integrate Batch in a dev environment, and go into production mode when everything has been tested and validated.

For this matter, we strongly recommend that you create two applications per OS on the dashboard: one for tests and one for production (e.g. MyApp and [DEV] MyApp). This will allow you to use the Live API Key for all your apps and test all features before going live.

Using a Live API Key for both apps allows you to avoid relying on the Dev API Key, which has a more limited functional scope than the Live one.

Thereafter, dev apps can only be displayed to developers so as not to disturb your operational teams on the dashboard (see more here).


This article belongs to Batch's FAQ. Need more help? Find insightful articles, documentation, case & market studies, guides, and even more in our website's Resources section on batch.com and our blog.

Did this answer your question?