When providing the necessary information to a developer, say for a web application, what would typically be provided to the developer and what would it be called if there is a particular name for it? In my mind i think i need to provide user interface design as a wireframe and the features that i want but how do you provide that properly? What is expected?
Depends on the developer and his purpose. Is he also doing html and graphics or just the backend. But regardless some sort of flowchart, maybe a UML diagram would help. With features described. A good developer can determine what a person with zero computer experience at all wants so honestly I wouldnt worry about it
I intend that the person who will do the web design will be a completely different person, so what i would expect from the developer would be the backend and for that person to have enough understanding of the importance of usser interface design but not for him/her to be a UI designer. A flowchart, i will look into that more deeply and UML too, while looking for info recently ive kept seeing UML mentioned. The last thing that you mentioned though, im thinking the opposite, im actually very concerned with it and wouldn't expect a developer to be trying to work out what i want, currently im trying to get a clear understanding of what i will provide to a developer so that i can give him/her a wireframe, possibly the other things that you mentioned and because it will also help me in the sense that i must understand what and why im having it built and who it will be for. My intention with the app will be constant iteration as i get feedback from users, i will be using the customer development approach so it wont be a case of just getting it built then nothing to think about.
Yes make sure the developer codes the backened as so you can have the frontend easily integrated. The developer should work out whatever you want, dont forget YOU are paying him, so he should do everything he can to accommodate you. It is good to know what you want, its even better to know how to explain it, but it should be a Q&A between you and him. Him asking questions trying to figure out what you want.
I will still do everything that i can to try and present as much information to the developer as i can but its refreshing to read what you said, my recent questions in various places have been met with quite hostile answers from programmers which gave me an impression that many might be a challenge to work with, as you say though it should be a Q&A between myself and the developer. Hopefully if i find the right developer and can discuss it properly with him/her i can then get a better understanding of their way of working on web apps.
We arent all hostile or get offended easily, which is probably what happened. I would imagine they took what you said the wrong way and felt you thought programmers werent good a comprehending requests
thats good to hear, i will try and help the developer (when that times comes) with what i mentioned above and i will keep an open mind as i imagine that a lot of developers will know better ways of doing certain things, thanks very much for your advice i appreciate it.