Refer to the powersync-swift repo on GitHub.
Full API reference for the PowerSync SDK [External link].
Gallery of example projects/demo apps built with PowerSync and Swift.
The PowerSync Swift SDK makes use of the PowerSync Kotlin Multiplatform SDK with the API tool SKIE under the hood to help generate and publish a Swift package. The Swift SDK abstracts the Kotlin SDK behind pure Swift Protocols, enabling us to fully leverage Swift’s native features and libraries. Our ultimate goal is to deliver a Swift-centric experience for developers.
You can add the PowerSync Swift package to your project using either Package.swift
or Xcode:
https://github.com/powersync-ja/powersync-swift.git
as the URL1.0.x
)Before implementing the PowerSync SDK in your project, make sure you have completed these steps:
Signed up for a PowerSync Cloud account (here) or self-host PowerSync.
Configured your backend database and connected it to your PowerSync instance.
Installed the PowerSync SDK.
The first step is defining the schema for the local SQLite database, which is provided to the PowerSyncDatabase
constructor via the schema
parameter. This schema represents a “view” of the downloaded data. No migrations are required — the schema is applied directly when the PowerSync database is constructed.
The types available are text
, integer
and real
. These should map directly to the values produced by the Sync Rules. If a value doesn’t match, it is cast automatically.
Example:
Note: No need to declare a primary key id
column, as PowerSync will automatically create this.
Next, you need to instantiate the PowerSync database — this is the core managed database.
Its primary function is to record all changes in the local database, whether online or offline. In addition, it automatically uploads changes to your app backend when connected.
Example:
Create a connector to integrate with your backend. The PowerSync backend connector provides the connection between your application backend and the PowerSync managed database.
It is used to:
Retrieve an auth token to connect to the PowerSync instance.
Apply local changes on your backend application server (and from there, to your backend database)
Accordingly, the connector must implement two methods:
PowerSyncBackendConnector.fetchCredentials
- This is called every couple of minutes and is used to obtain credentials for your app’s backend API. -> See Authentication Setup for instructions on how the credentials should be generated.
PowerSyncBackendConnector.uploadData
- Use this to upload client-side changes to your app backend.
-> See Writing Client Changes for considerations on the app backend implementation.
Example:
Once the PowerSync instance is configured you can start using the SQLite DB functions.
The most commonly used CRUD functions to interact with your SQLite data are:
PowerSyncDatabase.get - get (SELECT) a single row from a table.
PowerSyncDatabase.getOptional - get (SELECT) a single row from a table and return null
if not found.
PowerSyncDatabase.getAll - get (SELECT) a set of rows from a table.
PowerSyncDatabase.watch - execute a read query every time source tables are modified.
PowerSyncDatabase.execute - execute a write (INSERT/UPDATE/DELETE) query.
The get
method executes a read-only (SELECT) query and returns a single result. It throws an exception if no result is found. Use getOptional
to return a single optional result (returns null
if no result is found).
The getAll
method executes a read-only (SELECT) query and returns a set of rows.
The watch
method executes a read query whenever a change to a dependent table is made.
The execute
method executes a write query (INSERT, UPDATE, DELETE) and returns the results (if any).
You can include your own Logger that must conform to the LoggerProtocol as shown here.
The DefaultLogger
supports the following severity levels: .debug
, .info
, .warn
, .error
.
See Usage Examples for further examples of the SDK.
ORM support is not yet available, we are still investigating options. Please let us know what your needs around ORMs are.
See Troubleshooting for pointers to debug common issues.
Refer to the powersync-swift repo on GitHub.
Full API reference for the PowerSync SDK [External link].
Gallery of example projects/demo apps built with PowerSync and Swift.
The PowerSync Swift SDK makes use of the PowerSync Kotlin Multiplatform SDK with the API tool SKIE under the hood to help generate and publish a Swift package. The Swift SDK abstracts the Kotlin SDK behind pure Swift Protocols, enabling us to fully leverage Swift’s native features and libraries. Our ultimate goal is to deliver a Swift-centric experience for developers.
You can add the PowerSync Swift package to your project using either Package.swift
or Xcode:
https://github.com/powersync-ja/powersync-swift.git
as the URL1.0.x
)Before implementing the PowerSync SDK in your project, make sure you have completed these steps:
Signed up for a PowerSync Cloud account (here) or self-host PowerSync.
Configured your backend database and connected it to your PowerSync instance.
Installed the PowerSync SDK.
The first step is defining the schema for the local SQLite database, which is provided to the PowerSyncDatabase
constructor via the schema
parameter. This schema represents a “view” of the downloaded data. No migrations are required — the schema is applied directly when the PowerSync database is constructed.
The types available are text
, integer
and real
. These should map directly to the values produced by the Sync Rules. If a value doesn’t match, it is cast automatically.
Example:
Note: No need to declare a primary key id
column, as PowerSync will automatically create this.
Next, you need to instantiate the PowerSync database — this is the core managed database.
Its primary function is to record all changes in the local database, whether online or offline. In addition, it automatically uploads changes to your app backend when connected.
Example:
Create a connector to integrate with your backend. The PowerSync backend connector provides the connection between your application backend and the PowerSync managed database.
It is used to:
Retrieve an auth token to connect to the PowerSync instance.
Apply local changes on your backend application server (and from there, to your backend database)
Accordingly, the connector must implement two methods:
PowerSyncBackendConnector.fetchCredentials
- This is called every couple of minutes and is used to obtain credentials for your app’s backend API. -> See Authentication Setup for instructions on how the credentials should be generated.
PowerSyncBackendConnector.uploadData
- Use this to upload client-side changes to your app backend.
-> See Writing Client Changes for considerations on the app backend implementation.
Example:
Once the PowerSync instance is configured you can start using the SQLite DB functions.
The most commonly used CRUD functions to interact with your SQLite data are:
PowerSyncDatabase.get - get (SELECT) a single row from a table.
PowerSyncDatabase.getOptional - get (SELECT) a single row from a table and return null
if not found.
PowerSyncDatabase.getAll - get (SELECT) a set of rows from a table.
PowerSyncDatabase.watch - execute a read query every time source tables are modified.
PowerSyncDatabase.execute - execute a write (INSERT/UPDATE/DELETE) query.
The get
method executes a read-only (SELECT) query and returns a single result. It throws an exception if no result is found. Use getOptional
to return a single optional result (returns null
if no result is found).
The getAll
method executes a read-only (SELECT) query and returns a set of rows.
The watch
method executes a read query whenever a change to a dependent table is made.
The execute
method executes a write query (INSERT, UPDATE, DELETE) and returns the results (if any).
You can include your own Logger that must conform to the LoggerProtocol as shown here.
The DefaultLogger
supports the following severity levels: .debug
, .info
, .warn
, .error
.
See Usage Examples for further examples of the SDK.
ORM support is not yet available, we are still investigating options. Please let us know what your needs around ORMs are.
See Troubleshooting for pointers to debug common issues.