Quidli documentation
Visit websiteRead blogFollow us
  • What is Quidli?
  • Product overview
    • Web app
    • Discord
    • Slack
    • Telegram
    • GitHub
    • Farcaster
    • X (Twitter)
    • NFTs
    • Features
      • 🤝Send tokens
      • 🤖Automate token drops
      • 🎯Create reward flows
      • 👍Send tokens via emojis
      • 🪂Airdrop tokens
      • 👩‍💻Incentivize dev work
      • 💐Recognize contributors with NFTs
  • Use cases
    • Internal team recognition
      • Welcome new team members
      • Recognize top performers & achievements
      • Celebrate special occasions
    • Community engagement
      • Monitor community dynamics via token transactions
      • Ensure your top contributors are being recognized
      • Leverage community to help boost your project on socials
    • Developer relations
      • Highlight specific issues to address on GitHub
      • Decrease support ticket resolution time
      • Keep hackathon participants engaged
  • FAQs
    • Questions
      • How does Quidli work?
      • Which tokens are supported on Quidli?
      • How are tx fees handled?
      • Can I withdraw tokens?
      • Can I get my token(s) added?
    • How can I contact you?
Powered by GitBook
On this page
  1. Use cases

Developer relations

Motivate your developers to go above & beyond!

PreviousLeverage community to help boost your project on socialsNextHighlight specific issues to address on GitHub

Last updated 1 year ago

Attracting developers to contribute to code, reviews, projects, etc. is critical for your ecosystem's success. Share tokens to keep devs engaged & motivated to build with/for you.

We outline some of the more popular internal team recognition use cases for your reference.

Cover

Keep hackathon participants engaged

Cover

Decrease support ticket resolution time

Cover

Incentivize quality pull requests in GitHub

Cover

Get issues solved speedingly with Quidli