From 5ddcc4dbdb53c050527f4dec2d2432c8166186b3 Mon Sep 17 00:00:00 2001
From: hazn <43835582+haznai@users.noreply.github.com>
Date: Thu, 27 Nov 2025 09:04:56 +0100
Subject: [PATCH] Add explanation of client-first vs local-first

Clarify the distinction between client-first and local-first frameworks.
---
 docs/overview.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docs/overview.md b/docs/overview.md
index 3f068b7c8..e37e55fb5 100644
--- a/docs/overview.md
+++ b/docs/overview.md
@@ -176,6 +176,8 @@ This combines to support a model of uni-directional data flow, extending the red
 
 With an instant inner loop of optimistic state, superseded in time by the slower outer loop of persisting to the server and syncing the updated server state back into the collection.
 
+The Uni-directional and optimistic updates is the reason why Tanstack DB is called a "client-first" framework. Not to be confused with the [Local-first movement](https://www.inkandswitch.com/essay/local-first/), which usually implements bi-directional dataflow. 
+
 ## API reference
 
 ### Collections