We like open source a lot and have extensive experience with PHP as well as MySQL database. Other language we develop in are Java, Ruby and we’ve dabbled a bit in Python, but like any good developer we can adapt to different languages in a very short period of time.

As a lot of the applications we development as web-based, we are up to date with the latest web technology like HTML5, CSS3 and awesome new things like WebSockets. To speed up development we use libraries like jQuery and jQuery Mobile, or Sencha Touch if you prefer, and on the server side frameworks like Kohana and Spring take care of security as well.

To allow us fast turn-around times and good feedback to clients we’ve adapted methodologies like the agile methodology to deliver software that is not only of great quality, but also is exactly what the client needs.

We believe that each approach has its merits and much depends on the application that needs to development and whether the client has a clear vision off their requirements or not.

If the client has a clear vision then there is great advantage in doing an upfront design of the entire system, like the waterfall approach suggests, but not going into the level of detail this approach needs. This provides our team with a clear understanding of what the client wants and gives us the opportunity to accurately estimate the costs that will be involved in creating the application. But it is important to note that even when we have done an upfront design, we still split the project in small sprints and involve the client in each step, because we have learned that even the most clear “visioned” client will still require changes along the way…

Once we know what the client wants (either the entire application, or just a part of it) the we start developing the software in small incremental “batches” referred to as sprints in the agile world. After each sprint – which take from one week to a month – the client is presented with the newly completed features that were developed during that sprint. After discussing the changes with the client it is decided which features will be implemented during the next sprint or if a change is required to the design. Once that is done the next sprint starts and the process repeats itself until the final product is delivered.