appwrite-kotlin

Use the Account service to call createEmailPasswordSession with an email and password, or createOAuth2Session with an Activity and OAuthProvider for social login. On the server, use createSession with a userId and secret to exchange OAuth tokens.

Use TablesDB.listRows with a list of Query objects such as Query.equal, Query.greaterThan, Query.orderDesc, and Query.limit. Prefer cursor pagination with Query.cursorAfter for large datasets, and always use named arguments for method calls.

Use TablesDB for all new code, as the Databases class is deprecated. Only use Databases if the existing codebase already relies on it or it is explicitly requested.

Yes, SSR uses two clients: an admin client with an API key for creating sessions and a per-request session client that reads the a_session_<PROJECT_ID> cookie. Set httpOnly, secure, and SameSite=Strict on session cookies.

Appwrite grants no access by default, so resources without explicit permissions are inaccessible even to their creator. Set permissions using Permission and Role helpers, and avoid combining Role.any() with write, update, or delete.

Use Storage.createFile with a bucketId, a fileId from ID.unique(), and an InputFile created via InputFile.fromPath or InputFile.fromBytes. Attach read, update, and delete permissions to control who can access the uploaded file.