About the maker

Hi, I'm Finnian.

/ˈfɪn.i.ən/ · FIN-ee-an · rhymes with “minion”, sort of

I design things that move — and write the code that moves them. Hatch is the tool I wanted for my own projects, so I hatched it.

  • Central European Time
  • English & Deutsch
  • Replies within 2 working days
fig. 02 — how it started

I learned to code because my designs wanted to move.

And I learned to animate because my code wanted to feel something. Today I do both — at the exact point where a design file becomes a living thing: interfaces, animation, and the tiny transitions that make software feel kind.

Hatch began the same way. Projects everywhere, notes nowhere, and every new Claude session opening with “so… where were we?” So I built the nest I wanted to work in — and taught the agents to leave a note for the next one.

— Finnian

An unreasonable hobby

I spend an unreasonable amount of time on easing curves.

So here's the lab. Drag the two handles and watch the egg race a linear one. Hatchy has opinions.

time → progress →

fig. 03 — drag the dots · arrow keys work too

cubic-bezier(0.20, 0.00, 0.00, 1.00)

Decisive start, soft landing. Chef's kiss. 🤌

In numbers

Four numbers I'm stubborn about.

  • 60fps

    Minimum frame rate I accept.

  • 16.7ms

    Budget per frame, every frame.

  • 1.5px

    Favourite line weight. Every outline on this site.

  • 999px

    Border radius, mostly. Pills forever.

What I do

Design, motion, code — or all three.

01

Design

Web design and human interface design — layouts, typography, systems, and the unglamorous decisions in between.

  • Web design
  • Human interface
  • UX
  • Typography
02

Motion

Motion graphics, animation and UI transitions that explain instead of decorate.

  • Motion graphics
  • Animation
  • UI motion
  • Easing
03

Code

Apps and websites, from the first pixel to the last line — native with Swift, everything else with Java, PHP, JavaScript and CSS.

  • Swift
  • Java
  • JavaScript
  • PHP
  • CSS
How I work

Five steps. Always in this order.

  1. 01Listen

    What should people feel? Everything starts there.

  2. 02Sketch

    Fast, rough, on paper and in Figma. Many bad ideas, early.

  3. 03Move

    Prototype the motion before polishing the pixels.

  4. 04Build

    Real code, real data, real devices.

  5. 05Polish

    The last two percent. Frame by frame.

Things I believe

Good design is fragile.

Questions

Asked often enough to write down.

Do you take on client work?

Yes — studios, startups and people with slightly strange ideas. Interface design, motion, front-end development, or the whole thing end to end.

Where are you based?

Maria Enzersdorf, just south of Vienna, Austria. I work with people everywhere — remote is normal, coffee in Vienna is a bonus.

Which languages do you work in?

English and German. Code in Swift, Java, PHP, JavaScript and CSS. Motion in curves.

What do you need to get started?

A rough idea, a reason why, and ideally a deadline. A few sentences are enough for a first conversation — I reply within two working days.

Why is Hatch free?

Hatch started as the tool I wanted for my own projects. Sharing it costs a server, not a business model — so no price, no ads, no tracking.

Have something fragile to build?

Interfaces, motion, code — or all three. I reply within two working days.