Activity Feeds

Stream Feeds powers social feeds: timelines, follow graphs, comments, reactions and notification feeds, delivered to clients in real time. These docs cover Feeds v3, the current generation.

How the pieces fit together

Your app reads feeds and posts activities through a client SDK, which receives updates in real time over WebSocket. Your backend uses a server-side SDK to define feed groups, manage follows and sign the user tokens clients connect with.

flowchart LR
  subgraph app[Your app]
    client[Feeds client SDK]
  end
  subgraph backend[Your backend]
    server[Server-side SDK]
  end
  client <--> api[Stream API]
  server --> api
  server -. user token .-> client

SDKs

Client Side SDKs

Read feeds, post activities and subscribe to real-time updates from your app.

JavaScript

The core client for web apps.

iOS

Overview Tutorial

Android

React

Hooks and state on the JavaScript client.

Overview Tutorial

React Native

Overview Tutorial

Flutter

Overview Tutorial

Server Side SDKs

Create feed groups, write activities and manage follows from your backend.

Build with AI

Your AI agent can work with Stream from the terminal with the Stream CLI. There's also an Agent Skills pack so it can look up docs and configure your app.

curl -fsSL https://getstream.io/cli.sh | bash
getstream skills

Agent Skills

Stream CLI

Platform

Users, auth and the rest of the account-level machinery work the same in every Stream product, so they are documented once in the platform docs. Feeds apps touch these first:

Authentication and tokens

Create the user tokens your app reads feeds with.

Users

Create, update, query and delete the users behind every feed.

Permissions and roles

Control who can read and write which feeds.

Push notifications

Notify users about new activity.

Webhooks

React to feed events from your own backend.

Start here

Quickstart

Create a feed, post an activity and watch it update in real time. Code tabs cover every SDK.

Each tutorial builds a working social feed from an empty project. Pick your platform:

FAQ

What's the difference between Feeds v2 and v3?

v3 is the current generation and what these docs cover. The migration guide covers moving a v2 app.

Do feeds update in real time?

Yes. Clients subscribe over WebSocket and receive activities, comments and reactions as they happen.

Do I need my own backend?

Yes. Your server defines feed groups and signs the user tokens clients connect with.

Can I use Feeds with Chat?

Yes. Every Stream product shares the same app, users and tokens; the platform docs cover them once.

Can I read these docs as markdown?

Append .md to any page URL. /llms.txt indexes every page.