Mobile app developer
Provide relevant and engaging web content to thousands right in the palm of their hand, based on their interests and preferences.
About this use case
Use case
A mobile app developer providing a feed of popular content to its users in several countries. Users can browse different feeds of content, taken from multiple sources, by topic, language, or popularity.Solution summary
A server-to-server integration, collecting new content from NewsWhip'sv1/articlesandv1/fbPostsendpoints. This is stored in a database, which is used by their mobile app.Skills required
- Competent backend development skills
- Competent database administration skills
- Competent mobile app development (Android, iOS) skills
Time to implement
4 people, 2 weeks
Overview
A NewsWhip customer has a mobile app that serves customised content to their users across the world. They provide content from publisher RSS feeds directly in their app, but use NewsWhip's API to find and surface content that is highly customised to their users' tastes.
Due to the volume of users and the unpredictability of mobile app usage, the customer decided to build a server to server integration. They fetch content from NewsWhip at regular intervals, and store it in their own database, which their mobile app uses.
Their integration does the following:
- They perform one call per topic that they track. For example, 'celebrity'. They do this every 5 minutes.
- They restrict the response to only provide data from the previous 5 minutes. By taking the delta between the previous call and the current one, they conserve resources.
- They store the content, the social engagement stats, entities, authors, and topics in their database. These are the things they use to order the data and refine the content for their users.
It looks something like this:
Server to server integration
App to server integration
Tips
- This is a great setup to make the most out of the rate limit that's available to you. Going directly from mobile app to NewsWhip's API will very likely result in hitting the limit.
- Remember that the maximum number of results available for the Historical API is 5000 per call. If you are regularly hitting that limit, try reducing the time between calls.
Useful materials
Updated 11 months ago