Back to work

SaaS UI and front-end

Linear.app Exercise

Linear.app Exercise is a precision lab: a way to study how a high-end SaaS brand organizes messaging, visual layers, motion, contrast, and components so the product feels fast, serious, and desirable.

Screenshot of a Linear-inspired SaaS landing page with a dark interface and product details.

Year

2024

Duration

2 weeks

Budget range

Internal lab

Service

Product lab

Case notes

What had to be solved and how it was shaped.

Open live project

Challenge

The challenge was avoiding a superficial copy. The work had to understand why the interface works: hierarchy, spacing, density, contrast, alignment, section rhythm, responsive behavior, and perceived speed.

Solution

I built a landing page with Next.js, TypeScript, Tailwind CSS, and Framer Motion, separating sections and components to keep visual consistency, subtle animation, and controlled responsive behavior.

Outcome

A polished landing page that shows visual precision, fast execution, product judgment, and the ability to build detailed SaaS interfaces.

Results

  • Coherent visual system inspired by premium SaaS
  • Responsive components with subtle animation and polished states
  • A demonstrable base for projects where product perception matters as much as code

Scope

Visual analysisUI engineeringResponsive designMicrointeractionsPerceived performance

Technology

A stack chosen for the job, not for decoration.

Next.jsReactTypeScriptTailwind CSSFramer MotionVercelResponsive DesignComponent ArchitectureSaaS UIMotion Design

Capability map

Every layer that makes this project substantial.

Reference analysis

The exercise starts by understanding the visual system, not by copying pixels without judgment.

  • Reading hierarchy, density, contrast, and section rhythm
  • Identifying SaaS patterns: hero, product proof, trust, features, and calls to action
  • Translating the visual language into maintainable components

SaaS composition

The page is structured so the product feels fast, clear, and technically serious from the first viewport.

  • Hero with message, visual context, and primary action
  • Sections with editorial rhythm and product progression
  • Careful use of dark backgrounds, dividers, cards, and interface layers

Component system

The implementation separates repeatable blocks and pieces so the landing does not become rigid.

  • Components for sections, buttons, cards, pills, and product visuals
  • Tailwind classes organized for consistency
  • Structure prepared for iteration without rebuilding the whole page

Microinteractions

Motion is used to improve perceived quality, not to distract.

  • Subtle animation with Framer Motion
  • Smooth transitions for states and highlighted elements
  • Fast perceived response when interacting with the interface

Detailed responsive design

The layout preserves visual intent across large and small screens.

  • Hierarchies adapted for desktop, tablet, and mobile
  • Spacing, line breaks, and imagery controlled to avoid overlaps
  • Sections designed for scanning, not only for looking good in a screenshot

Product judgment

The value of the exercise is proving that I can read a premium interface and rebuild its decisions.

  • Clarity prioritized before decoration
  • Visual details used to build trust and serious software perception
  • A base applicable to dashboards, SaaS landing pages, and B2B products

Next project

If your website no longer represents what you do, it is time to rebuild it with intention.

Start a conversation