Case Studies

My "Company of One" approach is built on a simple philosophy: building things that are simple, strong, and timeless. Here are a few examples of that philosophy in practice.

Principle: Strength & Performance

The Challenge: A major brand needed a website that was not only beautiful but also incredibly fast and reliable, capable of handling huge amounts of traffic without breaking a sweat.

The Result: We built what I call a "Champions League" website, focusing on high-performance engineering from the ground up. The full story details the technical choices we made to deliver a world-class experience.

Champions League of Webdesign

Champions League of Webdesign

Cutting-edge technology meets top-tier digital demands

Creating a high-performance website is an art form that blends cutting-edge technology with an eye for design and commerce. At escape.nl, home to one of Amsterdam’s most iconic venues, every detail reflects the precision and care required to deliver seamless, engaging experiences to large audiences. This post highlights often-unseen details with big impact.

Principle: Simplicity & Scalability

The Challenge: Ordering food online is often a complex and frustrating process. The goal was to design a system for restaurants that was simple for customers to use, easy for owners to manage, and smart enough to handle the chaos of peak dinner hours.

The Result: By designing a scalable application and a thoughtful user interface, I created a frictionless food ordering experience. The posts below dive into the architecture and design thinking behind it.

Designing a multi dimensional capacity queue

Designing a multi dimensional capacity queue

Managing kitchen-, delivery- and pickup capacity

This month I needed to create additional dimensions to a capacity queue mechanism. The food ordering app that I created needed to be able to restrict capacity based on the number of orders, the contents in individual orders and the dispatch type (takeaway/delivery). Read along to find out how I used a Lambda Architecture to do this.

Linking Lemmid Store with kitchens

Linking Lemmid Store with kitchens

Integrating with external systems that you don't control

As part of the food ordering app I am building, I needed to design a reliable way to link the app to external systems. These external systems are beyond my direct control and include different checkout registers, kitchen management systems and ticket printers. Read along for more on designing for the unknown and unreliable.

Scalable application design without magic

Scalable application design without magic

Leveraging client computing power for high performance with many users

As part of the online food ordering app I'm building, I needed to design a scalable backend infrastructure that could handle lots of concurrent users. Scalability is considered a hard problem to tackle. Often it's presented like it's something magical, done by million dollar companies using secret tools. But, there is no such thing as magic, or is there?

Designing an interface for a food ordering page

Designing an interface for a food ordering page

Striking a balance between powerful options and mobile usability

Online ordering pages are more important than ever before. The COVID-19 virus, the resulting lockdowns and the social distancing rules have emphasised the need for a well-designed webshop user interface. This is surprisingly hard to get right!

Principle: Timeless Architecture

The Challenge: A large international company needed to decide on the foundational structure for their software. The choice would impact their business for the next decade: should they build one giant system, or many small ones that talk to each other?

The Result: My role was to act as a strategic guide. We carefully mapped out the pros and cons of each approach, cutting through the hype to find the right answer for their specific needs. This process of clear thinking allowed them to confidently make the best long-term decision for their business.

Monolithic vs Microservices software architecture

Monolithic vs Microservices software architecture

Choosing the right design for your app development

This week I flew to Gothenburg to meet people from a large international shipping company, talking about the development of enterprise level software. During the meeting there were various experts in the room, one of them asked me on choosing the right software architecture (for big, complex, enterprise level apps). A very good question, well worthy for a blog post.

Think your project could be the next case study? Let's talk about building something great together.

Contact