How can I submit feature requests or feedback?

GRYYD values user feedback as the primary driver of product development. Your feature requests, workflow suggestions, and usability feedback directly influence the product roadmap. Understanding the feedback submission process and how requests are prioritized helps you contribute to shaping GRYYD\'s future.

How to Submit Feedback

Email Submissions:

• Address: gryyd@metric-studio.com
• Subject Line Format:
  • Feature Requests: `[Feature Request] Brief Title` (e.g., \"[Feature Request] Batch Image Download\")
  • General Feedback: `[Feedback] Brief Title` (e.g., \"[Feedback] Improve Setup Page UX\")
  • Bug Reports: Use same email with subject `[Bug Report]` for faster routing

What to Include:

• ✅ Use Case: Describe the problem or workflow challenge you face
• ✅ Proposed Solution: How you envision the feature working (UI mockups welcome!)
• ✅ Current Workaround: How you currently solve this problem (if any)
• ✅ Expected Impact: How this would improve your workflow (time saved, quality improvement)
• ✅ Frequency: How often you would use this feature (daily, weekly, monthly)
• ✅ User Context: Your industry, team size, use case (helps prioritize for target audience)

Example Submission: ``` Subject: [Feature Request] Batch Download for Multiple Drafts

Use Case: I manage 10+ client campaigns per month. Currently, I must download images one draft at a time, which takes 20+ minutes per project.

Proposed Solution: Add a "Download All" button on the project page that:

1. Lets me select multiple drafts (checkboxes)
2. Choose download format (JPG/PNG) and resolution (2K/4K)
3. Downloads a single ZIP file with folder structure: ProjectName/DraftName/image01.jpg

Current Workaround: Manually downloading each draft individually, then organizing files locally.

Expected Impact: Would save 15-20 minutes per project, allowing me to handle 30% more clients.

Frequency: Daily (10-15 projects per week)

User Context: Marketing agency, team of 5 designers, e-commerce clients ```

Feedback Review Process

Review Timeline:

• Acknowledgment: Within 48 hours (automated confirmation)
• Internal Review: 1-2 weeks (feasibility, impact, strategic fit evaluation)
• Response: 2-3 weeks (accepted, under consideration, or declined with explanation)
• Development Updates: Quarterly updates for accepted features, beta testing invitations, launch announcements

Feature Request Categories

High-Priority Categories (Faster Review):

• Workflow Efficiency: Features saving 10+ minutes per session (batch operations, keyboard shortcuts)
• Collaboration: Team features, project sharing, commenting
• Quality Improvements: Better image quality, more control over generation parameters
• Integration: API access, third-party integrations (Shopify, Adobe, Figma)

Standard-Priority Categories:

• UI/UX Enhancements: Minor interface improvements, theme customization
• Reporting: Analytics dashboards, usage reports
• Localization: Additional language support beyond Korean/English

Low-Priority Categories (Longer Review Time):

• Nice-to-Have Features: Non-critical improvements (e.g., dark mode, custom fonts)
• Edge Cases: Features benefiting <5% of users

How Features Are Prioritized

Features are evaluated based on user impact, business value, development effort, and strategic alignment. High-impact workflow efficiency features and collaboration tools are typically prioritized over nice-to-have enhancements.

Feedback Best Practices

Do:

• ✅ Focus on the problem you are trying to solve (not just the solution)
• ✅ Provide real-world examples and use cases
• ✅ Be specific about expected behavior
• ✅ Attach screenshots or mockups if you have a clear vision
• ✅ Search FAQ/roadmap first to avoid duplicate requests

Avoid:

• ❌ Vague requests (\"Make it better\")
• ❌ Demanding features without context (\"You must add this!\")
• ❌ Comparing to competitors without explaining why (\"Tool X has this\")
• ❌ Submitting duplicate requests (check roadmap first)

Pro Tip: The most effective feature requests include a video walkthrough of your current workflow showing the pain point. Use Loom (loom.com) to record a 2-3 minute screen recording demonstrating the problem and how the proposed feature would help. This provides context engineers need to design the perfect solution.

See also: Customer Support | Upcoming Features | API Access