---
title: "Discussion on \"Designing an API for Mobile Clients: Pagination, Versioning and Errors\" | Hashnode"
description: "Discussion on \"Designing an API for Mobile Clients: Pagination, Versioning and Errors\". A web client and its backend usually update together: you deploy and every user gets the new version. Mobile does not work that way. Production runs versions released eighteen months ago, devices on f"
url: "https://hashnode.com/posts/designing-an-api-for-mobile-clients-pagination-versioning-and-errors/6b00180d5014a065335cd6b6"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Designing an API for Mobile Clients: Pagination, Versioning and Errors](https://mosmox.hashnode.dev/designing-an-api-for-mobile-clients-pagination-versioning-and-errors?utm_source=hashnode&utm_medium=feed)

A web client and its backend usually update together: you deploy and every user gets the new version. Mobile does not work that way. Production runs versions released eighteen months ago, devices on f

10h ago · 8 min read · mosmox.hashnode.dev  
Read the article

-   [#api](https://hashnode.com/tag/api)
-   [#mobile-development](https://hashnode.com/tag/mobile-development)
-   [#backend](https://hashnode.com/tag/backend)
-   [#ios](https://hashnode.com/tag/ios)
-   [#android](https://hashnode.com/tag/android)

## Written by

[Mosmox Studio](https://hashnode.com/@mosmox)

@mosmox · Kyiv, Ukraine

  
[View profile](https://hashnode.com/@mosmox)

Mobile product studio: iOS, Android & React Native apps

Mosmox is a mobile product studio from Ukraine. We research, design, build, launch and grow mobile products: native iOS and Android apps, React Native, and the web around them. We write practical notes on App Store and Google Play rules, mobile UX, accessibility and the numbers behind the mobile market.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
