Feature design process

We're not creating mock APIs for the fun of it, we're creating them to aid in the development of features. Given that we could have a rather large API, and thus lots to mock, we need a process in place that somewhat governs the order in which we do things. For example, do we need to wait for an API to be in place before we go ahead and start implementing a feature? If we can mock the API, then we shouldn't have to, but the API itself still needs to be designed, and there are lots of API stakeholders.

In this section we'll go over some of the necessary steps to ensure that we're using mocks correctly, and in a way that scales alongside our feature development.

Designing the API

Some API endpoints are generic enough to support multiple features. These are the entities that are central to our application. Typically, there're a handful of entities that play a vital role, and most features use them. On the other hand, most new features we develop will require an expansion...