Feature Requests
Have an idea to improve EcoDesign? We'd love to hear from you! Submit your feature requests and help us build the ecological design platform you need.
Your Ideas Drive Our Development
EcoDesign is built by the community, for the community. Your feedback and feature requests are invaluable in shaping the future of our platform. Every suggestion is carefully considered and helps us prioritize our development roadmap.
How to Submit Feature Requests
Submit Your Feature Request
support@earthunited.eco
Clicking the email link above will open your default email client with a pre-formatted template to help you structure your feature request.
Feature Request Guidelines
What Makes a Good Feature Request
Essential Elements
Clear Description:
- Specific Functionality: Describe exactly what you want the feature to do
- User Interface: How would users interact with this feature?
- Expected Behavior: What should happen when users use this feature?
- Scope: Is this a small enhancement or a major new capability?
Real-World Use Cases:
- Your Situation: Describe your specific project or challenge
- Current Workaround: How do you handle this need now?
- Frequency of Use: How often would you use this feature?
- Impact: How would this feature improve your experience?
Benefits and Value:
- Problem Solving: What problem does this feature solve?
- Time Savings: How would this feature save time or effort?
- Better Outcomes: How would this lead to better project results?
- User Base: Who else might benefit from this feature?
Feature Request Categories
AI and Research
- New AI agent capabilities
- Enhanced research questions
- AI-powered analysis tools
- Conversation management features
- Research export and sharing
Project Management
- Project planning tools
- Task and timeline management
- Progress tracking features
- Collaboration capabilities
- Resource management tools
Design and Planning
- Design visualization tools
- Mapping and layout features
- Component libraries
- Design templates
- CAD integration
Data and Integration
- Import/export capabilities
- Third-party integrations
- Data visualization
- API access
- Reporting features
Learning and Knowledge
- Educational content
- Tutorial enhancements
- Knowledge base features
- Community learning tools
- Certification programs
User Experience
- Mobile app features
- Interface improvements
- Accessibility enhancements
- Customization options
- Performance optimizations
Feature Request Examples
Well-Structured Request Examples
Good Example
Feature: Seasonal Planting Calendar
Description: A visual calendar that shows optimal planting times for my specific location and selected plants.
Use Case: I have a 200 sqm garden in Amsterdam and want to plan my planting schedule for the entire year. Currently, I need to research each plant individually.
Benefits: This would save hours of research and ensure I plant at optimal times for maximum success.
Needs Improvement
Feature: Better plants
Description: Make the plant suggestions better.
Issues: Too vague - what specifically needs improvement? What's your current experience? What would "better" look like?
Feature Request Process
What Happens After You Submit
Our Review Process
- Acknowledgment (1-2 business days): We'll confirm receipt of your feature request
- Initial Review (1 week): Our team evaluates the request for clarity and feasibility
- Community Assessment: We consider how many users would benefit from this feature
- Technical Evaluation: Our development team assesses implementation complexity
- Roadmap Planning: Approved features are added to our development roadmap
- Status Updates: We'll keep you informed about your request's progress
Prioritization Factors
How We Prioritize Features
- User Impact: How many users would benefit from this feature?
- Problem Severity: Does this solve a critical user need or pain point?
- Strategic Alignment: Does this fit with our product vision and goals?
- Technical Feasibility: How complex is this feature to implement?
- Resource Requirements: What development resources would this require?
- User Feedback Volume: How many users have requested similar features?
Frequently Asked Questions
Common Questions About Feature Requests
Q: How long does it take to implement a feature?
A: Implementation time varies greatly depending on complexity. Simple enhancements might be included in the next release (4-6 weeks), while major features could take several months. We'll provide realistic timelines during our evaluation.
Q: Can I request a feature that already exists in other software?
A: Absolutely! If there's a feature in other tools that would enhance EcoDesign, we'd love to hear about it. Please explain how it would fit into the ecological design workflow.
Q: Do you implement all feature requests?
A: While we can't implement every request, we carefully consider each one. Some requests might be outside our product scope, technically unfeasible, or serve a very small user base. We'll always explain our decision.
Q: Can I suggest improvements to existing features?
A: Yes! Enhancement suggestions for existing features are just as valuable as completely new feature ideas. Please describe what you'd like improved and why.
Q: Is there a limit to how many features I can request?
A: No limit! However, we recommend submitting separate emails for different features to help us track and evaluate each one properly.
Alternative Ways to Influence Development
Beyond Feature Requests
User Feedback
- Bug Reports: Help us identify and fix issues
- Usability Feedback: Share what's confusing or difficult
- Success Stories: Tell us what's working well
- Workflow Suggestions: How could processes be smoother?
Community Involvement
- Beta Testing: Try new features before release
- User Interviews: Share detailed feedback in interviews
- Community Forums: Discuss ideas with other users
- Feature Voting: Help prioritize community requests
Feature Request Template
Copy This Template for Your Email
Subject: Feature Request: [Brief Feature Name] Hi Earth United Team, I would like to suggest a new feature for EcoDesign: FEATURE NAME: [Provide a clear, descriptive name] DESCRIPTION: [Explain what this feature would do and how it would work] WHY THIS WOULD BE HELPFUL: [Describe the problem this solves or benefit it provides] MY USE CASE: [Explain your specific situation and how you would use this feature] CURRENT WORKAROUND: [How do you handle this need currently, if at all?] WHO ELSE MIGHT BENEFIT: [Consider other users who might find this valuable] ADDITIONAL DETAILS: [Any other relevant information, mockups, or examples] Thank you for considering my suggestion! Best regards, [Your name] [Optional: Your location/project type for context]
Stay Updated
Follow Development Progress
Want to stay informed about new features and development progress?
- Release Notes: Check our announcements for new feature releases
- Beta Programs: Join our beta testing community for early access
- Newsletter: Subscribe to our development updates
- Social Media: Follow us for feature previews and updates
We'll also personally update you on the status of your specific feature requests.
Ready to Submit Your Idea?
This link opens your email client with a pre-formatted template
Remember
Your ideas and feedback are the driving force behind EcoDesign's evolution. Every feature request helps us understand user needs better and build a platform that truly serves the ecological design community. Thank you for taking the time to share your vision with us!