Brick City Loft

Brick City Loft was a complete design and Webflow development project for a distinctive New York property.

The challenge was to translate the character of the physical space into a digital experience that felt specific to the property rather than like another generic rental template.

THE CHALLENGE

Hospitality and property websites often fall into the same pattern. Large photographs, a booking button and a familiar collection of sections. That can communicate information, but it doesn't necessarily communicate why someone should remember this particular place. Brick City Loft already had character. My job was to make the website feel like an extension of that identity while still keeping the booking journey clear and practical.

THE DESIGN DIRECTION

I built the visual direction around the personality of the loft rather than starting from a generic hospitality template. The interface needed to feel urban, editorial and premium without becoming decorative at the expense of usability. Typography, composition, imagery and spacing were used to create a strong visual rhythm while keeping the experience easy to navigate. The property itself remained the focus. The design system existed to frame it rather than compete with it.

THE RESULT

The finished website gives Brick City Loft a digital identity that reflects the character of the property while keeping the commercial goal clear. The project combines: UX strategy Visual direction Responsive UI design Webflow development Interactions Conversion hierarchy Unlike Smart Sync and FYKZIT, this case isn't about complex backend automation. And that's exactly why it belongs in the portfolio. It shows that when a project doesn't require a custom application or automated workflow, I can still take responsibility for the entire digital experience — from the first UX decision to the finished production build.

The technology changes with the problem. The standard of the product doesn't.

UX AROUND THE BOOKING JOURNEY

A visually distinctive site still needs a clear hierarchy. The booking action was treated as the primary conversion path throughout the experience. Supporting content gives visitors the information and atmosphere they need to understand the property, but secondary actions aren't allowed to compete with the main goal. This principle also influenced later discussions around expanding the experience to additional properties: exploration can grow, but booking hierarchy stays clear.

FROM DESIGN TO WEBFLOW

I handled the project through implementation rather than stopping at the design stage. The final experience was developed in Webflow with responsive behavior, interactions and reusable styling considered as part of the original design. Building the interface myself allowed me to preserve the details of the visual direction across breakpoints instead of simplifying the concept during handoff.

RESPONSIVE EXPERIENCE

The design needed to maintain its character on smaller screens rather than simply stack desktop sections vertically. Typography, spacing, content hierarchy and interaction behavior were adjusted around the available screen size. The goal was to keep the same visual identity while making the booking journey easy to use from mobile.

A SYSTEM THAT CAN EXPAND

The project also needed to leave room for the broader Brick City property direction. As plans for additional properties developed, the existing experience had to be considered as part of a larger system rather than something that would immediately need to be replaced. That led to thinking about how visitors could move between different property experiences while keeping the primary booking action clear. The important part was preserving the identity of each property without turning navigation into a competing layer over the experience itself.

DESIGN AND DEVELOPMENT AS ONE RESPONSIBILITY

Brick City Loft is a good example of why I often prefer owning both sides of a project. I wasn't designing a static composition and then handing it off. I was making decisions while already considering how they would behave in the browser, across breakpoints and inside the final Webflow implementation. That creates a much shorter distance between the original idea and the finished product.