an engaging
website is not an
exact science.

I am a ux engineer/frontend developer with an eye for a great user experience.

Just back from a wonderful assignment

As frontend development is moving towards frameworks at a fast pace, it calls for frontend professionals that are focussed on component building and backend integration. That is why a big chasm has opened up between what designers want and how frontend developers follow up on that.

Closing this gap, and making sure that design and development sing from the same songsheet, calls for a new specialist professional. Enter the UX Engineer.

What I add to the design process

I advise design teams about everything that is possible in frontend so we are sure we can design to the limits (and often further).

Most important in UX/UI design is thorough testing. I build one or more prototypes of a new design idea in real code, so we can get the "feel" of an interface much more true than with just wireframes, PSD or Sketch files. Think of being able to measure actual click behaviour and seeing animation in real-time.

Because a prototype is in code, I can make changes very fast – during a test if needs be. Think of animation speeds and directions, font sizes or colour changes.

If A/B testing is involved, then we're in luck: the frontend code used for the prototypes is moved straight into the A/B test.

And once a prototype has tested great, the code is re-used in the actual development of the new feature. Nothing is wasted.

 

Am I necessary?

Do you wonder why you should engage a UX engineer? Here are some articles that shed light on the problem of bad communication between designers and developers:

My projects

Let me show you some of the things I did. Click here for a peek at some of my projects