Skip to content

3. defer watchOS support to a separate future plan

status

accepted

context

the app's requirements call for watches to be "first class citizens". Flutter runs natively on Wear OS (it's a regular Android app with extra manifest/gradle configuration), but Flutter's engine cannot run on watchOS at all - this is an Apple platform restriction, not a missing library. a real watchOS app requires a native SwiftUI/WatchKit target bridged to the Flutter iOS app via WatchConnectivity, which is an entirely separate codebase/skillset from the rest of this Flutter project.

decision

build and ship Wear OS support as part of this project's phased plan (phase 10). explicitly defer watchOS to a separate future plan/effort, so it isn't silently forgotten but also doesn't block or complicate the Flutter-only phases of this plan.

consequences

  • ios/ in this repository only contains the phone app; no watchOS target exists yet.
  • when watchOS work begins, expect: a new native SwiftUI watch target scaffolded under ios/, a WatchConnectivity bridge (conceptually similar to a method channel) to the Flutter iOS app, and a feature subset matching whatever Wear OS ships in phase 10.
  • see docs/dev-guide/PROJECT_PLAN.md's "Deferred: watchOS companion app" section for scope notes.