Skip to content

PACKAGES-TO-IMPL.md

Latest commit

 

History

History
37 lines (25 loc) · 2.3 KB

PACKAGES-TO-IMPL.md

File metadata and controls

37 lines (25 loc) · 2.3 KB
Raw

Platform Views (Native View Embedding)

See TODO.md for full implementation plan covering:

  • PlatformView trait and PlatformViewRegistry in core
  • Android: JNI bridge, hybrid composition via FrameLayout, input forwarding, lifecycle
  • iOS: Obj-C bridge, UIView subview composition, input forwarding, lifecycle
  • TargetPlatform enum for runtime platform detection

Reference:

We implement the basic packages used in the apps in the src/packages module (e.g., src/packages/connectivity, src/packages/sensors, etc.). Feature-gate each package. Visit the GitHub repo of each package, review the source code, and implement the complete functionality. Also check the example code to understand usage. Implement in the following order of priority:

eg: src/packages/connectivity/mod.rs,android/,ios/ etc., we can have a common interface in mod.rs and platform-specific implementations in android/ and ios/ folders. The mod.rs file can use conditional compilation to include the appropriate platform-specific implementation based on the target platform. Create todos for each package implementation, and track progress in the TODO.md file.

  1. https://pub.dev/packages/geolocator in src/packages/location/
  2. https://pub.dev/packages/location in src/packages/location/
  3. https://pub.dev/packages/flutter_local_notifications in src/packages/notifications/
  4. https://pub.dev/packages/video_player in src/packages/video_player/
  5. https://pub.dev/packages/just_audio in src/packages/audio/

Tier 5 — Platform-Specific & UI Helpers

  1. https://pub.dev/packages/android_intent_plus
  2. https://pub.dev/packages/android_alarm_manager_plus
  3. https://pub.dev/packages/infinite_scroll_pagination

Rationale for ordering:

Tier 1 packages are dependencies or utilities that nearly every other package or feature relies on (storage, paths, app info, launching URLs). Tier 2 covers connectivity and location, which gate many runtime behaviors. Tier 3 adds the user-visible features people expect (notifications, sharing, media playback). Tier 4 is hardware access that's important but more niche. Tier 5 contains Android-only packages and a UI helper, which have the narrowest scope.