Roadmap

Where LiraLora is, what we are building, and where the workflow platform goes next.

LiraLora starts from a focused wedge: guided creative and educational AI workflows where continuity matters, replay matters, and one-shot prompting is not enough.

The roadmap is not about becoming a vague app that claims it does everything. The product expands when a new workflow can truly benefit from the same core strengths: durable memory, selective context, guided orchestration, user learning, and replayable refinement.

That means the near-term story stays disciplined while the longer-term platform grows into adjacent workflow families that can reuse the same foundation without losing the clarity of the current product.

Current wedge: character, LoRA, and educational-content workflows

Shared foundation: memory, learning, replay, and local/cloud flexibility

Expansion path: adjacent workflow families that benefit from the same core

Explore current workflows See how it works

Product arc

The roadmap widens in phases so the product can stay coherent while the platform grows.

Now

A focused wedge around continuity-heavy creative and educational work

The product today is centered on workflows that naturally stress test continuity: recurring characters, LoRA preparation and training support, early-reader content, homeschool materials, and work that benefits from checkpoints and revisions without restarting the whole run.

Workflow guidance instead of one-off prompt juggling
Memory and learning that help carry preferences forward
Replay and run-family structure for cheaper revisions
Local-first flexibility with optional cloud offload where it helps

Building

The application, infrastructure, and durable workflow foundation

The current buildout is centered on the actual product: the desktop application, the supporting infrastructure around it, and the systems that make long-running AI workflows durable instead of fragile. That includes testing how memory, learning, replay, orchestration, and local-plus-cloud execution behave under real workflow pressure.

Desktop application experience for guided workflow execution and review
Supporting infrastructure for accounts, billing, orchestration, and heavier background work
Durable memory and learning behavior tested against real multi-step workflows
Replay, checkpoints, and run-family behavior that make revisions cheaper and clearer
A future blog or update stream to show progress as the product and workflow set expand

Future directions

Expanded workflow families on the same orchestration core

Future work should feel like a widening set of workflow families, not a random pile of features. The product grows outward into adjacent domains that benefit from the same memory, learning, checkpoint, and replay model while still keeping the user experience guided and coherent.

Broader creator pipelines and recurring asset systems
Heavier media workflows that mix local compute with selective cloud services
Richer educational production from lightweight readers to more advanced materials
Eventually, domain-specific packs that can sit on the same shared core

Workflow horizons

These are the kinds of workflow families that fit the longer-term shape of the product.

Future workflow family

Coding and app-building workflows

A future coding-oriented family could use the same orchestration scaffold for planning, revisions, checkpoints, and memory of how a user or team likes to work, without forcing the current product to become a generic everything-mode too early.

Creative media

Music generation pipelines

Music workflows can benefit from the same structure: ideation, direction review, variation, selective context carry-forward, and branching from the right checkpoint instead of losing the thread every time a style or motif changes.

Continuity-heavy media

Video generation and shot continuity

Video work raises the stakes on continuity. Story beats, characters, scenes, edits, and revisions all become easier to manage when the system can remember what mattered and replay from the right stage instead of rebuilding a whole run.

Reusable asset systems

Asset pack generation

Recurring item sets, environments, variants, props, and visual identity systems are a natural fit for workflow-guided generation with approvals, lineage, and shared memory across many outputs.

Educational expansion

Advanced AI-generated textbooks and guided learning materials

The educational wedge can deepen far beyond early-reader books into richer lesson systems, subject-specific materials, larger textbook-like structures, and multi-level learning content that stays controlled, reusable, and easier to revise over time.

Learning experiences

Broader children's learning experiences

Illustrated readers, activity sets, workbook companions, and adaptive learning materials all benefit from the same continuity model when recurring characters, style consistency, reading level, and content review matter at once.

How the roadmap stays disciplined

The expansion story only works if the product keeps feeling like a guided system with a clear center of gravity.

New workflow areas should reuse the same memory, learning, replay, and orchestration foundation.
Expansion should help users get more from local hardware first, then offload only what is impractical to run locally.
The product should widen into coherent workflow families, not collapse into a vague promise that AI can do everything.

See the current product shape

How it works Explore workflows Memory vs context FAQ

The roadmap works best when paired with the pages that explain how the current foundation behaves in practice.