webdev-readme-mobile-backend

Define the table in drizzle/schema.ts using drizzle-orm mysql-core helpers, then run pnpm drizzle-kit generate to produce migration SQL and apply it via webdev_execute_sql. Add query helpers in server/db.ts and export inferred types from the schema.

Use protectedProcedure from server/_core/trpc instead of publicProcedure, which guarantees ctx.user exists. On the frontend, catch UNAUTHORIZED errors from failed calls and redirect the user to the login screen.

Yes. On iOS and Android, login uses WebBrowser.openAuthSessionAsync and stores a Bearer token in expo-secure-store. On web, authentication uses an HTTP-only cookie that the browser sends automatically with requests.

Yes. Backend capabilities like invokeLLM, generateImage, transcribeAudio, and storagePut work with publicProcedure routes. User authentication is only mandatory when you need to identify users or sync user-specific data.

The json_schema response format works reliably only for flat structures. For nested arrays or objects, use response_format with type json_object instead and describe the desired shape in the system prompt, then parse the returned content with JSON.parse.

Call storagePut from server/storage.ts with a relative key, file buffer, and content type. It returns a key and a /manus-storage/ URL served via signed redirect, which you save in your database for later retrieval.