Meet Our Core Development Principles

Through 100s of projects, we’ve crossed the digital landscape through perseverance and have refined a core set of beliefs as to how to drive the development process.

Always with an eye for delivering quality products, providing timely deliverables and being on-point, honest and clear in our communication, we deliver on these “commandments” to bring our clients to the promised land.

1. Follow universal standards

We’re not looking to reinvent the wheel. Good code is clean code and it’s readable, understandable and workable for others to take it on further down the road. By keeping things simple and updated according to recognised standards, we secure that any member in our team can pick up the work. Which means less risk for the product owner.

2. Mobile mindset first

Everything we do from design to development needs to adhere to the norm of responsive. Adapting to mobile is not simply adjustments during coding, — it requires careful thought and outlining in the conceptual phase. To get it right, we secure the cross-browser and cross-device support is there.

3. No repeats for easy updates

Don’t repeat yourself. Our aim is to only do things once in development, which means rather than writing things multiple times where needed, we cross-reference and centralise. This allows us to only go to one place, when a change request arrives. In that sense, smarter architecture means easier maintenance.

4. Apply powerful tools

Where it makes sense during our development and testing phases, we utilise tools for automation and better performance testing — for instance CSS preprocessors SASS and LESS. These help in cross-validation and to reduce human error. And speed up development.

5. Customise without compromise

Squashing our designs into 3rd party preprovided templates is a complete no-go. We always code our front-end templates from scratch to adhere to the basic ideas and concepts of the design. Not only for aesthetic pixel-perfection reasons, but just as much for performance and user-related concerns.

6. Proactive optimisation

Planning the promotional search engine visibility of products and services needs to take place in the very early stages of the project lifecycle, not as a last-minute configuration. Given the nature of the information architecture and system setup, we incorporate tools and workflows to get it right.

7. Developing the right “feel”

Movement. It takes some skill and experience from front-end developers, but it’s what lifts the experience from 80 to 100+. How things appear, how they move upon interaction, how you’re introduced to new elements on scroll. We certainly haven’t seen the end of this one yet.

8. Dead-simple, friendly interfaces

When we’re delivering a solution, the interface towards the end user is just one side to the coin. On the other end, we’ve got the editorial worktool managed by the client-side, often with great intensity. Here, it’s pivotal that the structure and logic of the administration tool is well thought through and that it delivers on what it should.

9. Cloud machines that last

A hosting solution should live up to the following criteria: Performance, security, flexibility, ease-of-use, cost-efficiency. For these reasons, we always suggest that our clients own the hosting account directly with the cloud provider and then gives us administrative and technical access. That leaves zero middleman and provides longterm accountability.

10. Document for autonomy

When building a technical platform, we don’t provide full code documentation, unless specifically requested. It would be waste of time and money for most our clients. Instead, we do inline code commenting, and we provide a CMS manual with overview of how to manage the service after launch.