On larger projects, where different team members work on features that are dependent on other team members' contributions, the ability to work as if the feature already exists, when in fact those developers haven't completed it, can keep overall progress chugging along. When it comes to web and mobile apps, one of the classic "divides" occurs between client and server. You might have developers focusing solely on the front end or mobile app, with others focusing on server-side concerns, like web services. Have you ever been on a team where the client-focused developers had to wait for server-side devs to complete work on HTTP services before they could continue on? This does not have to be the case. Mocking HTTP services itself isn't difficult – and depending on your client side architectural choices, you can also mock your data using your models/view models. We take a quick look at two of these options in this post.