Build or buy an in-app video editor: what it really takes

Someone on your team has written "add video editing" on the roadmap. Before anyone estimates it, it helps to know what users mean by those words and what each path costs your team. This is the build vs buy video editor decision, laid out for founders, CTOs and heads of product: the scope, what building it involves, the options in between, and what to check if you buy.

The question behind "add video editing"

"Add video editing" can mean a trim handle before upload, or it can mean the editor your users already know from the apps they edit in today. Those are very different projects, and the gap between them is where estimates go wrong.

So the useful first question isn't "how do we build it?" It's "what will our users do with it?" If they post a clip as recorded, a trimmer is enough. If they want to add text, captions, music, effects and a second clip, they expect a real editor, and they will compare yours with the one they already use.

What users expect from an in-app video editor

Here is the scope checklist. Each line is a feature users notice when it's missing:

• Timeline with several tracks: video, text, stickers, audio.
• Trim, split, reorder, speed on every clip.
• Text with fonts, styles and animation, placed and resized on the video.
• Captions timed to speech.
• Looks and effects: filters, colour adjustments, transitions between clips.
• Audio: music, voice, volume and fades.
• A live preview that matches the exported video exactly.
• Undo and redo for every action.
• Save and reopen a project, ideally on another device.
• Export to a file your app can save, share or upload, in the background.
• Every platform you ship: iOS, Android, and maybe web, behaving the same way.

And then your own layer on top: your brand, your media library, your wording, your languages.

Building it: what your team takes on

The platforms give you processing, not an editor. Apple describes AVFoundation as the framework to "work with audiovisual assets, control device cameras, process audio, and configure system audio interactions". Google describes Media3 Transformer as "an API for editing media, including converting between formats (transcoding), applying changes like trimming a clip from a longer video, cropping a portion of the video frame, applying custom effects, and other editing operations". In the browser, WebCodecs lets you "encode and decode video and audio" with per-frame control.

These are strong foundations. None of them is a timeline, a text panel, a caption editor or an undo stack. That part, the part users touch, is yours to design, build and keep working on every platform.

We know because we did it. Before Nitrakit, we built an in-app editor for iOS and Android the usual way, in 2022 and 2023. A few things we learned:

• The foundation decides what's possible. Our Android app was built on an open-source transcoding library that decoded clips one after another. Layering a second video on top (an overlay or picture-in-picture) needs several decoders running at once and every frame composited, which that library couldn't do. So video overlays didn't work.
• Preview and export drift apart. Preview and export ran on different pipelines, and what users saw on screen didn't always match the file they got. Two pipelines also means every fix has to be made twice.
• Two platforms, two results. We built two native apps, one for iOS and one for Android, and the same project didn't always come out the same on both.

None of this is a reason not to build. It's the work to budget for: a team that knows video, on every platform, for as long as the feature exists. Formats, OS versions and devices keep changing after launch.

Options short of a full build

There are honest middle paths, and each fits some apps:

• A trimmer. Platform APIs make trimming and basic transcoding approachable. If users only cut the start and end of a clip, this may be all you need. Plan for the day they ask for text and music.
• An open-source starting point. Libraries and sample apps can save weeks on the processing side. Check how active the project is, its licence terms for your app, and how much of the editor UI it actually includes. Usually you still own the timeline, panels, undo and saving.
• Send users to another app. They edit elsewhere and come back with a file. It costs you nothing to build. It also means users leave your app at the moment they're creating, and some don't come back to post.

Buying it: what to check in any video editor SDK

If you buy, the editor itself is the product you're evaluating. Questions worth asking any vendor, us included:

• Does it run on every platform you ship? iOS, Android, React Native or Flutter, web. One editor everywhere, or separate products with different features?
• Can it look like your app? Colours and fonts are the start. Can you hide tools, add your own, change every label, ship in your users' languages?
• Does it fit your stack? Where do media, fonts and music come from: your library and your storage, or theirs? Can a saved project reopen on another device?
• Does preview match export? Make an edit with text and effects, export it, compare.
• What does it add to your app? Ask for measured app size per platform.
• Where does it run? On the device, or on servers someone has to pay for?
• How is it licensed? Can you try everything before you pay? What changes when you release?
• Who do you talk to? When something breaks a week before launch, is there a person who knows the code?

Try the demo, then try it in your own app. A day with the SDK in your codebase tells you more than any feature table.

Build vs buy: a simple way to decide

No formula here, just questions to answer with your team:

1. Is video editing your product, or a feature of it? If editing itself is how you win, building may be right. If it supports what you sell, buying usually is.
2. Which platforms must it ship on, and at the same time? Each one multiplies the build.
3. Do you have people who've shipped video before? If not, you're also hiring.
4. What does the team stop building while it does this? That's the real cost.
5. Who maintains it in two years? The editor needs care as long as it exists.

If your answers point to "feature, several platforms, no video team", that's the case for buying. If they point to "editing is our product", build, and use the checklist above as your scope.

Where Nitrakit fits

Nitrakit is the buy option for teams whose product isn't video editing. It puts a complete video editor inside your app: timeline, real-time preview, effects, text and captions, audio, and export to MP4, on iOS (and macOS), Android, React Native including Expo, and the web with JavaScript, React, Vue, Svelte and Angular. The introduction lists what's included.

• Your brand. Theme, tools, icons, pickers, wording and languages are yours to set. See Customisation.
• Your stack. Projects store your own media ids, not files, so they sync through your backend and reopen on another device. See Projects and media.
• On the device. Editing and export run on the user's device or in the browser, with no servers to run for it. See Platform support.
• Checkable footprint. Measured sizes per platform are on the App size page.

To see what adding it looks like in code, read Add a video editor to your React Native app.

Try it before you decide

Open the live demo to use the editor in your browser. Then install the SDK and run it in your own app: it's free to build and test, and you need a license key when you release. Plans are on the pricing page, and teams getting ready to release can talk to us. Questions on the way? Ask on Discord.

Install the SDK