Wish an app existed? Share the idea and find people who can help

Maybe you want an easier way to organize a volunteer group, manage a particular kind of work, or solve a small frustration that keeps returning. If you have caught yourself thinking, “I wish an app existed for this,” you already have the beginning of a product brief.
The hard part is making the idea clear enough for someone else to understand. A good request describes the situation behind the wish—not just the features you imagine. That gives developers room to ask better questions and suggest solutions you may not have considered.
Explain the need before prescribing the app
Start with who experiences the problem, when it happens, and what they do today. Name the workaround if there is one. Then describe what a better outcome would look like. For example: “Our volunteer coordinators spend Sunday night matching people to shifts in a spreadsheet. I wish there were a simple way to see availability and fill gaps.” This says more than “I need a scheduling app” because it gives a maker context to explore.
Make the request easy to respond to
- Describe a real moment. What happened the last time you ran into the problem?
- Identify who else has it. Is this specific to you, your team, or a wider group?
- Share your current workaround. Spreadsheets, repeated messages, or several disconnected tools can reveal what is missing.
- Separate needs from guesses. State the outcome you want and leave room for builders to propose how to reach it.
- Ask a clear question. Invite people to share existing tools, point out risks, or discuss a possible approach.
How a maker community can help
On AppHunter Community, you can share an app wish and invite developers, indie makers, and other interested people to respond. Someone might point out an existing product, help sharpen the problem, suggest a simpler first version, or decide the request is a project they want to explore. Those are possibilities, not promises: posting a request does not guarantee that a developer will take it on or that an app will be delivered.
If a maker does want to build, use the conversation to clarify scope, ownership, timing, budget, and support before work begins. A public idea post is a starting conversation, not a contract. Keep private, sensitive, or confidential information out of a public post.
Could this be a product opportunity?
One person’s wish is a useful signal, not proof of a market. Ask whether other people share the problem and how they handle it today. Look for repeated needs, current spending, and strong workarounds. A quick conversation can help you decide whether to research further, sketch a prototype, or leave the idea for now.
Describe the problem. Let the conversation begin.
Share what you wish existed and invite the AppHunter maker community to discuss it.
Share an app wish