@OP, just to give you a perspective, what this inquiry looks like in a different context that's easier for people to imagine.
Hi engineer, I'm looking to build a transportation tool:
- it must have wheel
- It must be able to move on land
- it must be able to carry people
- it may or may not need to carry stuff other than people, this will be decided in the future
- it should be able to carry more than one people, capacity is to be decided later
Please give me a proposal or suggestion.
Now, are you able to imagine what the transportation tool looks like in the engineer's mind? I bet you can't, neither of us can.
Usually professional engineers with sense of responsibility won't give an answer. Instead, the response will probably be "it depends...", following by long long series of Q&A:
- ONLY on land?
- what kind of terrain?
- max weight it must be able to carry?
- speed?
- which countries the tool should support?
- any govt regulation in those countries?
- ... (and blah blah...)
Without the details, what you need and what engineers imagine are almost guaranteed different thing. In another word,
to be productive towards your goal, provide as much details as possible in such inquiry.
On the other hand, be careful on where to raise inquiry. The concern mentioned by @Femsroot is valid.A funny (perhaps upset) thing is that, for most software inquiries I received, whenever I don't give a straight forward positive answer (e.g. contains "it depends on..."), asker will be pissed off "Damn, I cant talk to you guys engineer. I asking simple question, why engineers won't give me simple answer"