buildOne report1 publisher ClearPix rebuilt its browser watermark remover on WebCodecs hardware codecs and MediaBunny muxing, cutting one job from 95 seconds to 9. The result comes from one job on the team's own Macs, and it holds only where the browser can reach a hardware H.264 encoder.
Reality
- Evidence38
- Adoption15
- Hype gap+20
- Incentives40
- Confidence42
buildOne report1 publisher Miraiclip takes edits only as dispatched commands, keeps a microsecond-precision timeline and a full history, and emits every change as an RFC-6902 JSON patch. Everything a user touches, you write yourself.
Reality
- Evidence34
- Adoption12
- Hype gap+12
- Incentives58
- Confidence44
buildOne report1 publisher A browser benchmark puts the platform encoder 7.5 to 10.1 times ahead of ffmpeg.wasm on an Apple M3, while the same code path runs about five times slower on a machine with no hardware AVC. On size, ffmpeg.wasm won.
Reality
- Evidence46
- Adoption22
- Hype gap+14
- Incentives55
- Confidence44
buildOne report1 publisher A dev.to walkthrough traces the tab crash to two optimization targets pointing opposite ways. The repair it proposes lands in every generative node rather than in the export button, which is where the adoption cost actually sits.
Reality
- Evidence26
- Adoption
- Insufficient
- Hype gap+44
- Incentives38
- Confidence44
buildOne report1 publisher Timeline Studio keeps project media in the tab, which relocates the hard problems: mixed WebGPU and WASM runtimes, pinned model mirrors, and an export that cannot just record the preview.
Reality
- Evidence30
- Adoption
- Insufficient
- Hype gap−5
- Incentives68
- Confidence34
buildOne report1 publisher WebCodecs and WebGPU can run demux, decode, effects and re-encode on the user's machine. The consequence is that your cost model turns into a capability-detection problem.
Reality
- Evidence28
- Adoption
- Insufficient
- Hype gap+52
- Incentives
- Insufficient
- Confidence26