LogoSniCap
OverviewDemosAPIArchitecture

Published direction

Roadmap

Review the published ReactSnap direction across asset embedding, PDF support, diagnostics, and browser capability coverage.

Rendering StrategiesRoadmapMenu

Published direction for asset embedding, PDF, and diagnostics.

HTML in CanvasforeignObjectArchitectureRoadmap

On this page

Near-term prioritiesAsset embeddingBetter diagnosticsPDF backendMedium-term directionWebsite implications

ReactSnap is already useful for browser-side previews and exports. The roadmap is about hardening the renderer around real production assets rather than turning it into a broader visual tool.

Near-term priorities#

Asset embedding#

Font fetching, font embedding, and image inlining are still the biggest fidelity gaps between a useful preview engine and a dependable export layer for more varied UI.

Better diagnostics#

Strategy selection is one of the product's differentiators, so the debugging story should keep getting stronger. Clear fallback reasons, capability visibility, and predictable runtime errors help teams trust the browser behavior they are seeing.

PDF backend#

@reactsnap/pdf currently throws an explicit scaffold message. The next substantial milestone is wiring a real backend so page-to-document export becomes more than an API placeholder.

Medium-term direction#

  • broaden coverage around html-in-canvas
  • keep foreignObject dependable as a compatibility baseline
  • refine SVG mode boundaries
  • make documentation and demos feel like one coherent developer surface

Website implications#

The site should present roadmap items as honest capability boundaries, not hidden caveats. That means marking preview features clearly, keeping demo pages resilient when experimental APIs are unavailable, and using API docs that match the published npm packages rather than a future branch of the repository.