u/Due-Following-8455

I’m maintaining an open-source Swift/Metal project called Harbeth, and I’m trying to keep the public API focused on one job: GPU image and frame processing across Apple platforms.

The core idea is that common visual inputs should be able to enter the same Metal-backed processing flow:

• Image
• Texture
• Pixel buffer
• Sample buffer

The video I’m sharing is a short 25s overview. The main line is: “GPU image processing for every frame.”

Where I’d like feedback from Swift developers:

1. Should a processing library expose separate entry points for each input type, or is a unified routing API easier to reason about?
2. For camera preview / video frame use cases, what should the library own vs. what should stay in app code?
3. Are custom kernels and LUT pipelines enough as extension points, or would you expect a different plugin/filter model?

Important boundary: this is not a full camera SDK or video editing SDK. It’s intended to be the GPU processing core underneath those workflows.