name: Feature request
description: Suggest an improvement or new feature.
title: "[Feature]: "
labels:
  - enhancement
body:
  - type: markdown
    attributes:
      value: |
        One feature request per issue, please. The more real-world your use case is, the easier it is to evaluate.

        Feature requests are reviewed as product proposals first.
        Please do not open a pull request for a new feature, major UX change, or broad cosmetic update unless a maintainer has explicitly approved it first.
        Unapproved feature PRs will usually be closed.

        **Any large PR or change that is not a simple bug fix MUST be discussed and approved via a feature request issue first.**
        PRs that introduce large changes without a linked, approved feature request **will not be reviewed at all** and will be closed immediately. No exceptions.

  - type: dropdown
    id: area
    attributes:
      label: Area (tag)
      options:
        - Playback
        - Streams / Sources
        - Next Episode / Auto-play
        - Watch Progress
        - Subtitles
        - Audio
        - Navigation / Gestures
        - UI / Layout
        - Settings
        - Sync (Trakt / remote)
        - Downloads / Offline
        - Platform-specific (iOS only / Android only / Desktop only)
        - Other
    validations:
      required: true

  - type: textarea
    id: problem
    attributes:
      label: Problem statement
      description: What problem are you trying to solve?
      placeholder: "I want to be able to..."
    validations:
      required: true

  - type: textarea
    id: proposed
    attributes:
      label: Proposed solution
      description: What would you like the app to do?
    validations:
      required: true

  - type: dropdown
    id: contribution_plan
    attributes:
      label: Are you planning to implement this yourself?
      description: Major features are usually implemented in-house unless approved first.
      options:
        - No, this is only a proposal
        - Maybe, but only if approved first
        - Yes, but I understand implementation still needs maintainer approval
    validations:
      required: true

  - type: textarea
    id: alternatives
    attributes:
      label: Alternatives considered (optional)
      description: Any workarounds or other approaches you considered.
    validations:
      required: false

  - type: textarea
    id: extra
    attributes:
      label: Additional context (optional)
      description: Mockups, examples from other apps, etc.
    validations:
      required: false