Slashdot Mirror

← Back to Stories (view on slashdot.org)

HOWTO Go About Marketing to Developers?

Posted by Cliff on from the where-traditional-marketing-strategies-fail dept.

byrnereese asks: "My company has finally realized that one of the keys to our success will be to create a strong developer program (IBM's Developer Works, and Palm's PalmSource come to mind as examples). It just so happens that I have been appointed to lead this program. Now I have a lot of my own ideas, but I wanted to ask a large developer community directly the one question I know I am going to have to articulate a coherent answer to at some point: 'What is the most effective way to market a toolset, or development platform, to a developer in order to encourage them to build products using your product, without turning them off at the same time?'"

4 of 267 comments (clear)

  1. Make it friendly by nate1138 · · Score: 5, Insightful

    Just focus on the advantages you have over your competition. Unlike many markets, yours isn't full of people that can't tie their shoes. These are the folks building the products and systems people depend on. Many of them are even responsible for making decisions about large technology puchases for their own companies. So basically, don't lie to them, don't overcommit, and simply show why your option is best. Also, having reasonable terms of use is helpful. Nobody I know likes to be told how to use a product that they just paid for.

    --
    Where's my lobbyist? Right here.
  2. Don't lock them in by Myshkin · · Score: 5, Insightful

    One of the most important things that I look at is how locked in to a particular product will I be if I use it extensivelly. This means:

    1) If there are standards, support them.
    2) If there are file formats, document them.
    3) If there are APIs, expose them.
    4) If you discontinue support, open source the code.
    5) If the company goes belly up, open source everything.

  3. i don't think it's possible by cballowe · · Score: 5, Insightful

    I pick my tools based on what works, not based on the marketing. I listen to other developers, check news groups and web commentary, and eventually pick the right tool for the job.

    The better the tool, the faster word will spread but it's gotta be a significantly better tool for its intended purpose than what developers are already comfortable with otherwise they'll have no reason to switch. Picking up a new tool requires a temporary drop in productivity - the only way to offset this is to have it be much easier to work with in the long run.

  4. Free is good, not not required. by haplo21112 · · Score: 5, Insightful

    Honestly if you want me to use your tools:
    1. Good! no Excellent documentation is a must, if I can't figure out at least the basics of how to use the product in about 5 minutes...I don't have time for it...I'll move on to the next guy or just use what I already have...
    a.) Lots of code examples, and documnent everything, assume nothing...
    2. Stright forward use.
    3. have people that have a clue ready to answer my questions if I am still lost.

    --
    Power Corrupts,Absolute Power Corrupts Absolutely, leaving one person(group)in charge is absolutely corrupt.