Spin the Names is maintained by one developer, so feedback from users has an outsized impact on what gets built and fixed. If something isn't working or you have an idea that would make the tool more useful, reaching out genuinely makes a difference.

All feedback goes to ash@spinthenames.com.

Reporting a bug

The more specific you can be, the faster something can be fixed. Helpful details to include:

• What happened — describe the unexpected behavior as clearly as you can
• What you expected to happen — what the correct behavior should be
• Steps to reproduce — what you did before the issue occurred
• Device and browser — e.g., iPhone 14 / Safari, Windows 11 / Chrome, iPad / Firefox
• Screenshots or video — if you can capture the issue, it helps enormously

A report like "the wheel doesn't work" is hard to act on. A report like "the wheel freezes after the second spin on iPad Safari when I have more than 20 names" gets fixed much faster.

Requesting a feature

Feature requests are welcome. The most useful ones explain the underlying need, not just the solution. Instead of "add a confetti animation," something like "I use this for classroom celebrations and it would help if there were a more dramatic win moment for students" gives more to work with.

Good feature requests include:

• What you're trying to accomplish and why the current tool doesn't fully support it
• How often you'd use this feature and in what context
• Any examples of how other tools handle similar needs (useful for reference, not required)

Not every request becomes a feature — especially if it's complex to build or only useful to a small number of people — but all of them are read and considered.

What's actually built from feedback?

Several of the app's current features came directly from user feedback: multilingual support, saved wheels, embedding options, and various customization settings all started as requests from teachers, event organizers, and streamers who explained what they needed and why.

The most impactful requests tend to come from people who use the app regularly in a specific context — a teacher who runs it every day for class, an event coordinator who uses it monthly for giveaways. If that's you, your input carries real weight.

Response times

Spin the Names is maintained by an independent developer alongside other work. Bug reports for significant issues are typically addressed quickly. Feature requests and general feedback are read and may be acknowledged, but a personal reply isn't always possible. If something is genuinely broken for you, lead with that — it gets prioritized.

Positive feedback

If the app helped your class, made your event go smoothly, or just saved you an awkward moment deciding who does the dishes — sending a quick note is appreciated more than you might think. Independent software often runs quietly in the background, and hearing it's actually useful to real people is genuinely motivating.