Mobile integration · iOS · Android¶

The smartphone is the most relevant mesh device: portable, sensor-rich, always with you. Jarvis integrates deeply with iOS and Android, respecting each platform's constraints.

iOS¶

Available capabilities¶

Integration pattern¶

iOS is closed: deep Jarvis integration requires a companion app distributed via the App Store (or TestFlight). The app exposes:

• App Intents for Siri/Shortcuts (OpenBriefing, AskJarvis(text), RecordNote)
• Widget extension for home screen
• Live Activity extension for in-progress briefing
• HomeKit Bridge to expose Jarvis as an accessory
• Push notifications via APNS

flowchart LR
    SIRI[Siri] -->|App Intent| APP[Jarvis iOS App]
    SHORT[Shortcuts] -->|App Intent| APP
    APP -->|HTTPS| SERVER[Jarvis Server]
    SERVER -->|APNS| APP
    APP <-->|HealthKit| HK[HealthKit]
    APP <-->|HomeKit| HOME[HomeKit accessories]
    APP -->|x-callback-url| OTHER[Other apps]

App Intents example¶

// Siri: "Hey Siri, Jarvis briefing"
struct OpenBriefingIntent: AppIntent {
    static var title: LocalizedStringResource = "Open Jarvis Briefing"

    func perform() async throws -> some IntentResult {
        let briefing = try await JarvisAPI.shared.fetchDailyBriefing()
        return .result(view: BriefingView(briefing: briefing))
    }
}

URL scheme¶

The app also supports a URL scheme for integration from external automations:

jarvis://chat?text=Summarise+last+meeting
jarvis://briefing?type=morning
jarvis://memory/recall?topic=vacation

Android¶

Available capabilities¶

Integration pattern¶

Android is significantly more open than iOS:

flowchart LR
    LAUNCHER[Launcher / Voice] -->|Intent| APP[Jarvis Android App]
    TASKER[Tasker] -->|MCP / Intent| APP
    HA[Home Assistant Companion] -->|Intent broadcast| APP
    KDE[KDE Connect] <--> APP
    APP <-->|HTTPS| SERVER[Jarvis Server]
    APP <-->|Health Connect| HC[Health Connect]
    APP -->|MQTT| HABRIDGE[Home Assistant]
    APP -->|Wear OS| WATCH[Wear OS Watch]

Tasker MCP integration¶

Tasker exposes an MCP Server that Jarvis can call for ultra-deep device control (volume, notifications, scene execution, context-aware automations).

# Example Tasker task invocable via MCP
- task: "Drive Mode"
  trigger: "context: in_car"
  actions:
    - mute_notifications
    - launch: "Google Maps"
    - audio_route: "bluetooth"
    - announce_jarvis: "Drive mode active"

Android Intent example¶

// Trigger a Jarvis action from another app or Tasker
val intent = Intent("dev.federicocalo.jarvis.ACTION_BRIEFING").apply {
    putExtra("type", "morning")
    putExtra("voice", true)
}
sendBroadcast(intent)

iOS vs Android comparison¶

KDE Connect¶

KDE Connect covers laptop ↔ Android (and now iOS too). Capabilities used by Jarvis:

• 📋 Clipboard sync (copy on PC, paste on phone)
• 🔔 Bidirectional notifications (reply to SMS from PC)
• 📂 Fast file transfer
• 🎵 Media remote (control phone stream from PC)
• 🖱️ Mouse/keyboard remote (for presentations)

KDE_CONNECT_DEVICE_ID=...

Configuration¶

# iOS
JARVIS_IOS_APNS_KEY_ID=...
JARVIS_IOS_TEAM_ID=...
JARVIS_IOS_BUNDLE_ID=dev.federicocalo.jarvis

# Android
JARVIS_ANDROID_FCM_KEY=...
JARVIS_ANDROID_PACKAGE=dev.federicocalo.jarvis

# KDE Connect
KDE_CONNECT_ENABLED=true

# Home Assistant Companion
HOME_ASSISTANT_URL=http://hassio.local:8123
HOME_ASSISTANT_TOKEN=eyJ...

Roadmap¶