...can be found on our updated blog. We switched to another blogging engine, so we can make all posts ven more interesting! Check it out: Codigy Blog

Yes, comments will be added to the blog as soon as we get to it... :-)

Problem with ambition is; your own site is always one step behind :-P

Traditional Festival Guides

Summer is coming, festivals are coming... Good news for music fans all around the world!

But how to explore those festivals? Which band is playing where and when? We are all familiar with the paper, analog "festival guides" which are handed out at the festival. The problem is; most of us lose the damned thing the first time we touch the festival grounds!

The new generation of smartphones have triggered a massive use of internet and mobile applications. Last year, this resulted in the first "phone-driven" festival guides. In our opinion; they had a lot of potential, but failed horribly in the execution (at least here in the Netherlands).

New opportunities

The problem is; most people (and developers) look at a mobile phone as a new way to browse the web. Native mobile applications are targeted to bring the same functionality as their web counterparts. But to be honest; mobile phones (and even the iPhone) are so-so devices to browse the internet. Their displays are to small, our fingers to big and the network connections are often too slow. So when we are building applications, we should focus on the extra functionality such a device brings instead.

When we look at the current mobile festival guides we see the same, global, trend; applications are focused on bringing the information the same way as traditional "paper" festival guides and festival sites. This results in hard-to-navigate interfaces combined with to much unnecessary information. By using the information a user gives us through his mobile phone, we could push information based on the position or mood of the user! This results in a focused, interactive experience which couldn't be done with the traditional information channels...

Stay tuned for more information! :D

We decided to give our site a fresh new look!

The new look compliments our creativity, way of work and strategy in a better way then the previous look and feel.

We all know; good web applications don't come cheap...

And in most cases, money is needed to create a good, solid web application. To bad that you don't always get what you pay for; you pay for the hours needed to create, for instance, a blog module. While internally, the module is just copy-pasted from an other, older project. This is as unfair to the client as it is inefficient to the developer.

Copy paste syndrome

By copy pasting the module from an older project, the developer forces himself to maintain and support the specific module twice (or often a lot more). This normally isn't a problem when the modules stay to share the same code base. When a client needs a specific addition to the module, the sources start to drift apart and fixes or functionalities in the first module aren't reverted back to the duplicated module; here is where the pain starts.

The client, who once bought the blog module, payed a sum of money to get a duplicated version but doesn't get the extra functionality which is developed later on. If the client desires those extensions, he or she just has to buy the "2.0" version. But how hard is it for the developer to just revert those changes back to the client when ever those are made? Well normally, quite hard... As noted earlier most non-specific modules tend to evolve in something specific overtime.

So aren't these functionalities added because of the extra time it takes to revert them, or does the developer just want to charge the client twice? Both reasons share the same basis; profit... It simply isn't very efficient in terms of profit to spend extra, non payed hours just to please a costumer with functionality he didn't desire in the first place.

But when you look at terms of quality and customer satisfaction, you bring your service to a whole new level!

Higher quality

We believe in the latter; happy customers mean more profit in the end and does good things to the karma of the company. This is why we use the following strategy when in comes to selling non-specific modules like blogs, webshops, CMS or CRM systems; you buy it, we support it!

We like to host the applications you use on our own servers, in this way we can provide the best service and quality possible. For trusting us in doing that, we will update your applications with additional functionalities and fixes as long as you stay with us!

How do we do this? By hosting the applications ourselves, we can assure that all of of client's applications share the same source-code. If a bug is fixed for Client A, it's automagically fixed for all the other clients. If we want to sell the new and fancy "2.0" version to Client B, all the other clients automatically have the fancy, new version! Easy isn't it? The only difference in the modules is the additional, functionality the client desires which don't belong in the "standard" version (which is the reason why he / she has to pay for this extension).

In this way, it's like constantly getting a new, up to date version without paying extra!

Keep an eye on this blog for further information and an exciting announcement we are going to make about a wonderful product!