Learning Path: Building for Offline-First

Follow the steps on this learning path to learn about the advantages of an offline-first development strategy for both developers and engineering managers. We’ll look generally at the difficulties of mobile networking, compare different solutions for implementing an offline-first architecture, and finally dive deep into how Realm makes for a reliable offline-first app experience with minimal development effort.

Get more development news like this

1. Serverless in an Offline-first World

Alexander Stigsen introduces the serverless concept, discusses the challenges of mobile connectivity, and how Realm fits into the landscape.

2. REST API Failure Situations

Take a deep dive with Marin Todorov into the current best practices for mobile networking via REST, and some of the built-in challenges and limitations of this approach.

3. Three Approaches to Offline-First Development

Compare three difference solutions for implementing offline functionality in your app, from simple to robust.

4. Eventually Consistent: A Mobile-First Distributed System

This piece discusses popular approaches to data consistency in a smartphone world, and clear solution to overcoming conflict resolution challenges.

5. The Offline First Approach to Mobile App Development

Learn about the pros and cons of different architectural approaches to offline-first development with Realm’s Director of Product Adam Fish and Sergey Bondari of personal finance management app Concur.

Next Up: Offline-First #1 – Serverless in an Offline-first World

General link arrow white

About the content

This content has been published here with the express permission of the author.


Realm Team

At Realm, our mission is to help developers build better apps faster. We provide a unique set of tools and platform technologies designed to make it easy for developers to build apps with sophisticated, powerful features — things like realtime collaboration, augmented reality, live data synchronization, offline experiences, messaging, and more.

Everything we build is developed with an eye toward enabling developers for what we believe the mobile internet evolves into — an open network of billions of users and trillions of devices, and realtime interactivity across them all.

4 design patterns for a RESTless mobile integration »

close