Can FluidVoice Be Used on Other Apple Platforms? macOS Compatibility and Roadmap

FluidVoice is currently restricted to macOS and cannot compile for iOS, iPadOS, watchOS, or tvOS due to hard dependencies on macOS-specific frameworks, though iOS support is actively planned according to the project roadmap.

FluidVoice is an open-source voice application developed by altic-dev that leverages native macOS frameworks for audio processing and UI rendering. While the repository has gained attention for its innovative approach to voice interfaces, users frequently ask whether FluidVoice can be used on other Apple platforms beyond macOS. The current implementation is architected exclusively for macOS 15 (Sequoia), with platform-specific dependencies that prevent cross-compilation.

Current Platform Limitations in FluidVoice

macOS-Only Package Configuration

The project's package manifest explicitly restricts builds to macOS. In Package.swift, the platforms array declares only a macOS target:

platforms: [
    .macOS(.v15),
],

This configuration prevents the Swift Package Manager from resolving dependencies or compiling the binary for any other Apple operating system. The platforms parameter lacks iOS, iPadOS, watchOS, or tvOS specifications, making cross-platform compilation impossible without modifying the package manifest.

AppKit and ApplicationServices Dependencies

FluidVoice relies on AppKit and ApplicationServices, frameworks exclusive to macOS. These frameworks handle the menu bar integration, global hotkeys, and window management that define the application's user experience. Because AppKit is unavailable on iOS (which uses UIKit) or other Apple platforms, the codebase cannot link against these system libraries on non-macOS devices.

Technical Barriers to iOS and iPadOS Support

Entry Point Architecture

The application's entry point in Sources/Fluid/fluidApp.swift demonstrates the macOS-specific initialization that prevents iOS compilation:

import SwiftUI

@main
struct FluidApp: App {
    @StateObject private var menuBarManager = MenuBarManager()
    @StateObject private var appServices: AppServices
    @ObservedObject private var settings = SettingsStore.shared
    @NSApplicationDelegateAdaptor(AppDelegate.self) var appDelegate

    init() {
        // Initialise the shared services singleton
        _appServices = StateObject(wrappedValue: AppServices.shared)
    }

    var body: some Scene {
        WindowGroup(id: "main") {
            AdaptiveAppTheme(accent: self.settings.accentColor) {
                ContentView()
                    .environmentObject(self.menuBarManager)
                    .environmentObject(self.appServices)
            }
        }
        .defaultSize(width: 1000, height: 700)
    }
}

The @NSApplicationDelegateAdaptor attribute and AppDelegate references are macOS-specific patterns that have no equivalent in the iOS application lifecycle. Additionally, the MenuBarManager class manages the macOS status bar, a UI paradigm that does not exist on iOS or iPadOS.

UI Components Built for macOS

The view layer in Sources/Fluid/Views/ combines SwiftUI with AppKit-specific components to create the native macOS interface. While SwiftUI is cross-platform, the implementation uses macOS-specific modifiers and window behaviors that would require significant refactoring for UIKit or iPadOS multitasking environments.

FluidVoice Platform Roadmap

According to the project's README.md, the development team has publicly committed to expanding platform support. The documentation states:

"FluidVoice is on macOS today. iOS and Windows are on the way"

This roadmap confirms that while FluidVoice cannot be used on other Apple platforms currently, iOS compatibility is actively planned. However, the README makes no mention of iPadOS, watchOS, or tvOS support, suggesting the immediate focus is limited to iOS rather than universal Apple platform deployment.

Requirements for iOS Port

When iOS support arrives, the codebase will require a separate UI layer using UIKit or iOS-compatible SwiftUI components. The team will need to:

• Replace @NSApplicationDelegateAdaptor with iOS app lifecycle management
• Reimplement MenuBarManager functionality using iOS-specific UI patterns
• Add iOS targets to Package.swift
• Create platform-specific view variants in Sources/Fluid/Views/

Summary

• FluidVoice is currently macOS-only, targeting macOS 15 (Sequoia) exclusively
• The Package.swift manifest contains no iOS, iPadOS, watchOS, or tvOS platform targets
• AppKit dependencies in Sources/Fluid/fluidApp.swift prevent compilation for iOS
• The README confirms iOS support is planned but does not mention other Apple platforms
• Porting to iOS will require replacing macOS-specific frameworks with UIKit equivalents

Frequently Asked Questions

Can FluidVoice run on iPad?

No. FluidVoice cannot run on iPad or iPadOS because it depends on macOS-specific frameworks like AppKit and ApplicationServices that are unavailable on iPad devices. The application would require a complete UIKit reimplementation to support iPadOS.

Is there an iOS version of FluidVoice?

Not currently. According to the official README in the altic-dev/FluidVoice repository, iOS support is on the development roadmap but has not been released. The codebase remains macOS-only as of the latest commit.

What macOS version is required for FluidVoice?

FluidVoice requires macOS 15 (Sequoia) or later. The Package.swift file explicitly sets the platform requirement to .macOS(.v15), and the application uses APIs introduced in this version.

Will FluidVoice support Apple Watch or Apple TV?

There is no indication of watchOS or tvOS support in the project roadmap. The README mentions only iOS and Windows as future platforms, with no references to Apple Watch or Apple TV compatibility in the source code or documentation.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}