Web Dev//SDK

Wrapper around an API. A library that makes talking to a service easier. Instead of writing `fetch('https://supabase.co/rest/v1/contacts')`, you write `supabase.from('contacts').select()`. It puts HTTP requests into typed functions — for mobile apps, Node.js servers, Python scripts, whatever platform.

Wrapper around an API. A library that makes talking to a service easier. Instead of writing fetch('https://supabase.co/rest/v1/contacts'), you write supabase.from('contacts').select(). It puts HTTP requests into typed functions — for mobile apps, Node.js servers, Python scripts, whatever platform.

Not the same as helpers: helpers (like @supabase/ssr) are framework-specific extras. The Supabase SDK is generic TypeScript; the SSR helpers are specifically for Next.js — they manage session cookies between browser and server. Without them, four lines instead of forty, but you'd have to write the cookie logic yourself.

A nice way to think about it: a browser tab is like an SDK for people who don't code. You give them a visual layer over the same operations an SDK does with functions. The user has permissions and touches their Supabase (RLS protected) — same as an SDK would, but with clicks instead of code.