Roadmap

Recently shipped work and the current Core Builds engineering priorities.

Shipped on July 22, 2026

Area	Completed work
Configurator v2.78	Modular source architecture with a generated standalone index.html release
Quick Install	Multi-provider selection, contextual Get-key links, optional TMDB metadata, compact extras picker
Compatibility	AIOStreams enum normalization and safe defaults before export/install
Hosts	Stable-first probing, minimum-version checks, restrictions, remembered successful host, nightly fallback
Devices	Centralized conservative video, HDR, and audio capability rules
UX	Seven-step tutorial, mobile safe areas, keyboard handling, landscape support, repaired light mode
Security messaging	Accurate local export, hosted Direct Install, and Stremio API descriptions
Community	Core Crew naming, central gem support control, live usage counter retained
Apex v0.9.0	Resolution-first sorting and Core Clean formatter refinements

Current priorities

Documentation and release quality

• Keep Configurator, Quick Start, Device Profiles, What’s New, and SEL documentation aligned with current releases.
• Validate both Markdown and Mintlify MDX links.
• Keep Template Suite and Configurator version numbers independent and sourced from versions.json.

Template validation

• Track current upstream AIOStreams preset types in the validator.
• Maintain an explicit review list for intentional requiredLanguages policies.
• Pin or snapshot upstream schema expectations and add golden generated templates.

End-to-end testing

• Add browser smoke tests for desktop and phone-sized Quick Install flows.
• Exercise create/update operations against test AIOStreams instances without using real user credentials.
• Verify host restrictions and version behaviour over a longer health window.

Worker hardening

• Restrict proxy origins, methods, and target paths.
• Add rate limits, request timeouts, and body/response size limits.
• Apply Cache-Control: no-store to sensitive operations.
• Reject or redact secrets in public paste payloads.
• Reduce analytics identifiability and move concurrency-sensitive counters to a suitable storage primitive.
• Consolidate the legacy counter worker with the maintained combined worker.

Repository maintenance

• Reduce duplicate material across the root README, Guides/, and Mintlify docs/.
• Publish generated PDFs as release assets where practical rather than tracking every generated copy.
• Replace scheduled direct commits to main with CI reporting or bot pull requests.

Longer-term ideas

• Parent/child AIOStreams configuration architecture after a reliable permanent parent host exists.
• Mobile and bandwidth-focused templates.
• Anime Dub 4K variant.
• Broader codec, audio, and HDR priority expression rollout after template-specific testing.
• GitHub-native sponsorship in addition to the existing Ko-fi option.

Roadmap items are plans, not guarantees. Host availability and upstream AIOStreams schema changes can alter sequencing.