Community Feedback: Feature Requests and Improvement Areas

[viborc]

Hey Scope community!

Over the past few weeks, we've been conducting user research sessions to better understand how you're using Scope, where you're running into friction, and what capabilities would make the biggest difference in your workflows.

First and foremost: thank you. To everyone who took the time to share feedback, hop on calls, or send us your thoughts - we hear you, and this input is invaluable as we shape the future of Scope.

What We Heard

Based on your feedback, we've identified several key areas where Scope can improve:

Output and Export

• Video export/download capabilities
• Upscaling workflows for higher resolution output
• Streaming output options (RTMP, external platforms) - we now support this with Spout!

Onboarding and First-Time Experience

• Pre-loaded default model to eliminate the blank starting state
• In-app tutorials and contextual tips
• Welcome flow with clearer first steps
• Progress indicators during model downloads
• Session and token persistence across restarts

Models and Prompting

• Presets and starting prompts per model
• Model comparison and guidance ("what is this model good at?")
• LLM-assisted prompt enhancement
• Ability to specify local model paths

Timeline and Editing

• More flexible timeline editing (insert, reorder, trim segments)
• Cache reset scheduling for scene cuts
• Live prompting capabilities

Interface and Usability

• Better parameter explanations and tooltips
• Clearer prompt change behavior
• Improved discoverability of core actions

Infrastructure and Platform

• Desktop app for local-first usage
• Better production deployment documentation
• Docker installation documentation
• API access options

Community and Sharing

• Community hub for sharing creations and discovering workflows - we also now have this live!
• Easier sharing to external platforms

What This Means
We're taking all of this into account as we plan our roadmap - and some these elements we've already implemented or they are coming very soon.

To be clear: this doesn't mean we'll implement everything immediately or in any particular order. Product development involves tradeoffs, and we need to balance community requests with technical feasibility, strategic priorities, and resource constraints.
That said, your input directly influences where we focus our energy. Keep it coming.

Continue the Conversation
This is an open discussion - we, as a team, would love to hear more from you:

• What's missing from this list? Are there features or capabilities you need that we haven't captured?
• What's most important to you? If you could only pick one or two things, what would unblock your workflow the most?
• How are you using Scope today? Context helps us understand the "why" behind feature requests.

Scope is an open-source project, and building it in the open means building it with you. Drop your thoughts below, open issues for specific features, or contribute directly if you're so inclined.

Thanks for being part of this!