I think you first need to decide, as a product team, what a reasonable release schedule would be - can you release a new version every week, every two weeks, every two months, etc? From that, estimate how many development hours you have available for each release (factoring in that you have a single developer, and that time needs to be reserved for design, coding, documentation, re-factoring, support, writing deployment scripts, surfing stackexchange, testing, etc.)
Then, keep track of all requested new features, enhancements, and bugs. For each, provide a rough development estimate. You will now have a list of items, their "cost" (in development hours), and an amount you can "spend" for each release.
The next step is to somehow select the items to be included in the future releases. If you can establish a single point-of-contact - a "product manager" or a "user representative" or even a small working group - that's great. That person/group has the final say into what is included or not in each release. If it's not possible to define a single person/group for this, you can try surveying the user base - ask the users to simply rank the features that are most important to them. if you do this, to keep it simple, I would only include new features being considered, in the survey - leave out bug fixed, small enhancements, etc.