appwrite-kotlin

Use the Account service to call createEmailPasswordSession for email login or createOAuth2Session with an Activity reference for OAuth providers like Google. On the server, use createSession with a userId and secret to establish sessions.

Use the TablesDB service with listRows and pass Query helpers such as Query.equal, Query.greaterThan, Query.orderDesc, and Query.limit. Prefer cursor pagination with Query.cursorAfter for large datasets, and use TablesDB rather than the deprecated Databases class.

Yes, the Realtime service supports subscribing to channels for table rows, storage files, teams, and function executions. Subscriptions deliver events and payloads through callbacks and work with coroutines, and you close them with subscription.close().

Yes, use the sdk-for-kotlin artifact with an API key for server-side admin operations. For SSR auth, maintain a reusable admin client and create a per-request session client that reads the a_session_<PROJECT_ID> cookie.

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