Connecting
Learn/L8 · Convex

Convex replaces API routes

For most apps, you don't need REST endpoints — call Convex functions directly from React.

Difficulty 2/5
Short

Plain English

For most apps, you don't need REST endpoints — call Convex functions directly from React. Picture it like this: Skipping the post office because the kitchen has a window onto the dining room. In the apps you ship (Agentify, wedding portals, CRM), you will bump into this on almost every screen — name it clearly when you prompt your coding agent.

Analogy

Skipping the post office because the kitchen has a window onto the dining room.

Go deeper

For most apps, you don't need REST endpoints — call Convex functions directly from React.

Common mistakes

  • Letting the AI rename this concept three different ways in one PR.
  • Building UI before you can say what is stored and who can change it.

AI-agent trap

Agents may invent jargon here. Ask them to explain the concept in plain English first, then map it to your schema and one real screen.

Summary

For most apps, you don't need REST endpoints — call Convex functions directly from React. Skipping the post office because the kitchen has a window onto the dining room. Ask yourself: where does this live in the database, which function changes it, and which screen shows it?

Confidence: