Hi,
We're two people with a new idea that we're currently trying to build into an app for iPhone and Android.
Since we're good designers our selfs and know exactly how we want the app to look and work, we are just looking for a programmer to write down "the codes". In the present, we have been posted the project briefly on vworkers.com.
BUT we have one reflection..
We are affraid of exposing our whole idea, design+function, to someone we do not know. It would feel safer to just expose the function, very objectively.
But anyway, the "programmers-manual" has to be pretty specific for it to be come the way we want, we have found out (ha ha)..
Maybe we just should trust the programmer we hire? I have a hard time finding another solution.
TO THE REAL QUSETION:
- How and with what do we simplest and BEST write our "programmers-manual"?
Programs? Tips? Tricks?
We have everything sketched on paper, but not on the computer.
I could not find any old post to answer my question completely.
If you don't trust the programmer, don't hire them. You can try a NDA but most non-company developers hate it.
I think an NDA (non-disclosure agreement) is essential in protecting your ideas. If you have a signed NDA and your programmer steals your idea, you have a clear, open-and-shut case to sue them and recover damages.
I would refuse to hire any consultant who would not sign an NDA before seeing my company's confidential plans and designs. NDA's are standard fare in this industry, and any programmer who won't sign one is not grounded in reality. (Assuming it's a reasonable NDA that is).
We use a very even-handed NDA that works both ways, and offers protection to both parties. I would suggest avoiding a hostile, "What's ours is ours, and what's yours is ours, and if you even think about taking our stuff, we'll kill you" sort of NDA. Find one that's fair and balanced. You're less likely to get pushback from your developer that way.
Check out this password generator app that shows various techniques including using a data container singleton object to share data between objects in your project.
- How do we expose our "project" to the programmer?
What do the programmerwant to know and what is the most common tool the developer/designer/employer uses to expose it for the programmer?
- How do they want it?
- How do you guys do?
- How do we expose our "project" to the programmer?
What do the programmerwant to know and what is the most common tool the developer/designer/employer uses to expose it for the programmer?
- How do they want it?
- How do you guys do?
I would be glad for any answers!
The less information about design/purpose you're willing to expose to the programmer, the less likely you'll be to end up getting what you want.
This needs to be a very collaborative process. If the programmer isn't allowed to understand what you are trying to achieve, the programmer won't be able to implement it for you properly. And it will be a very frustrating project for both parties.
__________________ Recall It!Tag your notes. Tag your photos. Tag your thoughts. Tag your life.
If this is a larger project, you could hire the programmer for a small 1 week project and see how he/she does. If they work well with you, then let them know about the larger project.
It's never easy to find someone good that you trust and works within the timeline and price point, but once you found the person to do all that, you MUST open up everything the programmer needs.
I've done many projects and almost all of them, the other party changes things after the fact.
Most are going to want a per hour pay rate, some will do fix-price jobs, but either way it's in your best interest to have all the details spelled out from the start.
Building a manual for programmer...
Linear Mode
