Six screenshot/AI requests from launch week. Which one should I ship next?

These came from people who tried the SlimSnap screenshot-to-JSON workflow during launch and asked for something specific. Listing in the order they came in.

1. Screenshot capture for scrollable content and open dropdowns. Right now the capture clips to the visible window, so if a dropdown or long list is open, parts get cut. Balpreet S flagged this on LinkedIn.

2. Native Mac app screenshot support (scope verification). Several people asked whether SlimSnap captures Linear / Notion / Figma desktop screenshots, or just browser windows. The answer changes who can use it.

3. Confidence and overlap indicators on annotations. When the arrow is ambiguous (e.g. drawn between two close buttons in the screenshot), the JSON should signal that. Corey Clark asked on LinkedIn.

4. Nested element hierarchy in the schema. Current screenshot schema is flat with bbox containment for nesting. Jyoti S Mohanty asked whether to make hierarchy explicit. Schema v2 candidate.

5. Hybrid mode (JSON + raw screenshot). For users who want the safety net of pixels alongside the structured spec. Martin Zokov asked on X. Optional, would double the per-screenshot token cost.

6. Windows screenshot support. Multiple people. OCR layer is Mac-native, so this is a real porting project, not a one-line change.

Which one should I build next? Vote in the comments, ideally with one line on why it matters for your screenshot workflow.

I have my own gut ranking but want to see what actual users prioritize.