We opened a Discord community for Nenne

What can you share?

We want to hear every kind of Nenne story

The main reason for opening the community is not simply to broadcast announcements. We want to understand the moments when people reach for Nenne and carry those experiences into future updates and guidance. Positive feedback and constructive criticism are both necessary if we want to see the app clearly.

The announcements channel will be the first place to find news. We will share updates, new features, and things worth knowing before you use them. If you want to know what changed after an update or how a feature might fit a particular situation, keep an eye on that channel.

If you encounter a bug, please use the bug report channel. A problem that seems small can still affect many other people. Tell us whether it happens only on a certain screen, only after connecting headphones, or only after the app has been left in the background. Those details help us narrow down the cause.

Feature ideas are welcome as well. You can simply ask for the feature you want, but it helps even more when you describe the situation behind it. What were you trying to do? Which step felt awkward? What kind of place were you in? The reason behind a request lets us consider the real problem rather than only one possible solution.

Reviews and kind words belong there too. Tell us where you first tried Nenne, what felt comfortable about hearing an alarm through headphones, or when the app let you rest without waking someone nearby. A small story can help another person decide whether the app is useful, and it gives the people making Nenne a reason to keep going.

When reporting a bug

Reproducible details help the most

When you report a bug, please include what was happening at the time. Your phone model and operating system, the Nenne version, the headphones you used, and the screen or action where the problem appeared can make all the difference. If we can recreate the same situation, we can investigate the cause and check whether a fix really worked.

A useful report often follows a simple order: what you were trying to do, which steps you took, and what happened. “The alarm did not ring” is already useful, but the time you set, the alarm mode, the headphone connection, and whether the phone was locked can point us in the right direction much sooner.

If you have a screenshot or short recording, you can attach it too. Please hide names, phone numbers, email addresses, locations, notification contents, and any other personal information before sharing. Do not upload another person’s information either. A detailed report and careful protection of private information should always go together.

Not every issue can be fixed immediately. Device differences, operating-system behavior, headphone connections, and background activity can all matter. Even so, reports help us write better guidance for people with the same problem and decide what to investigate first. We may need time to respond, but we will not treat the information casually.

When suggesting a feature

Tell us about the moment behind the idea

A feature suggestion gives us a chance to imagine a different version of Nenne. Behind “I wish it could do this” there is usually a specific moment: a setting that felt too complicated, a break that was hard to time, or a moment when you could not tell whether your headphones were connected. Describing that scene helps us think about a solution from the right starting point.

Please share an idea even if someone has already suggested something similar. The reason and context may be different, and several experiences together can show which problem is most important. They also help us notice what a new feature might accidentally make more complicated.

A suggestion does not become meaningless just because it cannot be added right away. Nenne needs to stay focused on helping people take a quiet break without losing its simplicity. We will consider how an idea fits that purpose, and when possible, explain what we can do next and why some requests need more time.

A community we can share

Speak freely, and respect each other’s time

People will have different opinions about the same feature, and the same error may affect people in very different ways. Please describe your experience clearly while respecting other members’ ways of using the app. It is much easier to have a useful conversation about what felt difficult and what could change than about who is to blame.

Reading the guide and existing announcements first can prevent repeated questions. If another report describes the same situation, add useful details to that conversation instead of opening several identical posts. If your situation is different, start a new report so the two problems can be checked separately.

Replies may take time. We cannot read every message instantly or promise an immediate answer to every idea, but that does not make a message unimportant. We will gather what we can, check it carefully, and share what we know and what we can do next. Please help us keep the server calm and welcoming as it grows.

Join us

Help us shape the next part of Nenne

If something comes to mind while using Nenne, please do not assume it is too small to mention. “This part worked well” is useful, and “I got stuck here” is useful too. A question from someone who just found the app, an idea from a long-time user, and a first impression from today all help us understand our users and their needs more clearly.

You can join the Nenne Discord community through this invitation link. After joining, read the guide and rules, then start in whichever channel fits your message. Announcements, bug reports, feature ideas, reviews, and kind words are all welcome.

Your words help make Nenne more reliable and show us how to help more people rest quietly. Just as a personal alarm can let you rest without disturbing anyone nearby, one thoughtful message can help us create a better experience for the next person who needs a short break.