Home / Guides / Describing your idea

How to describe your app idea

A simple way to describe an app idea so a developer understands it: who uses it, what they do, and what success looks like. Includes a short template.

Short answer. Describe who uses the app, what each of them needs to do, and what is painful about how it works today. Skip the technology. A few honest sentences about the problem are worth more than a long feature list.

The three questions

  • Who uses it? Customers, staff, managers, suppliers.
  • What do they need to do? Book, order, check, approve, upload.
  • What goes wrong today? Missed calls, double typing, lost paperwork.

A short template

  • Today we ... and the problem is ...
  • I want customers or staff to be able to ...
  • It would be a success if ...

What to leave out

  • Technical choices. That is our job.
  • Every possible feature. Start with what matters most and keep a later list.

Questions

Should I include examples of apps I like?

Yes, if you have them. Say what you like about them.

What if I am not sure it is a good idea?

Send it anyway. An honest no is useful too.

Want help with this?

Ask us, or send your idea and get a plan back.