Not a game
Less about mechanics, more about continuity.
The product is built for immersion, narrative momentum, and repeat reading sessions rather than combat systems, grinding loops, or complex gameplay rules.
Twincurrent Studio
AI-native narrative products
Immersive AI Interactive Novels
Twincurrent Studio is building Storyloom, an immersive AI interactive novel reader. It is not a game lobby and not a linear ebook reader. It is a product where readers choose an identity, enter different openings, push the plot through ongoing rounds, reopen branches, and keep coming back because the story keeps moving.
Product Positioning
Not a game
The product is built for immersion, narrative momentum, and repeat reading sessions rather than combat systems, grinding loops, or complex gameplay rules.
What it is
Readers enter a work, choose an identity, start from a different opening, and then progress through persistent dialogue turns with branch history and replay built into the experience.
Not a static reader
Works do not freeze after page one. They grow through AI generation, but inside a structured product with controlled content supply, guided choices, and a clear reading mindset.
Reader Experience
Storyloom launches with a real library of works, not a one-title demo. Readers browse, search, and continue where they left off.
Different roles and opening setups change the first emotional angle of the story, which makes the product feel personal before the core reading begins.
Progress is structured as turn-by-turn narrative continuation. The main interaction is system choices, with free input treated as reader action rather than open chat.
Readers can scroll back, reopen earlier moments, and create new branches only when they make a different choice. That turns replay into product depth instead of confusion.
Why This Product Can Scale
The library begins with platform-made or platform-curated works, so quality is legible from day one and the app feels like a destination rather than a blank prompt box.
Early creators can submit story packages, character identities, openings, and front-end assets, but publication remains curated. This protects product quality while expanding supply.
HTML drives the pre-story atmosphere, the app owns the reader experience, and the backend controls story generation, entitlement, and token state. That keeps the product stable as usage grows.
Business Model
Primary engine
$9.99/month MVP anchor
The product is designed so readers treat Storyloom as an ongoing reading service. Subscription is the core revenue layer because the experience is built around returning to works, continuing lines, and consuming story worlds over time.
Token purchases exist to cover incremental generation cost, but the company story is subscription-first: recurring access, recurring engagement, recurring revenue.
Non-subscribers can still get a baseline experience. That reduces friction at the top of the funnel while subscription captures the readers who want continuity and momentum.
Continue Reading, branch history, replay, and multi-work discovery are all product decisions that reinforce subscription behavior rather than one-session novelty.
Core Principles
Buttons, panels, and rules should not break the emotional spell of the story.
Works are meant to keep moving over many turns, with enough payoff to sustain habit.
System options are primary. Free input remains bounded as narrative action, not freeform chat.
Models sit behind the platform. The app remains a controlled reader, not an exposed model shell.
Company Snapshot
The goal is not to ship a flashy experiment. The goal is to build an immersive AI interactive novel product that readers return to, pay for, and treat like an evolving reading service.
Current contact email: momentlog@163.com