<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Peter Ian Betos on Medium]]></title>
        <description><![CDATA[Stories by Peter Ian Betos on Medium]]></description>
        <link>https://medium.com/@peterbetos?source=rss-a0efa80c5294------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*bGKGJ-VtTedB7fB5.</url>
            <title>Stories by Peter Ian Betos on Medium</title>
            <link>https://medium.com/@peterbetos?source=rss-a0efa80c5294------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 15:16:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@peterbetos/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Preparing List-Oriented API for Mobile Apps]]></title>
            <link>https://medium.com/@peterbetos/preparing-list-oriented-api-for-mobile-apps-ebf4e12abc5?source=rss-a0efa80c5294------2</link>
            <guid isPermaLink="false">https://medium.com/p/ebf4e12abc5</guid>
            <category><![CDATA[api]]></category>
            <dc:creator><![CDATA[Peter Ian Betos]]></dc:creator>
            <pubDate>Tue, 21 Mar 2017 11:05:49 GMT</pubDate>
            <atom:updated>2017-03-21T11:05:49.564Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Disclaimer: The principles below doesn’t include approaches on how to apply security principles on the web service.</em></p><p>When you’re preparing web service API’s for a client application, the goal is to give the data to the app as simple and as fast as how the client app intends to render it. Ideally the optimal scenario for web service to client app integration will be to have a ready made BaaS that can prepare the data models and immediately inherit its properties to the client application (like how Firebase does it). How would you prepare the interface agreement, however, if you need to start the web service endpoints from scratch? Heavy list-oriented API’s (or at least the endpoints) should have the following principles below if you need the relationship of the client application user experience with the web service endpoints to be straightforward. The principles are sorted based on priority. If there are any potential conflicts on the principles while conceptualizing the API, the preceding principle applies:</p><ol><li><strong>“Client Application Use Case”-Facilitative</strong> — The goal is to minimize wait time for each use case screen to be ready. So the API structure should be able to facilitate at the most optimal number of 1 (at most) API execution per use case screen interaction. The internal backend API’s can be structured as heavily modular if the platform needs it, however<strong> the web service API endpoint should be use case oriented. </strong>If ayaw ng nagde-design ng backend, sabihin mo walang sisihan.</li><li><strong>“Selective Data” — Enabled</strong> — The API should be able to provide a response that can facilitate both summary and detail-oriented data list. The API should also be able to facilitate selective use-case-oriented data, to provide an option to the client application a possibility for minimal data if needed for a specific screen. The API should also facilitate responses that can only return a single list item.</li><li><strong>Model-Modular</strong> — Fields should be, as much as possible, separated as per how the model/entity fields/attribute is represented. The web service should be able to facilitate at least one model/entity as its minimum requirement. This also implies that if the screen use case needs a representation of model/entity list as a summary, the API should be ready to do so. See item number 2 for details.</li><li><strong>Delta/Pagination-Based</strong> — The API should be able to provide results in paginated quantities (e.g. by 10’s or 20’s) or in delta sets (e.g. how many records are updated/new after 5 PM) to minimize the throughput time the API needs to provide lazy-loaded response to the client app. The fields that can be applied to facilitate such property are the following:</li></ol><ul><li><strong>Limits</strong> — provides limits on how many records will be given on the response provided that there is a starting point.</li><li><strong>Time Range</strong> — provides time limits for the records that will be requested. This is very helpful if the client application just need to capture the delta changes starting from the time it is last updated.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ebf4e12abc5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>