Mobile API

Native mobile capabilities are exposed two ways:

• Per-platform managers — application.IOS (in //go:build ios files) and application.Android (in //go:build android files). Use these for anything platform-specific. See the iOS and Android references for the full per-platform surface.
• application.Mobile — a single, build-guarded manager covering the subset of capabilities that behave identically on both platforms. Use this when you want one code path that compiles and runs everywhere.

application.Mobile

application.Mobile dispatches to IOS on iOS, to Android on Android, and to a no-op stub on desktop. Because it has no build constraint, you can call it from ordinary, platform-agnostic Go — no //go:build files of your own:

// Works in any file, on any target.
// On desktop this returns "" (no-op); on device it returns the real path.
dbDir := application.Mobile.StoragePath()
if dbDir == "" {
    // Off-device, or the directory could not be created — handle accordingly.
    return
}
db, _ := sql.Open("sqlite", filepath.Join(dbDir, "app.db"))

StoragePath() returns the absolute path to the app’s private files directory — getFilesDir() on Android, the Application Support directory on iOS — the recommended home for databases and other persistent files. It returns an empty string on desktop, and on device if the directory is unavailable (on iOS, if it cannot be created), so check for "" before using it.

Capabilities

The Mobile manager exposes the capabilities whose signatures are identical on iOS and Android:

Asynchronous results arrive as common:* events, exactly as with the per-platform managers — see Events for the payloads.

What stays platform-specific

Capabilities that differ in shape between iOS and Android are not on Mobile; call them through application.IOS / application.Android from a build-tagged file: