Feature Requests
Help shape the future of Kasanova by suggesting features.
How to Request Features
GitHub Issues (Preferred)
Submit on GitHub:
Visit Kasanova GitHub repository
Check existing feature requests first
Open new issue if not exists
Use "Feature Request" template
Describe your idea clearly
Good Feature Requests Include:
Clear description of feature
Problem it solves
How you'd use it
Why it's valuable
Examples if applicable
Template:
Feature: Dark Mode
Problem: Bright interface strains eyes at night
Solution: Add dark theme option in settings
Use Case: Using app before bed, in dark rooms
Value: Better UX, reduced eye strain, modern design
Examples: Like [other wallet], [popular app]Community Discussions
Discuss Ideas:
Telegram/Discord
Get community feedback
Refine before formal request
Gauge interest
Benefits:
Community input
Collaborative refinement
See if others want it too
May already be planned
Roadmap Visibility
What's Planned: Check our public roadmap (coming soon):
Upcoming features
In development
Under consideration
Released recently
Upvote Features:
See existing requests
Upvote ones you want
Comment with use cases
Help us prioritize
Feature Categories
High Priority
Security & Privacy:
Enhanced security features
Privacy improvements
Additional auth methods
Core Functionality:
Essential wallet operations
Performance improvements
Bug fixes
User Requests
Community-Driven:
Most requested features
Popular improvements
Nice-to-have additions
Based On:
Feature request volume
Upvotes and comments
Community discussions
User feedback
Experimental
Beta Features:
Testing new ideas
Opt-in early access
Feedback appreciated
May or may not ship
What Makes a Good Request?
✅ Do
Be Specific:
Clear feature description
Detailed use case
Expected behavior
Why it matters
Research First:
Check existing requests
Review roadmap
Search discussions
Avoid duplicates
Explain Value:
Who benefits?
How does it help?
What problem solved?
Why prioritize?
Provide Examples:
Other apps doing it well
User flows
Mockups (if you can)
Concrete scenarios
❌ Don't
Vague Requests:
"Make it better"
"Add more features"
No details provided
Duplicate Requests:
Already submitted
Upvote existing instead
Comment on original
Demands:
"You must add this"
"I'll quit if you don't"
Entitled tone
Unrealistic expectations
Evaluation Process
How We Decide:
Community Interest - Upvotes, comments
Alignment - Fits Kasanova's vision
Feasibility - Technical possibility
Resources - Development time required
Priority - Impact vs effort
Factors:
Security implications
Privacy impact
User experience
Performance effects
Maintenance burden
Response & Timeline
We Will:
Review all requests
Comment on feasibility
Label appropriately
Update status
We Cannot:
Implement everything
Provide exact timelines
Guarantee inclusion
Rush features without testing
Timeline Factors:
Complexity
Team capacity
Dependencies
Testing needs
Security review
Feature Types
Quick Wins
Small improvements
Low complexity
High impact
Fast to ship
Major Features
Significant work
Longer timeline
Careful planning
Thorough testing
Long-Term Vision
Strategic additions
Future roadmap
Research needed
Eventual goals
Examples of Past Requests
Implemented:
Zen mode
Biometric authentication
Marketplace integration
Token deployment wizard
In Progress:
Hardware wallet support
Multi-language support
Advanced charting
Batch transactions
Under Consideration:
Desktop app
DeFi integrations
Cross-chain bridges
DAO governance
Contributing Code
For Developers:
Code contributions welcome
Open GitHub PR
Follow contribution guidelines
Discuss major changes first
Open Source (Future):
Plans to open source
Community contributions
Code review process
Collaboration
Feedback Channels
Where to Share:
GitHub: Feature requests
Discord: Discussions
Telegram: Quick feedback
Email: Detailed proposals
What to Share:
Feature ideas
UX improvements
Bug reports
General feedback
Next Steps
Last updated