Let us start by being precise about the word in that title, because for a React Face Filters SDK it is the word most likely to mislead. What we publish alongside the SDK is companion source code: a reference React integration layer, structured to be productized rather than read once and abandoned. It is not a rewrite of the engine, it is not a distributable package pulled from a registry, and it carries…
“Open source” attached to a face beauty SDK usually means one of two very different things, and conflating them wastes everybody’s time. Either the processing core is published — which for a commercial imaging engine is rare — or the integration layer around it is published, so teams can see how a real product wires up sessions, preview surfaces, and look selection. We did the second. Saying so plainly beats letting people…
Titles containing “open source” tend to promise more than a vendor intends. This one deserves a plain statement in the first paragraph, so nobody has to infer it: We did not open-source the engine. What we publish alongside the SDK is companion source code — a reference React integration layer — structured to be productized rather than read once and abandoned. It is not a rewrite of the engine, and…
Every team building a React video editing SDK faces the same architectural fork: either you re-implement editing in JavaScript on top of canvas and the platform media APIs, or you let a native engine do the rendering and write React for everything above it. Most teams start out re-implementing editing in JavaScript, and we did too, before settling where we are now. This is the engineering story of what we actually built…