Contact Pineapple
Got a bug, a feature idea, or want to contribute? Here are the fastest ways to reach us. Replies go to the maintainers via GitHub — there's no official mailbox, but a project email forward is being set up.
🐛 Report a bug
Best path: open a GitHub issue with device, severity, and reproduction. Filing with details gets traction fastest.
✨ Request / suggest a feature
UX redesigns, artist features, catalogue requests: the issue backlog already holds 99 starter tickets (#12–#111).
💬 Community & discussion
For design questions, use case story or how-to, join GitHub Discussions — keeps answers searchable forever.
🔧 Contribute PRs
Read CONTRIBUTING.md first (no new deps · bundled vectors only). Tag your PR; we run assembleDebug testDebugUnitTest locally before merge.
📧 Direct reach
Email alias being finalised. For now, ping kiinshuk@users.noreply.github.com with [Pineapple] in the subject — or open an issue. Spam to that address is reported.
💖 Sponsor the maintainer
Pineapple is free & MIT. If it's useful to you, star the repo and consider sponsoring the maintainer.
Direct reach for a bug
For speed, include in your issue or email:
- Device model + Android version (API level if known).
- Steps to reproduce + tap-by-tap names.
- Whether you're on Wi-Fi / cell / airplane mode.
- Logcat snippet (Settings → Developer options → Take bug report) if the app crashes.
- Screenshot (Settings > Account's screenshot) when UI issue.
If requesting a device test, we bill at zero — but we do ask for the device-access itself, or at least synthetic offline/low-latency tests.