FinTech

Maclear

A deep frontend and UX refactor for a Swiss P2P business-investment platform

After the audit it became clear that isolated frontend tweaks would not solve the real issue. We chose to modernize the client layer and rebuild the frontend on a current stack so speed, maintainability, and UX could improve together.

Visit the project site
Maclear
Client
Maclear AG, Switzerland
Industry
FinTech / P2P
Project type
Frontend refactor / UX modernization
Focus
Vue 3, Nuxt, speed, maintainability

After the audit it became clear that isolated frontend tweaks would not solve the real issue. We chose to modernize the client layer and rebuild the frontend on a current stack so speed, maintainability, and UX could improve together.

What makes this case strong
we know when to patch and when to rebuild the right layer
we can modernize fintech products without sacrificing stability
we improve UX through architecture, not only through UI polishing

Project context

The platform was already live and used by private investors and the SME segment.

Accumulated frontend debt was slowing the interface down and limiting product growth.

Initial task

Step 01

Reduce technical debt in the client layer.

Step 02

Improve responsiveness and first-render performance.

Step 03

Preserve the density of financial data while making the experience cleaner and easier to use.

Challenges and constraints

This was not just a delivery project built around a list of requirements. The approach had to account for environment constraints, the live state of the existing system, and the cost of mistakes in real use.

01

An outdated stack and a fragmented frontend architecture.

02

The working platform could not be paused for a risky rewrite.

03

High data density had to coexist with a lighter, more readable UX.

What we did

01

Ran a frontend audit.

02

Identified the most critical technical debt and constraints.

03

Rejected the idea of patching the old layer piece by piece.

04

Moved the client side to Vue 3, Composition API, and a more current Nuxt stack.

05

Improved interface speed and first-render performance.

Key decisions

01

Instead of patching the legacy layer, we modernized it as a system.

02

We treated the balance between dense financial data and a clean UX as a core product decision.

Results

The interface became noticeably faster.

First-render and response speed improved.

The impact of outdated libraries and legacy debt was reduced.

The product received a stronger frontend foundation for the next stage of growth.

Our role in the project

frontend architectureUXperformanceproduct refactor

What this project shows about our work

we know when to patch and when to rebuild the right layer
we can modernize fintech products without sacrificing stability
we improve UX through architecture, not only through UI polishing

If you have a similar challenge, let’s define the right way to approach it

When frontend debt starts blocking growth, the answer is often not a cosmetic redesign, but an architectural shift.