Front-end development is the process of building the part of a website or application that users see and interact with: the interface. At Cube, we don’t treat that part as an afterthought, but as the component where a product’s promise is made or broken. That’s why we build front-end code based on a few core principles: accessibility, discoverability, and maintainability starting from the very first line.
The front end of your software: everything that happens on the screen. The buttons, the layout, the interaction, and the speed at which a page responds. Built using HTML for the structure, CSS for the design, and JavaScript for the behavior. The back end is its counterpart: the invisible side where data, logic, and security run on the server. What sets us apart is that we rarely view these two separately. The interface retrieves its data from somewhere, and the quality of the whole is determined by how well those layers work together. For us, the front end is where the end user experiences the value of a system, and that imposes certain obligations.
This is where our perspective begins. Modern tools, including AI assistants, can now rapidly generate front-end code that works at first glance. A button appears, a form submits, a page loads. We use these tools ourselves every day, because they make us faster. But we set the bar higher than just “it works.” Code that looks great in the browser can completely exclude a user with a screen reader, or leave Google in the dark about what’s on the page. Accessibility and discoverability don’t just happen on their own. They require the correct HTML elements, a logical structure, and testing against actual guidelines. That’s exactly where we combine the speed of the tools with our experience to identify what’s still not quite right. Building quickly and building correctly, rather than sacrificing one for the other.
Four guiding principles
Accessible from the first line.
For us, accessibility isn’t just an afterthought—it’s how we start. Semantic HTML, full keyboard navigation, and support for screen readers are built in as standard, and we test for compliance with WCAG 2.1 AA, the international guideline for digital accessibility. Since the European Accessibility Act came into effect (June 28, 2025), this has also become a legal requirement for many organizations. For us, the reasoning is simpler than the law: an interface that works for everyone works better for everyone.
Searchability is in the code, not alongside it.
Whether a search engine understands a page is determined in the front end, not in a separate optimization round afterward. A proper heading structure, semantic layout, fast load times (measured against Google’s Core Web Vitals), and structured data where relevant: that is the foundation upon which a custom software solution is found. We build that foundation right from the start, because fixing things later always runs up against the limits of the structure.
Components and a design system.
We don’t build every button and form from scratch; instead, we define reusable building blocks in a design system. Color, typography, and spacing come together in design tokens: a single, central source of truth. You’ll notice the benefit whenever a change is made. If we adjust a color or a component style in one place, it updates everywhere. This keeps the interface consistent and maintenance affordable, even as a product continues to evolve over the years. It’s also where the design, UI design, and our code intersect.
Maintainable code you'll be grateful for later.
You may not see the quality, but you’ll definitely notice it. Running in the background are automated tests, linting, type checks, and monitoring that catch errors before a user encounters them. Responsive design and progressive enhancement are the foundation here, not just an extra option: the interface works just as well on a phone as it does on a large screen. The result is code that you can continue to develop two years from now without every change breaking something else somewhere else.
There is no single “right” approach to front-end development; the choice depends on the project’s requirements. For interactive interfaces, we use Vue or Livewire, supplemented by Alpine.js for lighter interactions and Tailwind CSS for consistent styling. For logic that only appears in specific places, we use our own Lazymodules package: that code is only loaded when it’s actually needed, so the initial load time on other pages remains fast. We decide which combination to use on a case-by-case basis.
Vue.js, an innovative JavaScript framework, enables you to create dynamic and interactive web applications. It offers not only speed and flexibility but also a modular architecture suitable for both simple and complex projects. Its excellent documentation and performance make it even more appealing.
CSS defines the presentation of HTML elements on a webpage. It allows you to manage the styling, colors, fonts, and layout, making websites visually appealing and user-friendly.
Tailwind CSS offers a utility-first framework for CSS, giving developers full control over styling through low-level classes. This promotes the development of consistent and responsive designs, while significantly reducing development time.
HTML is the core of every website, providing structure and layout for web pages. It enables a functional and accessible online experience by defining elements such as headings, paragraphs, and links. HTML works together with CSS and JavaScript to create a responsive web design.
JavaScript is at the core of dynamic and interactive web pages. This language enables the creation of animations, form validations, and complex interfaces, resulting in functional and visually appealing web applications.
Livewire offers a Laravel framework that combines the simplicity of PHP with interactive web functionality. This enables the creation of dynamic applications with less JavaScript and real-time updates.
Alpine.js is a JavaScript framework that makes it easy to add interactive elements to your webpages without complex overhead. It offers an intuitive syntax for dynamic and responsive user interfaces.
WebGL uses a JavaScript API to enable 3D graphics directly in the browser, without the need for plugins. With WebGL, you can create stunning 3D visualizations and interactive graphical effects, resulting in a rich user experience.
Inertia.js simplifies the web development process by combining server-side rendering with client-side JavaScript frameworks such as Vue.js and React. This results in fast, dynamic applications without full page reloads, greatly enhancing the user experience.
Front-end rarely stands alone. The interface retrieves its data from the systems behind it: a CRM, an ERP, a DMP. That connection runs through middleware that links systems, and underneath that lies the back-end that manages the logic and data. We deliberately develop these layers as a single cohesive system, because otherwise you’ll run into seams sooner or later. Where appropriate, we build the front-end as a headless application separate from the back-end using a framework like Nuxt on top of Vue. The layer beneath it then remains fully replaceable or expandable on its own. This is the same philosophy that runs through our entire approach, from creation to ongoing development: building things that work together rather than separate components that just happen to sit next to each other.
Are you looking for a front-end developer, or do you want to have your front-end developed by a team that looks beyond the code? We don’t just assign a few people to your project who’ll deliver a template and then leave. At Cube, you get a team that builds front-end solutions as part of a comprehensive, accessible, and maintainable solution—one that you retain full ownership of. With over 15 years of experience in custom front-end, middleware, and back-end development, we know how these layers come together. Strategy, design, and technology are all part of one team, based in the Netherlands, and we think about the big picture—not just the specific part you happen to be outsourcing.
We help corporations operate like startups, and startups grow into corporations.
Let's connect
Jarno is happy to work with you to find a solution. No quote, no obligations, just clarity.
Pure Energie: From green ambition to pure results.
From startup to scale-up: a solid technical foundation for Vista Hypotheken.
How FC Twente scores digitally with a cutting-edge app and website.
Legal Mind: A digital foundation for an ambitious AI platform.
Phageguard is generating more leads with an award-winning website.
How Thermen Resorts extends the tranquility of its resorts to every digital experience.
Nou is strengthening its brand position with a customer portal, app, website, and online store.
Amber Projectmanager
_lagekwaliteit.-2.jpg&output=webp&q=90&hash=MTc1NDI5MTI2NA==&w=540&h=660&fit=cover&a=top)
Bart Developer
Bernard Developer
Bob Test Engineer | Security & Privacy
Demi Officemanager
Dennis Full Stack Developer
Guus Full Stack Developer
Jarno Business Director
Jarno Back-end Developer
Jasper Developer
Jenne Digital Marketeer
Jeroen Back-end Developer
Job CEO | Executive
Joost Tech Lead | Team Pentagon
Jordy Software Architect
Justin Tech Lead | Team Hexagon
Kees Projectmanager
Kevin Developer
Laura Digital Designer
Maartje Content Marketeer
Mans Operations Manager
Marcus Projectmanager
Marleen Projectmanager | Team Lead Octagon
Mart Front-end Developer
Melanie Projectmanager | Team Lead Hexagon
Mick Tech Lead | Team Nexus
Nicky Projectmanager
Onno Business Controller
Remi Software Architect
Rogier Business Consultant
Rosan Manager People & Organization
Roy Full Stack Developer
Ruben Full Stack Developer
Ruben Digital Designer
Sander Developer
Stijn Front-end Developer
Tamara Business Consultant
Thomas Back-end Developer
Tom Tech Lead | Team Octagon
.jpg&output=webp&q=90&hash=MTc3MTg0MzIwMw==&w=540&h=660&fit=cover&a=top)
Wesley Projectmanager
The front end is the part that users see and interact with: the interface, built using HTML, CSS, and JavaScript. The back end is the invisible part: data, logic, and security on the server. The middleware connects the two, ensuring that the interface displays the correct data.
Cube builds accessibility in from the very first line and ensures compliance with WCAG 2.1 AA: semantic HTML, keyboard navigation, and support for screen readers. Since the European Accessibility Act (June 28, 2025), this has also become a legal requirement for many organizations.
Cube uses Tailwind CSS, Alpine.js, Vue, and Livewire, supplemented by its own Lazymodules package. The choice depends on the project. Components are defined in a design system to ensure that the interface remains consistent and maintainable.
A design system defines colors, typography, spacing, and components as reusable building blocks (design tokens). This ensures that design and development speak the same language, keeps the interface consistent, and allows a change made in one place to be reflected everywhere.
Yes. Cube builds its front-end with proper SEO techniques: semantic HTML, a logical heading structure, fast load times (Core Web Vitals), and structured data where relevant. That discoverability is built into the structure itself, not through separate, after-the-fact optimization.
