ReelFork

ReelFork is an AI-native platform for branching interactive video and short-form drama. Its product is split into two connected surfaces: ReelFork Studio, where creators build branching stories, and ReelFork Cinema, where audiences discover and watch them. Current first-party social material describes Studio as a creator workspace that can turn ideas, scripts, comics, existing videos and AI shorts into branching interactive stories, while Cinema is the viewing and discovery layer across Web, iOS and Android.¹

The core idea is structurally different from ordinary text-to-video. Instead of generating one linear clip, ReelFork treats a story as a graph of scenes and choices. The company's engineering blog documents RFD, a YAML-based branching-video format in which nodes represent scenes and references determine the next scene or choice target.² The format is designed to be diffable, generatable by an LLM and portable between a visual editor, scripts and version control. ReelFork's own story agent writes this structure directly, which makes the AI layer part of the narrative architecture rather than only an asset generator.²

Current third-party product descriptions consistently portray Studio as an agent-assisted workflow for script decomposition, storyboarding, image/video generation and branch organization on a visual canvas.³⁴ SmolLaunch describes the product as a no-code workflow from idea or source material through branching script, storyboard, video generation and one-click publishing.⁴ These directory descriptions are useful corroboration of current positioning but do not establish output quality.

The technical direction is unusually open for such a young creative product. ReelFork's engineering material says an RFD package is validated before publication: references must resolve, the start node must be reachable, at least one ending must be reachable and orphaned nodes are rejected.² A separate engineering post documents embedding an interactive player with an iframe, reinforcing that ReelFork is building a portable playback layer rather than only a closed creator interface.⁵

ReelFork Cinema is independently verifiable through Apple's App Store. The iOS app is an 18+ entertainment app for interactive dramas and conventional short-drama viewing. Current version history documents interactive choices, episode and series purchases, playback-speed controls, entitlement checks, guest previews, quality switching, offline-download and playback work, and a direct entry into ReelFork Studio from the profile area.⁶ The release history therefore confirms that Cinema is an operating distribution/commerce surface rather than only a concept page.

The consumer app also makes clear that ReelFork is not limited to interactive stories. Its current home filtering distinguishes Interactive, Series and Video content, and the app description emphasizes swipe-based discovery, recommendations, favorites, search and watch history.⁶ This broadens the distribution proposition but also means creator success depends partly on ReelFork's ability to build an audience, not just on Studio's creation tools.

An external June 2026 event report identifies the project as “入剧 ReelFork” from Shanghai Daidaluozhi Information Technology Co. and describes its product grammar as strong narrative structure, key-node interaction, limited free expression and multiple replayable endings, implemented through pre-generated video plus lightweight AI judgment.⁷ That is useful external identity/context evidence and supports the view that ReelFork is targeting scalable interactive narrative rather than open-ended conversational role-play.

Pricing is currently clearer for Cinema than for Studio. Apple's U.S. App Store lists ReelFork Cinema as free to download with in-app purchases. Current coin packs are $1.99 for 100 coins, $6.99 for 500, $12.99 for 1,000 and $69.99 for 5,000.⁶ These are consumer-content purchases inside Cinema; they should not be treated as creator-platform subscription prices.

For Studio, accessible public evidence is less precise. SmolLaunch describes ReelFork as “Free to start + paid plans,” and its launch page says early creators can receive generation credits and launch-program support.⁴ ReelFork's own LinkedIn post likewise mentions project credits and invite plans for early creators.¹ Neither accessible source provides a dependable current public table of Studio plan names, monthly prices, generation quotas or overage rates.

That opacity matters because AI video generation can be expensive and branch-heavy stories multiply asset count. A project with several choices can require many more scenes than a linear short of equivalent viewing length. Without a verified public Studio pricing schedule, value-for-money cannot be assessed simply from the existence of a free starting path.

Cinema's own monetization is more mature. The App Store release history documents single-episode unlocking and full-series purchases where supported, as well as entitlement and paid-viewing flows.⁶ That indicates a real consumer-commerce layer, but public evidence reviewed here does not establish the creator revenue split, payout thresholds, territory economics or whether Studio generation costs are offset against distribution revenue.

Creators evaluating ReelFork should therefore separate three economic questions: the cost of generating/producing in Studio, the cost or limits of hosting/distribution, and the monetization terms for paid viewing in Cinema. Public sources currently answer the third only partially and the first two inadequately. A serious commercial deployment should obtain current creator terms before committing production volume.

ReelFork is an unusually new product, and its evidence base reflects that. The strongest independently structured source is Apple's App Store, which confirms an operating ReelFork Cinema app, current version 2.0.2, in-app purchases, release history and a direct Studio entry.⁶ The U.S. listing currently shows 5.0/5 from one rating and one written review.⁶ That sample is far too small to support a stable numeric product rating.

The one App Store review is directionally useful because it discusses swipe-based short-drama viewing, speed controls, loading improvements and interactive-choice placement, but a single consumer review says almost nothing about Studio generation quality.⁶ The external evidence must therefore remain surface-specific: Cinema's mobile playback experience cannot be silently transferred to Studio's AI authoring quality.

Outside the reviewed source set, current product directories provide consistent feature descriptions but little independent testing. SmolLaunch has no reviews yet and only a few community points.⁴ Chuchuang describes the Studio/Cinema workflow and intended creator audiences but does not provide controlled output testing.³ Detailed AI-tool directories describe Story Agent, branch editing, interaction types and developer features, but their feature tables should be treated as discovery/corroboration rather than independent reliability evidence.⁸

The engineering blog is a stronger technical source because it exposes concrete implementation concepts. RFD's text-based structure, link validation and Git-friendly workflow are specific enough to evaluate as architecture rather than marketing.² They are still first-party claims about ReelFork's implementation, but they materially improve transparency around how branching content is represented and checked.

Privacy evidence is fragmented by surface. Apple's App Store says the iOS developer declares that the Cinema app does not collect data; Apple explicitly notes that this disclosure has not been verified by Apple.⁶ That statement should not be generalized to ReelFork Studio, web accounts, creator uploads, generated assets, analytics, purchases or server-side processing. The accessible evidence reviewed here does not provide a complete current ReelFork-wide privacy/retention/security specification.

The app is rated 18+ and includes user-generated content and messaging/chat classifications on Apple's surface.⁶ This matters for moderation and creator distribution. Interactive drama platforms can combine generated media, user-uploaded assets, branching narratives and paid content, so rights management, moderation, age handling and takedown procedures are material operational questions even when the creation workflow itself is technically strong.

ReelFork's current evidence therefore supports a fairly confident description of what the product is trying to do and a lower-confidence view of how reliably it does it at production scale. There is not yet a mature G2/Capterra/TrustRadius-style corpus, a broad creator-review sample or an independent benchmark of story quality, video consistency, generation cost, render reliability or audience conversion.

ReelFork is best suited to creators who specifically want interactive narrative. AI filmmakers, short-drama teams, writers adapting fiction, comic creators and studios experimenting with choose-your-own-story formats gain more from its branch-first architecture than creators who only need a conventional linear video generator.¹³

The no-code/agent-assisted direction lowers the technical barrier for teams that would otherwise need a game engine, custom web player or engineering work to represent choices and consequences.⁴ RFD also gives more technical teams a path to treat narrative structure as data that can live in Git, be generated by scripts or LLMs and be validated before publication.²

Existing short-video creators may find the Studio-to-Cinema loop attractive because creation and distribution are connected. The consumer app already supports both interactive and ordinary serial/video content, so creators can theoretically publish into a dedicated discovery environment rather than exporting a file and building distribution separately.⁶ The practical value of that ecosystem will depend on audience scale and creator economics, which are not yet well established publicly.

ReelFork is less suitable for teams that need mature enterprise controls, detailed public security documentation, predictable publicly listed creator pricing or a large independent evidence base before adoption. It is also not the obvious choice for ordinary marketing video, editing existing footage or fully linear production where branching logic adds no value.

Because the platform is young, creators should start with a bounded pilot: one short branching story, a small number of decision nodes and explicit measurement of generation cost, revision effort, playback reliability and viewer completion/branch behavior. That kind of trial is more informative than assuming the platform's broad feature list will translate directly into production efficiency.