WorksAbout

Contact

プロフィール
(
Profile
)

About Me

( PROFILE )

I’m Luke — a digital designer and developer based in Brisbane, working with clients and teams globally.
I focus on building calm, considered digital experiences that balance visual clarity with technical depth — from brand-led websites to complex, CMS-driven platforms.

My work sits at the intersection of design and development, allowing decisions around layout, motion, and interaction to be made as part of a single system — not separate phases.
The result is work that feels intentional, scalable, and built to last.

Collection of books used as inspiration and education

( PRACTICE )

Experience

My background spans UI/UX design, front-end development, and motion — with experience building booking systems, product catalogues, and content-heavy platforms.

I work across both visual tools and code, using platforms like Webflow and Framer where they make sense, while also working with modern front-end frameworks where project requirements demand it.

This allows me to move fluidly between concept and implementation — ensuring ideas translate cleanly into production without compromise.

( DESIGN PHILOSOPHY )

My approach

My approach is shaped by designers and thinkers who prioritise clarity over decoration — including Dieter Rams, Shigeo Fukuda, Yusaku Kamekura, Paul Rand, and Massimo Vignelli. Their influence continues to inform how I think about hierarchy, systems, and restraint.

I’m also influenced by Japanese and Swiss design more broadly — not as surface-level aesthetics, but as ways of thinking about balance, intention, and reduction.This carries through into how I structure interfaces, design motion, and approach problem-solving.

( FOUNDATION )

Before moving into web and digital design, I studied interactive entertainment and animation — originally with a focus on game development and 3D. That foundation still shapes how I think about interaction, spatial design, and user feedback — particularly in motion and micro-interactions.

Outside of client work, I continue to learn and experiment — exploring motion, 3D workflows, and front-end development, while also studying Japanese language and design culture.

Technology, games, and digital systems have always been a core interest — not just as tools, but as experiences shaped by thoughtful design decisions.

( PROCESS )

How I work

I value clear communication, considered collaboration, and a structured workflow. Projects typically begin with alignment around goals and constraints, followed by iterative design and development — sharing progress early and refining as we go.

Whether working independently or alongside larger teams, the focus remains the same: bringing clarity to complexity and creating work that feels purposeful, human, and enduring.

Credentials & affiliations

Framer logo

Framer Partner

Webflow logo

Webflow Partner

Billy Blue School of Design logo

Billy Blue College of Design (Torrens University)

If you’re looking to build something clear, structured, and built to last — let’s talk.

Start a conversation

Frequently asked questions

( 01 )

What kind of clients do you work with?

I work with businesses that value thoughtful, intentional design — from startups and small teams to more established brands.

The size of the company matters less than a shared focus on clarity, quality, and meaningful digital experiences.

( 02 )

What services do you offer?

I work across both design and build — from brand and interface design through to interaction and front-end implementation.

Each project is approached as a system, spanning strategy, structure, and delivery.

( 03 )

Do you use a particular platform?

There’s no default platform — the choice depends on the structure, goals, and complexity of the project.

The stack should serve the idea, not define it.

( 04 )

What does your process look like?

Every project begins with clarity — understanding the business, audience, and intended outcome.

From there, structure and interface are defined before moving into build and refinement.

The goal is always the same: a final product that feels considered, performs well, and holds up over time.

( 05 )

How long does a typical project take?

Timelines vary depending on scope, but most projects take between 4–10 weeks from kickoff to launch.

Smaller builds can move faster, while more complex systems and integrations may require additional time.

( 06 )

Do you offer ongoing support after launch?

Yes — I often continue working with clients post-launch to support updates, improvements, and ongoing evolution.

The aim is to keep the system performing and adapting over time.

( 07 )

Why is there segments of Japanese on your portfolio?

I’m heavily influenced by Japanese graphic design and currently learning the language.

These elements are included as a reflection of that influence — and as a small layer of interaction within the work.

( BACK TO TOP )