Behind the InterfaceUI / UX RESEARCH

Research findings

Cross-site findings on creative direction, measured typography, hierarchy, interaction, responsive design, public-source evidence, and route coverage.

Interactive studyCompare the collection.
Sep 2026

Anton 400

Desktop 1440px viewport40px
Line height: 42px
Mobile 390px viewport40px
Line height: 42px

Keeps the same emphatic type size; changes arrangement rather than scale

Bars share a 0–180px scale across all websites. These are measured CSS values, not a reproduction of the original typefaces.

Desktop and mobile UI/UX research • Reviewed September 15–16, 2026

This review treats each website as a designed product: what it is trying to communicate, how its visual system supports that purpose, what interaction adds, and where the experience breaks down. The strongest shared lesson is that distinctive websites build a repeatable visual language around a specific idea. Oversized type, dark backgrounds and animation alone do not provide that idea.

Reading this research

Observed means I inspected the live page or exercised the control. Source-confirmed means public HTML/CSS/JavaScript contains the specific configuration or handler. Within that source evidence, configured means an actual component invocation or page markup is present, and implemented means a matching handler/component was inspected. Hook only means the markup suggests an interaction but its custom implementation was unavailable. Interpretation is my creative-direction assessment, not a measured business outcome.

Desktop inspection used chiefly 1280×720 and 1440px-wide views, with some larger-window observations. Mobile inspection used a 390×844 CSS-pixel viewport. These were responsive browser tests with pointer/keyboard input, not physical iPhone/Android device tests. Screenshot frames show a moment in moving compositions, not the complete animation.

All five homepages were explored through their major sections. Navigation, galleries, menus, accordions and representative secondary templates were inspected. The route inventory covers 65 additional route requests across Ace, MONOLOG and Lama Lama. It does not mean every case image, browser state, external client site or hardware gesture was tested.

This article brings together the cross-site comparison, measured type hierarchy, public-source evidence, and route coverage. The five website reviews contain the detailed browser observations, direct screenshots, implementation findings, and complete website-specific request tables.

Website reviews

Each website has its own page with its browser review, screenshots, measured typography, public-source evidence, and route findings where available.

Style map

WebsiteStyle / themeCore creative ideaBest reference forMain tension
AceTechnical editorial; dark product studio; ASCII and limePrecision, systems and small-team expertiseQuiet technical identity; persistent conversion railMobile execution and inconsistent navigation
Arkon DigitalCinematic creative coding; iridescent 3D; terminal typographyThe site itself demonstrates the developer's craftPersistent 3D scene across routesSpectacle competes with text, especially on mobile
Neue MontréalSwiss editorial; printed travel guide; colorful type exhibitionThe typeface becomes the content and the interactionProduct-led motion and long-form art directionVery long journey and custom-control accessibility
MONOLOGWarm monochrome; brutalist editorial; cinematic textureA premium independent partner with a personal point of viewSales narrative, work presentation and founder presenceSecondary-page completeness and experimental discoverability
Lama LamaSwiss agency system; pixel graphics; cinematic presentationAn expressive agency identity applied to every interface layerCoherent brand behavior; layered portfolio explorationMany modes and controls increase learning effort

Themes across the collection

Typography is the main identity system

The sites use remarkably few conventional interface decorations. Their hierarchy comes from font character, scale, spacing, weight and placement. Ace contrasts compressed Anton headings with restrained GT America and mono labels. Arkon uses a deliberate three-way contrast: elegant script, narrow industrial capitals and technical body text. MONOLOG alternates strong sans-serif statements, unusual display lettering and small mono annotations. Lama keeps its main sans family consistent and uses mono labels to make actions feel like instrument controls. Neue Montréal makes one family demonstrate an entire range of personalities.

The useful principle is assign each typographic voice a job. An expressive title, a readable explanation and a technical annotation can coexist if their roles stay consistent. Copying all the declared font files would miss the point: shared bundles often contain fonts that are not visibly important.

Layout alternates restraint and release

Ace's fixed left rail provides stability while the right column changes. Arkon arranges content around a central object like a stage. Neue Montréal alternates dense editorial passages with enormous letterforms and immersive full-screen chapters. MONOLOG's small explanatory columns sit beside oversized statements and generous media. Lama mixes narrow control panels with broad image fields and compact project indexes.

Negative space does structural work. It gives a dominant element room, separates chapters and creates anticipation. It becomes a problem when users cannot tell whether the space is deliberate, content is still loading or an interaction is required. Empty published routes are a separate issue from intentional whitespace.

Motion should have a reason

Three particularly strong reasons appear here: demonstration (Neue Montréal's variable weights), proof of skill (Arkon's real-time rendering), and brand consistency (Lama's pixel/logo treatment across media and controls). Ace's spinning seal and image degradation add a technical signature with less visual dominance. MONOLOG uses movement to support an editorial and persuasive sequence.

Persistent ambient motion has a different job from a click response. Ambient motion creates atmosphere; click motion should clarify what changed and where the user went. These sites sometimes mix those responsibilities. A morphing scene is memorable, but a clear selected filter, readable label and obvious close control still matter.

Discovery is enjoyable until it hides the task

The rewarding discoveries include Lama's pitch deck and contact playground, MONOLOG's footer experiment, Neue's city stories and Ace's reactive image treatments. They are optional depth. Navigation, buying, reading and contacting should remain understandable without finding them. In particular, icon-only controls, unexplained horizontal strips and hover-dependent information deserve explicit touch and keyboard alternatives.

Conversion is woven into the composition

Ace keeps booking beside the work on desktop. Arkon directs attention to the portfolio rather than a long lead form. Neue keeps a purchase link visible while visitors explore the specimen. MONOLOG develops trust through work, outcomes, process and FAQs before its closing invitation. Lama repeats contact access and turns its compact menu into a form/calendar/presentation hub.

These are different strategies for different offerings. A type specimen benefits from letting visitors play with the product; a studio must explain fit and credibility; a developer portfolio can use the interface as a live sample of capability. No conversion rates were measured here.

What was measured and tested

Type was sampled at 1440×1000 desktop and 390×844 mobile viewports. Values below are computed CSS pixels, rounded where appropriate, not estimates from screenshots. Font size and line height are separate measurements; a graphic wordmark or transformed specimen cannot reliably be described by the font size of its surrounding element.

I moved the pointer across titles, buttons, navigation, project imagery, postcards, service names, footer canvas regions and team rows. Browser pointer placement was paired with small wheel increments where needed. I checked the hovered element and resulting styles, alongside screenshots. This establishes hover responses; it does not establish physical-device touch behavior or a sustained mouse-button hold. Continuously animated backgrounds were not treated as proof of pointer response merely because successive frames differed.

The suggested reading orders are a creative-direction assessment based on size, placement, contrast and motion. They are not eye-tracking results. The raw computed-style samples retain the measurements; they also include offscreen elements and animation wrappers, so the curated tables below are the appropriate reference for visible typography.

Measured type hierarchy

Numbers shown as size / line height. Tracking is letter spacing, expressed in em where useful. These are observed roles at the tested widths, not an exhaustive design-token specification.

Site and roleTypeface / weightDesktopMobileWhat the difference does
Ace service headlinesAnton 40040 / 4240 / 42Keeps the same emphatic type size; changes arrangement rather than scale
Ace explanatory headingGT America Regular 40016 / 22.416 / 22.4Reading size stays sensible, but the retained 640px box clips on mobile
Ace fixed-rail proseGT America Light 30014 / 21Rail removedQuiet supporting context beside the dominant work stream
Ace chapter labelsGT America Mono Light 30012 / 1212 / 12+.1em spacing makes small labels feel like technical annotations
Arkon “Creative”Bonheur Royale 400161.54 / 80121.15 / 80Script ascenders/descenders visually interlock with the following line
Arkon “Developer”Bebas Neue 400107.69 / 107.6980.77 / 80.77Condensed capitals keep a forceful title within limited width
Arkon biographyJetBrains Mono 40012 / normal12 / normalThe explanatory text remains small even when the mobile navigation grows
Arkon navigationJetBrains Mono 300, active/hover emphasis12 / 16.816 / 22.4Mobile route links are easier to target/read than the biography
Neue cover titlePP Neue Montreal Bold 70074.08 / 66.6729.6 / 26.64Compact .9 leading makes the title a single graphic block
Neue cover explanation / Story labelPP Neue Montreal Text Regular 40024 / 2415 / 15Editorial density comes from 1.0 leading and −.03em tracking
MONOLOG hero positioningKHTeka 50017.75 / 19.5314.11 / 15.52Small centered statement lets the wordmark and atmosphere dominate
MONOLOG founder statementKHTeka 70045 / 49.525.31 / 29.11A stronger reading beat immediately after the restrained hero copy
MONOLOG service namesKHTeka 70094 / 9433.31 / 33.31Large scale supplies hierarchy; hover adds another emphasis layer
MONOLOG process displayAnimo, computed weight 500139.5 / 125.5583.72 / 75.35A distinct display voice marks a new chapter; rendered glyphs can be transformed
Lama hero headlineSuisse BP Intl 70072 / 57.640 / 32.8 leading creates a dense, emphatic uppercase shape
Lama hero explanationSuisse BP Intl 40020.04 / 24.0516 / 19.2Readable sentence rhythm contrasts with the tightly packed title
Lama mono action labelsSometype 50010 / 1810 / 18Consistent instrument-like voice, but mobile labels remain very small

Two distinctions matter. First, computed weight is not proof of a separate font file: a browser can synthesize a requested weight. Second, “headline” can describe visual prominence without meaning an HTML h1. Ace's 40px service terms are h3 elements, while its explanatory h1 is 16px. MONOLOG's semantic h1 is its small positioning statement, while the huge wordmark carries the strongest visual presence. That separation is not inherently wrong; it means visual hierarchy and document structure must be reviewed independently.

Information hierarchy compared

SitePrimary attentionExplanatory informationProof and detailWhat interaction adds
AceCondensed service statements and limeGray studio introduction; persistent railProject grid, counters, testimonials, principlesSmall feedback and technical texture; limited new content on hover
Arkon3D object and role titleCompact biography; perimeter metadataProject descriptions and image galleriesScene continuity and button/link feedback
Neue MontréalGiant specimens and editorial statementsRuled columns, family labels and narrativeWeight controls, optical comparisons, languages and glyphsDemonstrates product properties and reveals editorial stories
MONOLOGWordmark, atmosphere, then large statementsSmall positioning statement; project/process copyOutcomes, testimonials, FAQsChanges local emphasis and supplies contextual previews
Lama LamaUppercase declaration and cinematic mediaSupporting paragraphs and micro labelsCompact work index, case detail, people and awardsReveals previews, portraits, personality captions and alternative presentation modes

Three levels should be kept distinct when borrowing ideas from these sites. Page hierarchy determines which chapters matter. Component hierarchy determines how a project, quote or service is understood. Interaction hierarchy changes what is emphasized or revealed as the visitor acts. MONOLOG's service list and Lama's team list are clear examples of the third level.

The strongest takeaway is that hierarchy is not simply a descending list of font sizes. Alignment can make equally sized text understandable; contrast can turn a list into a selection interface; a hover can introduce a temporary layer of detail. The successful examples preserve a stable reading structure beneath those changes.

Pointer and interaction findings

The individual website pages document the live pointer evidence: Ace's project images zoom to 1.05; Arkon's CTA grows and navigation arrows appear; Neue's postcards tilt and purchase letters roll; MONOLOG's service list changes emphasis with its preview, and its cursor-following instruction was confirmed; and Lama's team rows reveal portraits and individual personality captions.

An additional responsive discovery is Lama's awards: desktop uses a press-and-hold reveal in its implementation, while mobile supplies a persistent View our awards disclosure that was opened and verified. The Lama Lama page distinguishes that source-confirmed desktop behavior from the live mobile test.

Desktop → mobile comparison

SiteNavigationContent / compositionInteraction adaptationMost important mobile concern
AceFull nav/CTAs → logo + partial-height menuFixed rail removed; cards/stats stackMenu exposes extra routes; case metadata has disclosures in source640px intro clipped; Works misroutes
ArkonThree route links stay visibleTitle up, bio down, central sphere remains dominantGallery controls persist; prev/next become smallerUnstable contrast over sphere; zoom restriction
Neue MontréalCentral chapter pill disappears; purchase staysLong vertical specimen; circles stack; comparisons selectively stay pairedCity accordion becomes horizontal rows; tilt greatly reducedLong-scroll orientation and custom-control semantics
MONOLOGAdds Menu; Start a project remainsTall hero; About fills widthLarge menu links and full-width biographyPlaceholder menu cards and incomplete published case routes
Lama LamaCompact menu expands to nearly screen widthHero stacks; work rows grow; services become horizontal cardsDesktop inline case preview → tested direct case navigation; deck has mobile-specific source behaviorSmall labels; differing layer/exit conventions

Responsive quality here is best judged by what gets rethought, not only by whether columns fit. Neue's accordion and Lama's services are strong examples. Ace's introduction demonstrates the opposite: changing the outer layout without releasing an inner fixed width breaks the reading experience.

What I would send back to the teams

These priorities are editorial recommendations based on observed impact, not formal severity scores from a full QA program.

PrioritySiteFindingEvidence / next action
Fix firstAceMobile introduction is clippedMeasured 640px inner width at 390px; use responsive width and recheck wrapping
Fix firstAceMobile Works goes to Notes; Lab points to /404; /works emptyLive navigation/DOM + route source; align links and destinations
Fix firstArkonHero body crosses bright sphereLive mobile screenshot; create a stable text-safe area
Fix firstMONOLOGPublished case routes show generic shellsAll seven source responses, one live confirmation; complete, redirect or remove from sitemap as appropriate
Fix nextArkonZoom-restricting viewport settingsSource; allow scaling and test reflow
Fix nextNeue MontréalDesktop cover text/rules overlap at 1280pxRepeated captured state; diagnose sizing/animation/font-loading interactions
Fix nextNeue MontréalMobile long page loses chapter navigationLive responsive header; add compact chapter access
Fix nextMONOLOGMenu content placeholders and unclear filtered countLive menu/filter; finish content and distinguish total/results
Fix nextLama LamaDeck Escape exit and form-error clarityTested state; harmonize layer controls and show errors beside fields
Fix nextLama LamaCubby placeholder narrative; sparse AI pageSource; editorial completion or deliberate removal from published discovery
ValidateAllReduced motion, focus, touch, contrast and device performanceTargeted follow-up required; no benchmark or compliance claim in this report

Principles worth taking into a new design

  1. Choose a concept before choosing effects. Technical precision, a live coding stage, a travel guide, a founder's editorial voice and a pixel-based agency identity are distinct starting points.
  2. Give motion an explanatory job. A changing weight shows a font capability; a persistent scene links routes; an opening row exposes portfolio depth. These are easier to justify than an unrelated decorative effect.
  3. Keep a quiet place to read. Large media can surround the copy, but the copy still needs stable contrast and a sensible line length.
  4. Separate expression from control clarity. Brand the button's behavior, but preserve recognizable selection, focus, labels and exits.
  5. Design mobile interactions deliberately. Replace a desktop arrangement when its geometry no longer works. A vertical accordion or horizontal service strip can preserve the idea better than shrinking it.
  6. Make hidden interactions optional rewards. A visitor should be able to assess the work and contact the team without finding the experiment.
  7. Audit the edges of the experience. Sitemaps, old project URLs, menus, footer links and validation states are part of the delivered design. The most polished homepage does not compensate for an empty destination.

My strongest references by purpose are Neue Montréal for product education, Lama Lama for a coherent interaction language, MONOLOG for narrative and trust, Ace for restrained technical art direction, and Arkon for demonstrable creative-development skill. These are qualitative judgments about this research set, not claims about which site converts best.

Public-source evidence

The public-source inspection, reviewed September 15–16, 2026, explains the fonts, visual tokens, breakpoints, motion settings, and interaction implementations behind the browser observations. All findings come from public HTML, CSS, JavaScript, and sitemaps; no source repository access was available. A shipped definition alone is not proof that a feature is active, and a library import is not proof of a visible effect.

Exact website-specific findings sit under the public-source sections for Ace, Arkon Digital, Neue Montréal, MONOLOG, and Lama Lama. The public origins and inspected asset URLs are retained here:

Evidence and boundaries

Temporary source snapshots, route snapshots, and extraction manifests from the research session are not included in this repository. The public origin URLs and module references are cited above and on the website pages; versioned assets may change or become unavailable. Source bundles are minified, so quoted selectors/function names are more useful retrieval anchors than line numbers. Every inventoried route is itself a primary source, although live content may have changed since inspection.

Screenshots are direct captures from the live research session. No image-generation or remote-media downloads were used, and no font binary downloads were necessary. Some animations, particularly pointer effects and mobile touch handling, were explained from inspected implementation instead of claiming they were all exercised. A font declaration does not establish actual rendered usage.

No forms were submitted, bookings made, external AI prompts sent, purchases performed or camera access granted. No Lighthouse or other performance benchmark was run. This research does not certify color-contrast compliance, screen-reader usability, keyboard coverage, reduced-motion compliance, or that every interaction is usable in every browser or viewport. Real-device Safari/Chrome, sustained long-press, full keyboard traversal, slow-network loading and measured frame rate remain outside this review.

Route inventory

65 public URL requests completed on 2026-09-16: 8 Ace, 8 MONOLOG, and 49 Lama Lama routes, including every English Lama case URL in its sitemap (41 URLs, 40 unique destinations). Every request ended at HTTP 200; that does not mean every page is complete. One redirect and several empty/incomplete content templates were found. This inventory describes delivered markup and selectively inspected public component code, not live interaction tests.

Most consequential findings

  • Ace /works is an empty page component. The public page bundle creates only a black 1200×1080 div and overlay, with no children. This is stronger than a missing server-rendered text observation. Page, actual page module.
  • Ace /laboratorium is not an experiment gallery. It is a personal-profile layout: headline, avatar, biography, social links, employment timeline and email CTA. Its content/style differ materially from the main studio site. It may be residual/template content; the source alone cannot establish intent or verify the claimed career history. Page.
  • MONOLOG's seven case URLs deliver the same generic old-looking shell. Each has title “MONOLOG,” no case heading/body, a navigation/footer with 2025 copyright, different positioning/contact copy, and the same text. These are incomplete-looking responses despite HTTP 200, not confirmed 404s. Client hydration can alter source responses; the MONOLOG review records a live confirmation for one case, not all seven.
  • Lama /contact has a camera playground. It obtains a front-facing webcam stream on activation, textures it into the branded WebGL grid, offers grid-size and dark/light controls, and stops camera tracks when reverting. This was source inspected only. Contact.
  • Lama /ai is sparse. Main page content is an AI heading followed by the standard contact/footer, with no substantive AI service content in the delivered markup. Page.
  • Lama Cubby case contains lorem ipsum. Its case introduction is placeholder Latin. Case.
  • Lama has duplicate sitemap destinations. /cases/10-10/ redirects to /cases/10-out-of-10/; both appear in the source sitemap.

Route findings by website

The complete request tables are on the corresponding website pages.

Arkon's three main routes and Neue Montréal's one-page structure were inspected separately from these 65 requests. Their observations are on the Arkon Digital and Neue Montréal pages.

Coverage limits and reading guidance

This is a public response/template and selectively inspected interaction-module inventory, not a report that all listed media or controls were exercised in a browser. HTTP 200 only proves a response was returned, not that content is complete or interactions work. The individual website reviews supply runtime evidence on main routes.

Third-party client sites, external portfolios/demos and transactional destinations were not exhaustively explored. Form submission, booking, purchases, camera permission, and client project functionality are outside this inventory. English routes were inventoried; alternate Dutch content was not exhaustively duplicated.

HTML snapshots sometimes contain repeated text for responsive variants, animated hover layers or accessibility/display copies. Those source repetitions were not classified as visual duplication defects. Similarity of case templates is intentional system reuse; the substantive concerns are empty/sparse content, placeholder prose, or navigation to a generic shell. Where case copy describes a client tool or creative system, the description is not evidence that the tool can be operated on Lama's case page.

Use the source findings as an investigation map and explanatory evidence alongside the live observations. Where a feature was only identified in markup, retain that distinction when reading or reusing the research.