The making of xCoder 2010 – part 1

February 21, 2010

When I started the work on xCoder 2010 back in August 2009, I had no idea what the name would be. I didn't exactly call my project "xCoder" internally, but I did have another codename for it. I wasn't really sure what direction I should go, but I already had some ideas that I knew I wanted to do no matter what, so I started with those. The big question, put in my mind by several customers, was whether to combine phpCoder and WebCoder or keep them as separate products, and if they should be combined, which name should be used? With the feedback from the xCoder 2010 forum, as well as feedback obtained from a range of trusted customers, I slowly made the decision: I wanted one application with the best from both worlds, mainly because people seemed to be bothered by the fact that they had to choose between two applications. My initial idea was to use a brand new name for this merged application, but I'm simply to fond of the WebCoder name to let it go. In other words, xCoder 2010 will be TSW WebCoder 2010, with the very best from phpCoder 2008 and WebCoder 2009 and a range of new stuff as well! I think this is what people want, and the more I think of it, it's what I want as a webdeveloper too.

This has all been very theoretic, but I promise that in my next post, I will start to show you some of the new goodies from WebCoder 2010. Stay tuned :)

Kasper (TSW) @ 6:05 pm in phpCoder,WebCoder

3 Responses to “The making of xCoder 2010 – part 1”

  1. BlackYeLL says:

    I think “WebCoder 2010″ is a right choice :)

  2. Anthony says:

    I personally love this idea. I hate the fact that I have to choose between WebCoder
    and phpCoder. As an additional thought, I think the customers would like this idea,
    and it may work to your benefit also. You should offer a pre-order system, where users
    get a discount somewhere around 25-50%, for pre-ordering WebCoder 2010. Also a beta
    testing system would be great too, beta testing systems seem to work best for both,
    it gives users a chance to familiarize themselves with the upcoming software, and it
    offers a free, and very effective means for developers to debug their software. For
    example, look at how effective the beta test was for Windows 7. Also as another note,
    the comment textbox for this page needs fixing, the sidebar on the right overlaps it
    when using Google Chrome.

  3. […] application means extra work and less time to focus on the stuff that really matters, so when combining WebCoder and phpCoder, I thought to my self: Why not throw in WebPad as well? So instead of releasing three different […]

Leave a Reply