expo-pro-video-editor 0.1.0

package/.prettierrc

@@ -0,0 +1,8 @@
+{
+  "printWidth": 100,
+  "tabWidth": 2,
+  "singleQuote": true,
+  "bracketSameLine": true,
+  "trailingComma": "es5",
+  "jsxSingleQuote": false,
+}

package/LICENSE

@@ -0,0 +1,67 @@
+BSD 3-Clause License
+
+Copyright (c) 2026, manuel2u
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+1. Redistributions of source code must retain the above copyright notice, this
+   list of conditions and the following disclaimer.
+
+2. Redistributions in binary form must reproduce the above copyright notice,
+   this list of conditions and the following disclaimer in the documentation
+   and/or other materials provided with the distribution.
+
+3. Neither the name of the copyright holder nor the names of its
+   contributors may be used to endorse or promote products derived from
+   this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
+CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
+OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
+OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+---
+
+Portions of this software (native iOS/Android video composition logic under
+ios/ and android/) are adapted from the pro_video_editor project:
+
+  https://github.com/hm21/pro_video_editor
+
+  BSD 3-Clause License
+
+  Copyright (c) 2025, Alex Frei
+
+  Redistribution and use in source and binary forms, with or without
+  modification, are permitted provided that the following conditions are met:
+
+  1. Redistributions of source code must retain the above copyright notice,
+     this list of conditions and the following disclaimer.
+
+  2. Redistributions in binary form must reproduce the above copyright
+     notice, this list of conditions and the following disclaimer in the
+     documentation and/or other materials provided with the distribution.
+
+  3. Neither the name of the copyright holder nor the names of its
+     contributors may be used to endorse or promote products derived from
+     this software without specific prior written permission.
+
+  THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+  AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+  IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+  ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE
+  LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
+  CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
+  SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
+  INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
+  CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
+  ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
+  POSSIBILITY OF SUCH DAMAGE.
+
+See NOTICE.md for a per-file breakdown of adapted vs. original code.

package/NOTICE.md

@@ -0,0 +1,250 @@
+# Third-Party Notices
+
+This package's native video composition engine (trim, color filters, image/GIF
+overlays, audio mixing, transitions, thumbnail/waveform generation) is adapted
+from [`pro_video_editor`](https://github.com/hm21/pro_video_editor) by Alex
+Frei, licensed under BSD-3-Clause. See `LICENSE` for the full original license
+text alongside this package's own.
+
+`pro_video_editor` is a Flutter plugin. Its Dart-facing API and Flutter
+plugin-registration glue (`MethodChannel`/`Pigeon`/`EventChannel` boundary
+code) do not apply to this package and were not reused — this package
+implements its own JS-facing API via the Expo Modules API. The native
+iOS (Swift/AVFoundation) and Android (Kotlin/Media3 Transformer) composition
+logic underneath that boundary — the actual video-processing implementation —
+is what this package adapts.
+
+As the port progresses, this file will track which native source files were
+adapted from `pro_video_editor` versus written new for this package, so the
+attribution stays accurate and specific rather than a blanket claim over the
+whole codebase.
+
+## iOS — adapted from `pro_video_editor`
+
+| This package | `pro_video_editor` source | Notes |
+| --- | --- | --- |
+| `ios/src/shared/EncodedImage.swift` | `darwin/.../shared/core/models/EncodedImage.swift` | `FlutterStandardTypedData` unwrap removed — Expo Modules API bridges JS binary data to `Data` directly. |
+| `ios/src/features/render/models/VideoClip.swift` | `darwin/.../render/models/VideoClip.swift` | Verbatim; doc comments referencing "the platform channel" reworded to "the JS boundary". |
+| `ios/src/features/render/models/VideoCompositorConfig.swift` | `darwin/.../render/models/VideoCompositorConfig.swift` | Verbatim, no changes. |
+| `ios/src/features/render/models/RenderConfig.swift` | `darwin/.../render/models/RenderConfig.swift` | `#if os(macOS) import FlutterMacOS #else import Flutter #endif` guard removed — unused by the file's actual logic. |
+| `ios/src/shared/LoggingConstants.swift` | `darwin/.../shared/core/constants/LoggingConstants.swift` | Verbatim; package tag renamed `ProVideoEditor` → `ExpoProVideoEditor`. |
+| `ios/src/shared/PluginLog.swift` | `darwin/.../shared/logging/PluginLog.swift` | Verbatim logic; doc comments referencing "Dart"/"Flutter"/the platform-channel log level reworded for a JS/Expo audience. |
+| `ios/src/features/render/helpers/ApplyRotation.swift` | `darwin/.../render/helpers/ApplyRotation.swift` | Verbatim, no changes. |
+| `ios/src/features/render/helpers/ApplyFlip.swift` | `darwin/.../render/helpers/ApplyFlip.swift` | Verbatim, no changes. |
+| `ios/src/features/render/helpers/ApplyCrop.swift` | `darwin/.../render/helpers/ApplyCrop.swift` | Verbatim, no changes. |
+| `ios/src/features/render/helpers/ApplyScale.swift` | `darwin/.../render/helpers/ApplyScale.swift` | Verbatim, no changes. |
+| `ios/src/features/render/helpers/ApplyBitrate.swift` | `darwin/.../render/helpers/ApplyBitrate.swift` | Verbatim, no changes. |
+| `ios/src/features/render/helpers/ApplyPlaybackSpeed.swift` | `darwin/.../render/helpers/ApplyPlaybackSpeed.swift` | Verbatim, no changes. References `CustomVideoCompositionInstruction`, ported separately. |
+| `ios/src/features/render/helpers/ApplyBlur.swift` | `darwin/.../render/helpers/ApplyBlur.swift` | Verbatim, no changes. |
+| `ios/src/features/render/helpers/ApplyColorMatrix.swift` | `darwin/.../render/helpers/ApplyColorMatrix.swift` | Verbatim, no changes. |
+| `ios/src/features/render/helpers/MediaInfoExtractor.swift` | `darwin/.../render/helpers/MediaInfoExtractor.swift` | Verbatim, no changes. |
+| `ios/src/features/render/helpers/DecodeOrientedImage.swift` | `darwin/.../render/helpers/DecodeOrientedImage.swift` | Verbatim; one doc comment mentioning "the plugin" reworded to "the module". |
+| `ios/src/features/render/helpers/ApplyAnimation.swift` | `darwin/.../render/helpers/ApplyAnimation.swift` | Verbatim, no changes. |
+| `ios/src/features/render/helpers/ApplyImageLayer.swift` | `darwin/.../render/helpers/ApplyImageLayer.swift` | Verbatim, no changes. |
+| `ios/src/features/render/utils/VideoCompositor.swift` | `darwin/.../render/utils/VideoCompositor.swift` | Verbatim; one doc comment referencing Flutter's `Transform.rotate` reworded to a framework-neutral description of the same clockwise-rotation convention. |
+| `ios/src/features/render/helpers/ApplyChromaKey.swift` | `darwin/.../render/helpers/ApplyChromaKey.swift` | Verbatim, no changes. |
+| `ios/src/features/render/helpers/ClipTransitionGeometry.swift` | `darwin/.../render/helpers/ClipTransitionGeometry.swift` | Verbatim, no changes. |
+| `ios/src/features/render/helpers/ClipTransitionRenderer.swift` | `darwin/.../render/helpers/ClipTransitionRenderer.swift` | Verbatim, no changes. References `ExportSessionDriver`, ported separately. |
+| `ios/src/shared/ExportGate.swift` | `darwin/.../shared/concurrency/ExportGate.swift` | Verbatim, no changes. |
+| `ios/src/shared/ExportSessionGuard.swift` | `darwin/.../shared/concurrency/ExportSessionGuard.swift` | Verbatim; one doc comment referencing "the plugin" reworded to "the module". |
+| `ios/src/shared/ExportWatchdog.swift` | `darwin/.../shared/concurrency/ExportWatchdog.swift` | Verbatim, no changes. |
+| `ios/src/shared/ExportSessionDriver.swift` | `darwin/.../shared/concurrency/ExportSessionDriver.swift` | Verbatim; one doc comment referencing "the plugin" reworded to "the module". (Initially missed in the first pass — caught by the compile-check step, see below.) |
+| `ios/src/features/render/RenderVideo.swift` | `darwin/.../render/RenderVideo.swift` | Verbatim, no changes — this file already exposes a plain Swift closure API (`onProgress`/`onComplete`/`onError`), with no Flutter dependency at all. The Flutter-specific glue lives one layer up, in `ProVideoEditorPlugin.swift`, which is not being ported (see below). |
+| — (not ported) | `darwin/.../shared/core/models/RenderTask.swift` | Deliberately **not** ported. This class exists only to adapt `RenderVideo`'s plain-closure callbacks into Flutter's `FlutterResult`/`FlutterError` method-channel convention. Expo Modules API's `AsyncFunction` (`async throws -> T`) already does this adaptation natively — resolving/rejecting the JS Promise — so this package's own module-glue layer (still to be written) replaces `RenderTask` directly rather than porting a Flutter-shaped wrapper and re-wrapping it again. |
+| `ios/src/features/render/utils/VideoMimeUtils.swift` | `darwin/.../render/utils/VideoMimeUtils.swift` | Verbatim, no changes. |
+| `ios/src/features/render/helpers/BitrateCapPolicy.swift` | `darwin/.../render/helpers/BitrateCapPolicy.swift` | Verbatim, no changes. |
+| `ios/src/features/render/helpers/TrackEndTrimmer.swift` | `darwin/.../render/helpers/TrackEndTrimmer.swift` | Verbatim, no changes. |
+| `ios/src/features/render/helpers/VideoTranscoder.swift` | `darwin/.../render/helpers/VideoTranscoder.swift` | Verbatim, no changes. |
+| `ios/src/features/render/helpers/BitrateCappedExporter.swift` | `darwin/.../render/helpers/BitrateCappedExporter.swift` | Verbatim; internal `DispatchQueue` labels renamed from `ch.waio.pro_video_editor.*` to `dev.expo.provideoeditor.*` (cosmetic — queue labels are diagnostic strings only, not a functional dependency). |
+| `ios/src/features/render/helpers/AudioSequenceBuilder.swift` | `darwin/.../render/helpers/AudioSequenceBuilder.swift` | Verbatim, no changes. |
+| `ios/src/features/render/helpers/AudioPreRenderer.swift` | `darwin/.../render/helpers/AudioPreRenderer.swift` | Verbatim, no changes. |
+| `ios/src/features/render/helpers/AudioReverser.swift` | `darwin/.../render/helpers/AudioReverser.swift` | Verbatim, no changes. |
+| `ios/src/features/render/helpers/VideoSequenceBuilder.swift` | `darwin/.../render/helpers/VideoSequenceBuilder.swift` | Verbatim, no changes. Also carries `VideoCompositionData`, `LayerPlacement`, and `CustomVideoCompositionInstruction`, which live in this same source file upstream. |
+| `ios/src/features/render/helpers/CompositionBuilder.swift` | `darwin/.../render/helpers/CompositionBuilder.swift` | Verbatim, no changes. |
+| `ios/src/features/render/helpers/ApplyComposition.swift` | `darwin/.../render/helpers/ApplyComposition.swift` | Verbatim, no changes. |
+| `ios/src/features/render/helpers/LayeredCompositionBuilder.swift` | `darwin/.../render/helpers/LayeredCompositionBuilder.swift` | Verbatim, no changes. |
+
+## iOS port status
+
+All 37 native source files that `RenderVideo.render(...)` transitively depends
+on have been ported (models, the full composition pipeline — single-track and
+layered — every effect helper, transitions, audio pre-render/reverse/mix, the
+bitrate-capped exporter, and the concurrency/export-safety layer). None of
+them had any real Flutter dependency once traced past their imports — the only
+two that did (`EncodedImage`'s byte-unwrap, and `RenderTask`, not ported at
+all) are noted above.
+
+**Verified**: the full set compiles cleanly as the `ExpoProVideoEditor` pod
+target (`xcodebuild ... -scheme ExpoProVideoEditor -sdk iphonesimulator build`
+→ `BUILD SUCCEEDED`) against the example app. Nothing is wired up to JS yet —
+this only confirms the native composition engine itself is complete and
+self-consistent.
+
+## iOS module glue (JS-callable)
+
+`ExpoProVideoEditorModule.swift` now exposes `render(config, id)` and
+`cancelRender(id)` as `AsyncFunction`s, plus an `onRenderProgress` event —
+the Expo Modules API equivalent of what `ProVideoEditorPlugin.swift`'s
+`renderVideo`/`cancelTask` method-channel handlers and `RenderTask` did for
+Flutter. Not a line-for-line port (there's no Flutter plugin file to adapt
+here): `AsyncFunction`'s `Promise` argument replaces `RenderTask`'s manual
+`FlutterResult` storage/dedup, and `Module.sendEvent` replaces the
+`FlutterEventChannel`/`StreamHandler` progress-streaming plumbing — both
+handled natively by Expo instead.
+
+The render config crosses the JS boundary as a **raw dictionary** (`[String:
+Any]` on the Swift side, a plain object in TS — see `src/ExpoProVideoEditor.types.ts`),
+handed straight to the already-ported `RenderConfig.fromArguments(_:)`
+unchanged, rather than re-modeling `RenderConfig`'s large/deeply-nested shape
+as a second parallel tree of Expo `Record` structs.
+
+**Verified**: compiles clean as part of the same `ExpoProVideoEditor` pod
+target build; `tsc --noEmit` and `eslint` both clean on the TS side.
+
+**Verified at runtime** on the iOS simulator via the example app's smoke-test
+screen: download a small public clip to a local file, `render()` a 3-second
+trim, resolve real output bytes (~1.9MB from a 5s/1.1MB source). This also
+caught and fixed a real bug — every error this module threw (not just render
+failures) was reaching JS as the literal string `"undefined reason"` instead
+of its actual message, because `Exception`'s JS-visible message reads its
+`reason` property (always `debugDescription`), not the `description` passed
+to `Exception(name:description:code:)`. Fixed by subclassing `Exception` to
+override `reason` — see the `fix(ios)` commit for detail.
+
+## Android — adapted from `pro_video_editor`
+
+| This package | `pro_video_editor` source | Notes |
+| --- | --- | --- |
+| `android/.../src/core/constants/LoggingConstants.kt` | `android/.../src/core/constants/LoggingConstants.kt` | Only `RENDER_TAG` ported (render scope only); tag renamed `ProVideoEditor` → `ExpoProVideoEditor`. Upstream declares this in Kotlin's default package; given an explicit package here (see below). |
+| `android/.../src/shared/logging/PluginLog.kt` | `android/.../src/shared/logging/PluginLog.kt` | Verbatim logic; the reflective `BuildConfig` class lookup repointed at this package's own `BuildConfig`; doc comments referencing "Dart"/"Flutter" reworded for a JS/Expo audience. |
+| `android/.../src/shared/concurrency/ExportGate.kt` | `android/.../src/shared/concurrency/ExportGate.kt` | Verbatim; doc comments reworded ("the split and render pipelines" → "the render pipeline", "the MethodChannel handler" → "the Expo Modules API's `AsyncFunction` handler"). Carries `ExportGateGuard` in the same file, same as upstream. |
+| `android/.../src/shared/media/EncodedImage.kt` | `android/.../src/shared/media/EncodedImage.kt` | Verbatim logic; doc comments referencing "the method channel"/"Dart" reworded to "the JS boundary". |
+| `android/.../src/shared/media/PcmRangeDecoder.kt` | `android/.../src/shared/media/PcmRangeDecoder.kt` | Verbatim, no changes. |
+| `android/.../src/shared/media/ImageOrientation.kt` | `android/.../src/shared/media/ImageOrientation.kt` | Verbatim, no changes. |
+| `android/.../src/features/render/models/RenderConfig.kt` | `android/.../src/features/render/models/RenderConfig.kt` | `fromMethodCall(call: MethodCall)` replaced with `fromArguments(args: Map<String, Any?>)`, reading the same fields directly off the map instead of through `call.argument<T>(key)` — the Kotlin equivalent of the iOS port's `fromMethodCall` → `fromArguments` adaptation. Carries `TransitionConfig`, `VideoClip`, `SegmentTransformConfig`, `LayerConfig`, `CompositionConfig`, `ColorFilterConfig`, `ChromaKeyConfig`, `AudioTrackConfig`, `LayerAnimationConfig`, `ImageLayer` in the same file, same as upstream. |
+| `android/.../src/features/render/models/RenderJobHandle.kt` | `android/.../src/features/render/models/RenderJobHandle.kt` | Verbatim, no changes. |
+| `android/.../src/features/render/models/CodecResourceExhaustedException.kt` | `android/.../src/features/render/models/CodecResourceExhaustedException.kt` | Verbatim, no changes. |
+| `android/.../src/features/render/models/VideoEncoderConfigurationException.kt` | `android/.../src/features/render/models/VideoEncoderConfigurationException.kt` | Verbatim; one doc comment referencing "the Flutter layer" reworded to "this module". |
+| `android/.../src/features/render/utils/VideoMimeUtils.kt` | `android/.../src/features/render/utils/VideoMimeUtils.kt` | Verbatim, no changes. Upstream declares this in Kotlin's default package; given an explicit package here. |
+| `android/.../src/features/render/utils/RotatedVideoDimensions.kt` | `android/.../src/features/render/utils/RotatedVideoDimensions.kt` | Verbatim, no changes. |
+| `android/.../src/features/render/EffectsProcessor.kt` | `android/.../src/features/render/utils/EffectsProcessor.kt` | Verbatim logic; moved to match its own declared package (`...features.render`, not `...features.render.utils` — an upstream directory/package mismatch, not preserved here). |
+| `android/.../src/features/render/helpers/ApplyRotation.kt` | `android/.../src/features/render/helpers/ApplyRotation.kt` | Verbatim logic. Upstream default-package file; given an explicit package plus an added `RENDER_TAG` import. |
+| `android/.../src/features/render/helpers/ApplyFlip.kt` | `android/.../src/features/render/helpers/ApplyFlip.kt` | Same treatment as `ApplyRotation.kt`. |
+| `android/.../src/features/render/helpers/ApplyScale.kt` | `android/.../src/features/render/helpers/ApplyScale.kt` | Same treatment as `ApplyRotation.kt`. |
+| `android/.../src/features/render/helpers/ApplyFrameRate.kt` | `android/.../src/features/render/helpers/ApplyFrameRate.kt` | Same treatment as `ApplyRotation.kt`. |
+| `android/.../src/features/render/helpers/ApplyPlaybackSpeed.kt` | `android/.../src/features/render/helpers/ApplyPlaybackSpeed.kt` | Same treatment as `ApplyRotation.kt`. |
+| `android/.../src/features/render/helpers/ApplyBlur.kt` | `android/.../src/features/render/helpers/ApplyBlur.kt` | Same treatment as `ApplyRotation.kt`. |
+| `android/.../src/features/render/helpers/ApplyColorMatrix.kt` | `android/.../src/features/render/helpers/ApplyColorMatrix.kt` | Same treatment as `ApplyRotation.kt`, plus its `ColorFilterConfig` import repointed at `RenderConfig.kt`. |
+| `android/.../src/features/render/helpers/ApplyBitrate.kt` | `android/.../src/features/render/helpers/ApplyBitrate.kt` | Same treatment as `ApplyRotation.kt`. Carries `BitrateChoice` in the same file, same as upstream. |
+| `android/.../src/features/render/helpers/ApplyCrop.kt` | `android/.../src/features/render/helpers/ApplyCrop.kt` | Same treatment as `ApplyRotation.kt`. |
+| `android/.../src/features/render/helpers/ApplyOpacity.kt` | `android/.../src/features/render/helpers/ApplyOpacity.kt` | Same treatment as `ApplyRotation.kt`. |
+| `android/.../src/features/render/helpers/ApplyChromaKey.kt` | `android/.../src/features/render/helpers/ApplyChromaKey.kt` | Upstream default-package file; given an explicit package plus `RENDER_TAG` and `ChromaKeyConfig` imports (the latter now in `RenderConfig.kt`). References `ChromaKeyEffect`, ported separately. |
+| `android/.../src/features/render/helpers/ChromaKeyMath.kt` | `android/.../src/features/render/helpers/ChromaKeyMath.kt` | Verbatim logic; `ChromaKeyConfig` import repointed at `RenderConfig.kt`. |
+| `android/.../src/features/render/helpers/ChromaKeyEffect.kt` | `android/.../src/features/render/helpers/ChromaKeyEffect.kt` | Verbatim logic; imports repointed (`RENDER_TAG`, `ChromaKeyConfig`, `ImageOrientation`). |
+| `android/.../src/features/render/helpers/ApplyAnimation.kt` | `android/.../src/features/render/helpers/ApplyAnimation.kt` | Verbatim, no changes. Carries `SlideOffset`, `OverlayAnchors`, `AnimatedBitmapOverlay`, and the `applyEasing`/`slideOffset`/`resolveAnchor` helpers, same as upstream. |
+| `android/.../src/features/render/helpers/ApplyImageLayer.kt` | `android/.../src/features/render/helpers/ApplyImageLayer.kt` | Verbatim logic; `RENDER_TAG` import added. Carries `applyTimedImageLayers`, `resolveOpenEndedOutAnimations`, `overlayDecodeSize`, and the bitmap-prep/rotate/unpremultiply helpers, same as upstream. |
+| `android/.../src/features/render/helpers/ApplyClipTransition.kt` | `android/.../src/features/render/helpers/ApplyClipTransition.kt` | Verbatim, no changes. Carries `ClipFadeOverlay`. |
+| `android/.../src/features/render/helpers/GifDecoder.kt` | `android/.../src/features/render/helpers/GifDecoder.kt` | Verbatim, no changes. |
+| `android/.../src/features/render/helpers/ClipTransitionGeometry.kt` | `android/.../src/features/render/helpers/ClipTransitionGeometry.kt` | Verbatim, no changes. |
+| `android/.../src/features/render/helpers/ClipTransitionRenderer.kt` | `android/.../src/features/render/helpers/ClipTransitionRenderer.kt` | Verbatim logic; `RENDER_TAG` import added. |
+| `android/.../src/features/render/helpers/VideoEncoderConfig.kt` | `android/.../src/features/render/helpers/VideoEncoderConfig.kt` | Verbatim, no changes. |
+| `android/.../src/features/render/helpers/VideoGlobalTrimCalculator.kt` | `android/.../src/features/render/helpers/VideoGlobalTrimCalculator.kt` | Verbatim, no changes. |
+| `android/.../src/features/render/helpers/VideoTimelineDurationCalculator.kt` | `android/.../src/features/render/helpers/VideoTimelineDurationCalculator.kt` | Verbatim, no changes. |
+| `android/.../src/features/render/helpers/BitrateCapPolicy.kt` | `android/.../src/features/render/helpers/BitrateCapPolicy.kt` | Verbatim, no changes. |
+| `android/.../src/features/render/helpers/EncoderFailureClassifier.kt` | `android/.../src/features/render/helpers/EncoderFailureClassifier.kt` | Verbatim, no changes. |
+| `android/.../src/features/render/helpers/ResilientVideoEncoderFactory.kt` | `android/.../src/features/render/helpers/ResilientVideoEncoderFactory.kt` | Verbatim logic; `RENDER_TAG` import added, `BitrateChoice`/`resolveBitrateSettings` bare imports dropped now that both are same-package. |
+| `android/.../src/features/render/helpers/MediaInfoExtractor.kt` | `android/.../src/features/render/helpers/MediaInfoExtractor.kt` | Verbatim logic; `RENDER_TAG` import added. |
+| `android/.../src/features/render/helpers/ConfigurableInAppMp4Muxer.kt` | `android/.../src/features/render/helpers/ConfigurableInAppMp4Muxer.kt` | Verbatim, no changes (`androidx.media3.common.Metadata` is a Media3 class, unrelated to this package). |
+| `android/.../src/features/render/helpers/VolumeAudioProcessor.kt` | `android/.../src/features/render/helpers/VolumeAudioProcessor.kt` | Verbatim logic; `RENDER_TAG` import added. |
+| `android/.../src/features/render/helpers/VolumeControlAudioMixer.kt` | `android/.../src/features/render/helpers/VolumeControlAudioMixer.kt` | Verbatim logic; `RENDER_TAG` import added. |
+| `android/.../src/features/render/helpers/AudioSequenceBuilder.kt` | `android/.../src/features/render/helpers/AudioSequenceBuilder.kt` | Verbatim logic; `RENDER_TAG` import added. |
+| `android/.../src/features/render/helpers/AudioPreRenderer.kt` | `android/.../src/features/render/helpers/AudioPreRenderer.kt` | Verbatim logic; `RENDER_TAG`/`PcmRangeDecoder` imports repointed. |
+| `android/.../src/features/render/helpers/VideoReverser.kt` | `android/.../src/features/render/helpers/VideoReverser.kt` | Verbatim, no changes beyond the `RENDER_TAG` import. |
+| `android/.../src/features/render/helpers/VideoTranscoder.kt` | `android/.../src/features/render/helpers/VideoTranscoder.kt` | Verbatim logic; `RENDER_TAG` import added. |
+| `android/.../src/features/render/helpers/VideoCompositionTransformation.kt` | `android/.../src/features/render/helpers/VideoCompositionTransformation.kt` | Verbatim; one doc comment referencing "the Flutter side" reworded to "the JS side". |
+| `android/.../src/features/render/helpers/VideoSequenceBuilder.kt` | `android/.../src/features/render/helpers/VideoSequenceBuilder.kt` | Verbatim logic; imports repointed (`RENDER_TAG`, `applyChromaKey`, `applyScale`, and the `models`/`utils`/`shared` cross-package imports). Carries `ImageLayerConfig` and `CropConfig` nested types, same as upstream. |
+| `android/.../src/features/render/helpers/CompositionBuilder.kt` | `android/.../src/features/render/helpers/CompositionBuilder.kt` | Verbatim logic; `RENDER_TAG`/`AudioTrackConfig`/`RenderConfig` imports repointed. |
+| `android/.../src/features/render/helpers/ApplyComposition.kt` | `android/.../src/features/render/helpers/ApplyComposition.kt` | Verbatim logic; `RenderConfig` import repointed. Carries `CompositionResult`, same as upstream. |
+| `android/.../src/features/render/helpers/LayeredCompositionBuilder.kt` | `android/.../src/features/render/helpers/LayeredCompositionBuilder.kt` | Verbatim logic; imports repointed (`RENDER_TAG`, `applyChromaKey`, and the `models` cross-package imports). |
+| `android/.../src/features/render/RenderVideo.kt` | `android/.../src/features/render/RenderVideo.kt` | Verbatim logic; imports repointed (`RENDER_TAG`, `mapFormatToMimeType`, and every `models`/`helpers`/`shared` cross-package import); one doc comment referencing "the Flutter layer" reworded to "this module". Already exposes a plain Kotlin callback API (`onProgress`/`onComplete`/`onError`) with no Flutter dependency at all — the Flutter-specific glue lives one layer up, in `ProVideoEditorPlugin.kt`, which is not being ported (see below). |
+| — (not ported) | `android/.../src/features/render/models/RenderTask.kt` | Deliberately **not** ported — same rationale as iOS's `RenderTask.swift`: this class only adapts `RenderVideo`'s plain-callback API into Flutter's method-channel `Result`/error convention, which Expo's `AsyncFunction`/`Promise` already does natively. |
+
+## Android port status
+
+All 45 native source files that `RenderVideo.render(...)` transitively depends
+on have been ported (models, the full composition pipeline — single-track and
+layered — every effect helper, transitions, audio pre-render/reverse/mix, the
+resilient encoder factory, and the concurrency/logging/media shared layer).
+None had any real Flutter dependency once traced past their imports — the only
+one that did (`RenderConfig.fromMethodCall`, and `RenderTask.kt`, not ported at
+all) is noted above. A handful of files (`ApplyAnimation`, `ApplyClipTransition`,
+`ApplyCrop`, `ApplyImageLayer`, `ApplyOpacity`, `GifDecoder`, `ApplyComposition`)
+were missed in the first dependency-discovery pass — same-package references
+with no `import` line are invisible to an import-based scan — and were caught
+by the compile-check step below, the same role the missing `ExportSessionDriver.swift`
+played on iOS.
+
+Roughly a third of upstream's `helpers/` files (`ApplyRotation`, `ApplyFlip`,
+`ApplyScale`, `ApplyFrameRate`, `ApplyPlaybackSpeed`, `ApplyBlur`,
+`ApplyChromaKey`, `ApplyColorMatrix`, `ApplyBitrate`, `ApplyCrop`,
+`ApplyOpacity`, `VideoMimeUtils`) declare no package at all upstream (Kotlin's
+default/unnamed package), relying on that for same-package access to
+`RENDER_TAG` and each other despite living in nested directories — an upstream
+inconsistency, not preserved here. Every ported file gets an explicit package
+matching its destination directory, with whatever new imports that requires.
+
+**Verified**: the full set compiles cleanly via
+`./gradlew :expo-pro-video-editor:compileDebugKotlin` (`BUILD SUCCESSFUL`)
+against the example app's generated Android project. Only pre-existing
+upstream deprecation warnings surface (`SpeedChangeEffect`,
+`EditedMediaItemSequence.Builder(vararg)`, `Movie`) — none introduced by the
+port.
+
+**Verified at runtime** on an Android emulator (API 36, Pixel 7) via the same
+smoke-test screen used for iOS: download a small public clip, `render()` a
+3-second trim, resolve real output bytes (~1.08MB from the same 5s/1.1MB
+source). This caught a real bug on the first attempt — see the module glue
+section below.
+
+## Android module glue (JS-callable)
+
+`ExpoProVideoEditorModule.kt` exposes `render(config, id)` and `cancelRender(id)`
+as `AsyncFunction`s (Kotlin's explicit-`Promise`-parameter form, matching
+`ExpoProVideoEditorModule.swift`'s pattern) plus an `onRenderProgress` event —
+the same role `ProVideoEditorPlugin.kt`'s `renderVideo`/`cancelTask`
+method-channel handlers and `RenderTask.kt` played for Flutter. Kotlin's
+`CodedException` needed no `Exception.reason`-style workaround: unlike iOS's
+`Exception`, whose JS-visible message reads a separate `reason` property (see
+the iOS `fix(ios)` commit), `CodedException`'s `message` constructor argument
+is exactly what reaches JS.
+
+The render config crosses the JS boundary as a **raw map** (`Map<String,
+Any?>` on the Kotlin side, a plain object in TS), handed straight to the
+already-ported `RenderConfig.fromArguments(_:)` unchanged — the same choice
+made on iOS, rather than re-modeling `RenderConfig`'s shape as a second
+parallel tree of Expo `Record` structs.
+
+**Verified**: compiles clean as part of the same
+`:expo-pro-video-editor:compileDebugKotlin` build, and confirmed working at
+runtime (see above) after one fix: Expo Modules API dispatches an
+`AsyncFunction` on a background queue by default, but Media3's `Transformer`
+requires every call — including `addListener`, invoked from `RenderVideo`'s
+own main-Looper `post` — on the exact thread that created it. Building the
+`Transformer` on the default background queue crashed the first render with
+`IllegalStateException: Transformer is accessed on the wrong thread` the
+moment the main-thread callback touched it. Fixed by chaining
+`.runOnQueue(Queues.MAIN)` onto both `AsyncFunction`s so the whole call stays
+on the single thread Media3 expects throughout — see the `fix(android)`
+commit for detail. No equivalent issue exists on iOS: `AVFoundation`'s
+`Transformer`-equivalent objects aren't thread-affine the same way, and the
+Expo Modules API's Swift side already runs `AsyncFunction` bodies
+consistently.
+
+## Remaining work
+
+The TS-facing API surface for anything beyond trim/basic effects (filters,
+image/text overlays, audio mixing, transitions) is modeled in `RenderConfig`
+on both platforms already and compiles, but only the trim path has been
+exercised at runtime so far on either platform — filters, image layers, audio
+mixing, and transitions are still untested end-to-end on iOS and Android
+alike.

package/README.md

@@ -0,0 +1,70 @@
+# expo-pro-video-editor
+
+A native video composition module for Expo/React Native — trim, crop, color
+filters, image/GIF/text overlays, and multi-track audio mixing, exported to a
+single video file.
+
+Built on the same native frameworks as any serious video editor: iOS uses
+`AVFoundation`/`AVMutableComposition` + `CoreImage`, Android uses
+`androidx.media3.transformer` + `MediaCodec`/`MediaMuxer`. No FFmpeg
+dependency (FFmpegKit, the library most RN video-processing packages relied
+on, was retired in 2025/2026), no paid SDK, no license fee.
+
+## Origin
+
+The native composition logic is adapted from
+[`pro_video_editor`](https://github.com/hm21/pro_video_editor), a Flutter
+plugin by Alex Frei that does the same job for Flutter apps via a
+`MethodChannel` bridge. Flutter and Expo/React Native don't share a plugin
+protocol, so that bridging layer can't be reused directly — but the actual
+video-processing code underneath it (AVFoundation compositions on iOS, Media3
+Transformer on Android) is plain native code that doesn't know or care which
+JS framework called it. This package keeps that native logic and replaces
+only the bridge with the Expo Modules API.
+
+See `LICENSE` and `NOTICE.md` for the full attribution — this is a BSD-3-Clause
+derivative work.
+
+## Status
+
+Early, in-progress port. Not yet published to npm. Track progress against
+`pro_video_editor`'s feature set in `NOTICE.md`.
+
+## Development
+
+This repo is a standard Expo native module layout:
+
+```
+src/       TypeScript API surface (what consumers import)
+ios/       Swift native implementation
+android/   Kotlin native implementation
+example/   A runnable Expo app for testing the module in isolation
+```
+
+### Running the example app
+
+```sh
+bun install
+cd example
+bun install
+bun ios      # or: bun android
+```
+
+`example/` autolinks this module from `..` (see `example/package.json`'s
+`expo.autolinking.nativeModulesDir`), so changes to `src/`, `ios/`, or
+`android/` are picked up without publishing anything.
+
+Beyond testing individual native features, `example/` also doubles as a
+staging ground for the actual clip-editor screen UI (trim scrubber, filter
+tray, text/sticker tool, audio picker) being built against the Shop Society
+Figma designs — proving the screen and the native module out together here,
+independent of `shop-society-mobile`'s app shell, before porting the finished
+screen over.
+
+### Scripts
+
+- `bun run build` — compile `src/` to `build/`
+- `bun run lint` — lint `src/`
+- `bun run test` — run tests
+- `bun run open:ios` / `bun run open:android` — open the example app's native
+  project in Xcode / Android Studio

package/android/build.gradle

@@ -0,0 +1,35 @@
+plugins {
+  id 'com.android.library'
+  id 'expo-module-gradle-plugin'
+}
+
+group = 'expo.modules.provideoeditor'
+version = '0.1.0'
+
+android {
+  namespace "expo.modules.provideoeditor"
+  defaultConfig {
+    versionCode 1
+    versionName "0.1.0"
+    minSdk 24
+  }
+  lintOptions {
+    abortOnError false
+  }
+}
+
+dependencies {
+  def media3_version = "1.10.1"
+  implementation "androidx.media3:media3-common:$media3_version"
+  implementation "androidx.media3:media3-transformer:$media3_version"
+  implementation "androidx.media3:media3-effect:$media3_version"
+  implementation "androidx.media3:media3-muxer:$media3_version"
+
+  // EXIF metadata for image-overlay orientation (ImageOrientation.kt).
+  // Preferred over android.media.ExifInterface: it covers HEIF/AVIF/WebP/PNG
+  // as well as JPEG.
+  implementation "androidx.exifinterface:exifinterface:1.4.2"
+
+  implementation "org.jetbrains.kotlinx:kotlinx-coroutines-android:1.7.3"
+  implementation "org.jetbrains.kotlinx:kotlinx-coroutines-core:1.7.3"
+}

package/android/src/main/AndroidManifest.xml

@@ -0,0 +1,2 @@
+<manifest>
+</manifest>

package/android/src/main/java/expo/modules/provideoeditor/ExpoProVideoEditorModule.kt

@@ -0,0 +1,163 @@
+package expo.modules.provideoeditor
+
+import androidx.media3.common.util.UnstableApi
+import expo.modules.kotlin.exception.CodedException
+import expo.modules.kotlin.functions.Queues
+import expo.modules.kotlin.modules.Module
+import expo.modules.kotlin.modules.ModuleDefinition
+import expo.modules.kotlin.Promise
+import expo.modules.provideoeditor.src.features.render.RenderVideo
+import expo.modules.provideoeditor.src.features.render.models.RenderConfig
+import expo.modules.provideoeditor.src.features.render.models.RenderJobHandle
+import expo.modules.provideoeditor.src.shared.logging.PluginLog
+
+@UnstableApi
+class ExpoProVideoEditorModule : Module() {
+  /**
+   * Active render jobs, keyed by the caller-supplied task id.
+   *
+   * Mirrors `ProVideoEditorPlugin.activeRenderTasks`: tracked so a second
+   * `render` call reusing the same `id` is rejected instead of silently
+   * racing another job, and so `cancelRender` can find the job to stop.
+   */
+  private val activeRenderHandles = mutableMapOf<String, RenderJobHandle>()
+
+  /**
+   * Whether the task for `id` was cancelled by an explicit `cancelRender`
+   * call, as opposed to a pipeline cancelling itself (a stalled-export
+   * watchdog, a refused start). Both surface the same way, but only the
+   * former is a genuine user-requested cancel.
+   */
+  private val explicitlyCancelled = mutableSetOf<String>()
+
+  override fun definition() = ModuleDefinition {
+    Name("ExpoProVideoEditor")
+
+    Events("onRenderProgress")
+
+    // Expo Modules API dispatches an AsyncFunction on a background queue by
+    // default. Media3's Transformer binds to whichever thread creates it and
+    // then requires every later call (including addListener from the
+    // RenderVideo pipeline's own main-Looper post) on that same thread — a
+    // Transformer built on the default background queue crashes the first
+    // time a main-thread callback touches it ("Transformer is accessed on the
+    // wrong thread"). Forcing this function onto the main queue keeps the
+    // whole render() call on the same thread Media3 expects throughout.
+    AsyncFunction("render") { args: Map<String, Any?>, id: String, promise: Promise ->
+      if (id.isEmpty()) {
+        promise.reject(ExpoProVideoEditorException.invalidArguments("Missing task id"))
+        return@AsyncFunction
+      }
+
+      if (activeRenderHandles.containsKey(id)) {
+        promise.reject(ExpoProVideoEditorException.taskAlreadyRunning(id))
+        return@AsyncFunction
+      }
+
+      val config: RenderConfig
+      try {
+        config = RenderConfig.fromArguments(args)
+      } catch (e: Exception) {
+        promise.reject(
+          ExpoProVideoEditorException.invalidArguments(
+            "Invalid render configuration: ${e.message}"
+          )
+        )
+        return@AsyncFunction
+      }
+
+      val context = appContext.reactContext
+      if (context == null) {
+        promise.reject(
+          ExpoProVideoEditorException.invalidArguments("Application context is not available")
+        )
+        return@AsyncFunction
+      }
+
+      sendEvent("onRenderProgress", mapOf("id" to id, "progress" to 0.0))
+
+      val renderVideo = RenderVideo(context)
+      val handle = renderVideo.render(
+        config = config,
+        onProgress = { progress ->
+          sendEvent("onRenderProgress", mapOf("id" to id, "progress" to progress))
+        },
+        onComplete = { outputData ->
+          sendEvent("onRenderProgress", mapOf("id" to id, "progress" to 1.0))
+          activeRenderHandles.remove(id)
+          explicitlyCancelled.remove(id)
+          promise.resolve(outputData)
+        },
+        onError = { error ->
+          PluginLog.e("ExpoProVideoEditor", "Render failed: ${error.message}", error)
+          activeRenderHandles.remove(id)
+          val wasCancelled = explicitlyCancelled.remove(id)
+          promise.reject(
+            ExpoProVideoEditorException.renderFailed(canceled = wasCancelled, error = error)
+          )
+        }
+      )
+
+      activeRenderHandles[id] = handle
+    }.runOnQueue(Queues.MAIN)
+
+    AsyncFunction("cancelRender") { id: String, promise: Promise ->
+      if (id.isEmpty()) {
+        promise.reject(ExpoProVideoEditorException.invalidArguments("Missing task id"))
+        return@AsyncFunction
+      }
+
+      val handle = activeRenderHandles[id]
+      if (handle == null) {
+        promise.reject(ExpoProVideoEditorException.taskNotFound(id))
+        return@AsyncFunction
+      }
+
+      explicitlyCancelled.add(id)
+      handle.cancel()
+      promise.resolve(null)
+    }.runOnQueue(Queues.MAIN)
+  }
+}
+
+/**
+ * Errors thrown across the JS boundary. Expo Modules API converts a thrown
+ * [CodedException] into a JS `Error` carrying `.code` and `.message` — the
+ * same shape iOS's `Exception` gives, and the same shape `FlutterError`'s
+ * `code`/`message` gave the Flutter side. Unlike iOS's `Exception` (whose
+ * JS-visible message reads a separate `reason` property, not the
+ * `description` an easy-to-reach initializer sets — see the iOS module's
+ * `fix(ios)` commit), `CodedException`'s `message` constructor argument is
+ * exactly what reaches JS, so no equivalent subclass trick is needed here.
+ */
+private class ExpoProVideoEditorException(
+  code: String,
+  message: String,
+  cause: Throwable? = null,
+) : CodedException(code, message, cause) {
+  companion object {
+    fun invalidArguments(message: String) =
+      ExpoProVideoEditorException("INVALID_ARGUMENTS", message)
+
+    fun taskAlreadyRunning(id: String) =
+      ExpoProVideoEditorException(
+        "TASK_ALREADY_RUNNING", "Task with id $id is already running"
+      )
+
+    fun taskNotFound(id: String) =
+      ExpoProVideoEditorException("TASK_NOT_FOUND", "No task found for id $id")
+
+    /**
+     * A pipeline can also cancel itself (a stalled-export watchdog, a refused
+     * start), so a bare cancellation-shaped failure is a cancellation even
+     * when `canceled` (an explicit `cancelRender` call) is false.
+     */
+    fun renderFailed(canceled: Boolean, error: Throwable): ExpoProVideoEditorException {
+      val isCancellation = error is java.util.concurrent.CancellationException
+      val code = if (canceled || isCancellation) "CANCELED" else "RENDER_ERROR"
+      return ExpoProVideoEditorException(
+        code, error.message ?: "Unknown render error", error
+      )
+    }
+  }
+}

package/android/src/main/java/expo/modules/provideoeditor/src/core/constants/LoggingConstants.kt

@@ -0,0 +1,4 @@
+package expo.modules.provideoeditor.src.core.constants
+
+const val PACKAGE_TAG = "ExpoProVideoEditor"
+const val RENDER_TAG = "$PACKAGE_TAG-Renderer"