There are a lot of comments here that are not very charitable, but, then, it IS Slashdot (Where the elite come to snark.)
Many people know that they would like to be able to use a computer to do something for which there are currently no apps available. They also know that the subject matter knowledge that they have would take years for a programmer to learn, and more investment of effort than most people would be willing to make. Their knowledge is every bit as critical as that of the programmer, and every bit as difficult to fully understand. They may not need a marketable app with all manner of multimedia extensions, don't foresee a sufficient market to cover the cost of a professional programmer, or else they do not believe that a programmer can get up to speed on the particulars of their problem to see all of the potential pitfalls any faster than they can get up to speed on the programming side of the problem. Coding expertise is valuable, but it is not the only valuable aspect of a program.
The great mass of non-programmers only hear the marketing news that makes it to the mainstream media, which usually consists of statements about how much easier programming is with product X. They, not unjustifiably, assume that after 25 years of such announcements, programming languages must be much easier and more powerful than they were when they took Basic in high school, 20 years ago.
Combine that with the archetypal image many people have in the back of their minds about computing, the Enterprise computer from Star Trek, and futurists promising computers with natural language interfaces (bolstered by commercials featuring Siri) and it's not unreasonable for them to believe that it may be possible for them to attempt a more complex problem than they are able to with current tools. They aren't meaning to be insulting when they think it should be easier. They are just going on the information they have and trying to figure out what their most efficient option is, between the frustration of learning to code, and the frustration of working with a coder on a project where they will have to teach a coder about all of the ins and outs of their discipline. All of the time that you spent learning to code, of which you are justifiably proud, an architect or engineer spent learning about structure, a doctor spent learning about medicine, a linguist spent learning about language.
To a coder, the app is the solution to a problem. To the user, the app is just a tool that may help them find a solution. To them, the coder only sees a small part of the big picture, and may have no commitment to what they understand as the real issue.
The suggestion that you as a professional coder could master their expertise sufficiently to solve their problem over the course of a project may be every bit as insulting to them as their belief that programming may be something they could learn over the course of a project is to you.