Use Supabase with Android Kotlin
Learn how to create a Supabase project, add some sample data to your database, and query the data from an Android Kotlin app.
1. Create a Supabase project#
To start, you need a Supabase project.
Create a new Supabase project from the Dashboard of any organization you belong to.
Want to create a project programmatically?
Use the Management API or ask the MCP server to create a new Supabase project.
2. Set up your database#
When your Supabase project is up and running, create an instruments table with some sample data. Then set only the privileges each Postgres role needs, add Row Level Security (RLS) for enhanced security for database data by default, and create an RLS policy to make the data in the table publicly readable.
Do these steps within your project's dashboard by copying and running the snippet in your project's SQL Editor.
Save some steps by clicking here to prefill the SQL in the SQL Editor, and then clicking Run.
Want to setup the database programmatically?
You can use the Management API or ask the MCP server to execute SQL queries.
1-- Create the table2create table instruments (3 id bigint primary key generated always as identity,4 name text not null5);67-- Insert sample data into the table8insert into instruments (name)9values10 ('violin'),11 ('viola'),12 ('cello');1314-- Grant the privileges the role needs, which is read access15grant select on public.instruments to anon;1617-- Enable row level security for the table18alter table instruments enable row level security;1920-- Create a policy to allow the anon role to read from the instruments table21create policy "public can read instruments"22on public.instruments23for select to anon24using (true);If you disabled the Data API during project setup, enable it in the Integrations > Data API section of the Dashboard and expose the specific tables or functions you want to access. To automatically grant access for new tables and functions in public, enable Automatically expose new tables.
3. Create an Android app with Android Studio#
Select the Android Studio > New > New Android Project menu item.
4. Set up AI tooling (optional)#
Supabase provides two ways to give AI tools context about your project: Agent Skills, which give your AI coding agent procedural knowledge, and the MCP server, which connects AI assistants to your Supabase project directly.
Agent Skills#
Agent Skills is a curated set of instructions that give your AI agent procedural knowledge about working with Supabase.
Install them so your AI coding agent can produce more accurate, reliable code using current Supabase patterns, such as authentication, server-side rendering, and database migrations, rather than relying solely on training data.
Installing Agent Skills#
To install, run the following command in the root of your project:
1npx skills add supabase/agent-skillsSupabase MCP server#
The Supabase MCP server connects AI assistants to Supabase, so they can inspect your schema and act on your projects on your behalf. Find out how to add it to your client in the MCP docs.
5. Install dependencies#
Open build.gradle.kts (app) file and add the serialization plugin, Ktor client, and Supabase client.
Replace the version placeholders $kotlin_version with the Kotlin version of the project, and $supabase_version and $ktor_version with the respective latest versions. For example, Kotlin 2.2.21, supabase-kt BOM 3.5.0, and Ktor 3.0.3.
If your project uses Kotlin 2.0 or newer with Jetpack Compose, declare the Compose compiler plugin in your root build.gradle.kts:
1id("org.jetbrains.kotlin.plugin.compose") version "$kotlin_version" apply falseThen apply it in the app module, without the version and without apply false:
1id("org.jetbrains.kotlin.plugin.compose")You can find the latest supabase-kt version on GitHub and Ktor in the Ktor documentation. Match your Kotlin version to the supabase-kt release requirements.
1plugins {2 ...3 kotlin("plugin.serialization") version "$kotlin_version"4}5...6dependencies {7 ...8 implementation(platform("io.github.jan-tennert.supabase:bom:$supabase_version"))9 implementation("io.github.jan-tennert.supabase:postgrest-kt")10 implementation("io.ktor:ktor-client-android:$ktor_version")11}6. Add internet access permission#
Add the following line to the AndroidManifest.xml file under the manifest tag and outside the application tag.
1...2<uses-permission android:name="android.permission.INTERNET" />3...7. Initialize the Supabase client#
You can create a Supabase client whenever you need to perform an API call.
For a quick example, create a client at the top of the MainActivity.kt file below the imports.
Replace the supabaseUrl and supabaseKey with your own, which you can get from the helper below, or from the project Connect panel:
Open Connect panel
1import io.github.jan.supabase.postgrest.from2import ...34val supabase = createSupabaseClient(5 supabaseUrl = "YOUR_SUPABASE_URL",6 supabaseKey = "YOUR_SUPABASE_PUBLISHABLE_KEY"7 ) {8 install(Postgrest)9}10...Get API details#
To interact with data in database tables, you use the client libraries that wrap the auto-generated Data API endpoints, authenticating using the Project URL and key from the project Connect dialog.
Read the API keys docs for a full explanation of all key types, their uses, and where to find them.
This guide substitutes your project URL and key directly into the code above, rather than reading them from a .env file. Mobile apps don't get environment variables injected at runtime the way a bundler-based web app does. You'd need a build-time mechanism specific to your toolchain, such as --dart-define-from-file for Flutter, an .xcconfig file for iOS, or a Gradle BuildConfig field for Android. That's a good next step once you're past this quickstart, so your keys aren't committed to source control.
8. Create a data model for instruments#
Create a serializable data class to represent the data from the database.
Add the following below the createSupabaseClient function in the MainActivity.kt file.
1import kotlinx.serialization.Serializable23@Serializable4data class Instrument(5 val id: Int,6 val name: String,7)9. Query data from the app#
Use LaunchedEffect to fetch data from the database and display it in a LazyColumn.
Replace the default MainActivity class with the following code.
This example application makes a network request from the UI code. In production, you should use a ViewModel to separate the UI and data fetching logic.
This snippet omits the app-specific theme wrapper that Android Studio generates (named after your project, e.g. <YourAppName>Theme), so it compiles regardless of what you named your project. Wrap the Surface in your generated theme composable from ui/theme/Theme.kt if you want your project's Material theme applied.
1class MainActivity : ComponentActivity() {2 override fun onCreate(savedInstanceState: Bundle?) {3 super.onCreate(savedInstanceState)4 setContent {5 // A surface container using the 'background' color from the theme6 Surface(7 modifier = Modifier.fillMaxSize(),8 color = MaterialTheme.colorScheme.background9 ) {10 InstrumentsList()11 }12 }13 }14}1516@Composable17fun InstrumentsList() {18 var instruments by remember { mutableStateOf<List<Instrument>>(listOf()) }19 var error by remember { mutableStateOf<String?>(null) }20 LaunchedEffect(Unit) {21 withContext(Dispatchers.IO) {22 try {23 instruments = supabase.from("instruments")24 .select().decodeList<Instrument>()25 } catch (e: Exception) {26 error = e.message27 }28 }29 }30 if (error != null) {31 Text(32 "Error loading instruments: $error",33 modifier = Modifier.padding(8.dp),34 )35 return36 }37 LazyColumn {38 items(39 instruments,40 key = { instrument -> instrument.id },41 ) { instrument ->42 Text(43 instrument.name,44 modifier = Modifier.padding(8.dp),45 )46 }47 }48}10. Start the app#
Run the app on an emulator or a physical device by clicking the Run app button in Android Studio.
Production requirements#
The quickstart procedure in this guide optimizes for getting you to a working app, not for production.
Before you deploy:
- If your app reads or writes through the Data API, review your Row Level Security policies. Any policy you added here is scoped to this quickstart's sample data, not to real user data.
- Set your Supabase credentials as environment variables on whatever platform you deploy to, rather than committing them to source control.
- Configure a custom domain for your Supabase project once you're ready to go live.
Next steps#
- Learn how to build a complete user management app with authentication in the Kotlin tutorial
- Explore the supabase-kt library on GitHub
- Insert more data into your database
- Upload and serve static files using Storage