Image and video decision

CueCam

A technical user can reproduce the core teleprompter + recorder and basic on-device captions in a few weeks, but matching CueCam's full polish, cloud-powered gaze features, and distribution will be costly and time-consuming.

View on the App Store
You pay

Not priced

No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.

You’d pay instead

$100one-off92 h to build

$0/mo3 h/mo upkeep

No published price to break even against.

No open-source build does this yet

Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.

What a replacement has to do

  • Paste or type a script -> run teleprompter while recording video -> auto-generate captions -> edit and export.

What it still won’t have

  • Polish and UX refinements (smoothness, many edge-case bugfixes and quality-of-life tweaks).
  • Cloud-powered features (the listing references a cloud 'Eye Contact' feature for gaze correction).
  • App Store distribution history, ratings, and user acquisition channels.
  • Deep integration with device hardware and many export/share platform optimizations.

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

CueCam does not publish a price we could read, so there is nothing to compare against. What building costs is below.

Money you would actually spend

Keep paying
—

Subscription price × seats × 12

Build it
—

AI build —APIs + hosting —

Time you would spend

—

—

What you would spend

What we assumed

The verdict above measures whether you could build it. This one is only about money.

Runnable build prompt

Not run yet
Build an iOS teleprompter + video recorder/editor in Swift using AVFoundation, SwiftUI, and CoreML/Apple Speech frameworks. In scope: (1) Teleprompter UI supporting word-tracking via on-device Speech framework, fixed-speed scrolling, and timed pacing; (2) Camera capture with selectable resolution/frame-rate, audio routing, live waveform, and teleprompter overlay; (3) On-device auto-caption generation, caption timeline editor (drag/stretch caption blocks, split/delete, undo/redo); (4) Basic editor: trim, export presets (9:16,16:9,1:1,4:5), background blur/replace, watermark, and audio noise reduction; (5) Local browser remote (WebSocket or local HTTP) plus a minimal cloud relay endpoint for remote code-based control (host on a low-cost server). Out of scope: training or providing cloud ML models for gaze correction and any large-scale analytics backend. Deliverables: runnable Xcode project, unit/UI tests for critical flows, error handling for camera/permission failures, and CI build script.
How we checked1 sources · 3/3 runs agreed · evidence score 56

How the score was reached

  • Partly verdict base52
  • 3/3 assessment runs agreed+4
  • Evidence score56

The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.

How scoring works →

Cited sources · 1

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

✓ 3 independent runs, one answer✓ Citations limited to fetched pages! 1 moat recorded