API Mocking 🛠️
Using API mocking tools in the following two common scenarios is highly recommended.
1. API and client applications are developed concurrently
In this case, setting up a mock server is not obligatory. The Web team regularly updates the staging server with new endpoint deployments daily, and web development moves faster than mobile development due to the latter’s more substantial workload, such as UI implementation, logic integration, and backend implementation. This means the mobile developers can either test directly on the deployed server or use Proxyman to quickly intercept the few in-development endpoints and mock the data.
Detailed information on how to use Proxyman
However, when there is a large discrepancy between the progress of API implementation and the development of the client application, creating a Postman Mock server also emerges as another beneficial and practical solution. With this approach, developers can continue building and testing the client application even when the API implementation lags too far behind.
Detailed information on how to use Postman Mock Server
2. The API is NOT developed concurrently with the client applications
In cases where API development is handled by a third party (hence outside the control of Nimble) or started after the client application development, it becomes imperative to have a mock server.
To ensure no obstacles or delays in the development and testing of mobile applications, a Mockoon JSON environment file, and an initial Postman collection must be set up in advance. The Web team or PM can do the setup.