/* The palette, and the only part of this file another app should need to change.
   Taken from the app's own theme (ui/theme/ParallaxTheme.kt) so the site and the product are the
   same colours rather than two guesses at the same mood. */
:root {
  --void:   #100e16;  /* page ground */
  --ground: #191622;  /* panels */
  --raise:  #241f30;  /* rules and panel borders */
  --edge:   #332b42;  /* the one brighter border */
  --glow:   #c4568a;  /* accent: numerals, labels, links. Nothing else. */
  --text:   #ece6ef;
  --muted:  #9a93a5;
  --faint:  #6b6478;
  --fainter:#4b4557;

  --measure: 620px;   /* the reading column */
}

/* Shared by every localized landing page. Colours are the app's own
   (ui/theme/ParallaxTheme.kt): dark always, fuchsia spent sparingly. The
   privacy policy keeps its own inline styles — it is a legal document that
   must render even if this file is ever unreachable. */
*, *::before, *::after { box-sizing: border-box; margin: 0; padding: 0; }

body {
  /* The tinted band behind the hero is deliberately full-bleed and sized in `vw`, and `100vw`
     counts the scrollbar — so it overhangs by exactly the scrollbar's width and the page gains a
     horizontal scrollbar of its own. `clip` rather than `hidden`: hidden would silently turn this
     into a scroll container, which breaks `position: sticky` for anything added later. */
  overflow-x: clip;
  font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, "Helvetica Neue", sans-serif;
  background: var(--void);
  color: var(--muted);
  font-size: 17px;
  line-height: 1.7;
  padding: 3.5rem 1.25rem 4rem;
  -webkit-text-size-adjust: 100%;
}
.container {
  position: relative;
  z-index: 1; max-width: 640px; margin: 0 auto; }

/* Hero */
.hero .sub {
  display: block;
  margin-top: 0.5rem;
  font-size: 0.8rem;
  font-weight: 500;
  letter-spacing: 0.09em;
  text-transform: uppercase;
  color: var(--faint);
}
.tagline {
  margin: 1.4rem auto 0;
  max-width: 22ch;
  font-size: 1.3rem;
  line-height: 1.35;
  color: var(--text);
}
.lead {
  margin: 0.9rem auto 0;
  max-width: 42ch;
  font-size: 0.97rem;
}

/* Google's own badge, self-hosted rather than hotlinked: the CSP is img-src 'self' data:, so an
   image served from Google would simply not appear. One file per language — the words are inside
   the artwork, so they are not interchangeable. */
.store {
  display: inline-block;
  margin-top: 1.8rem;
  line-height: 0;
}
.store img {
  width: 162px;
  height: auto;
  max-width: 100%;
}
.store:hover { opacity: 0.85; }

/* Features */
.features { border-top: 1px solid var(--raise); }
.feature {
  display: flex;
  gap: 1.1rem;
  padding: 1.5rem 0;
  border-bottom: 1px solid var(--raise);
}
.feature .num {
  flex-shrink: 0;
  width: 1.7rem;
  font-size: 0.72rem;
  font-weight: 600;
  letter-spacing: 0.08em;
  color: var(--glow);
  padding-top: 0.5rem;
}
.feature h2 {
  font-size: 1.05rem;
  font-weight: 600;
  color: var(--text);
  margin-bottom: 0.15rem;
}
.feature p { font-size: 0.95rem; color: var(--muted); }

/* Panels: the three things worth saying in prose */
.panel {
  margin-top: 1.75rem;
  padding: 1.25rem 1.4rem;
  background: var(--ground);
  border: 1px solid var(--raise);
  border-radius: 14px;
}
.panel h2 {
  font-size: 0.75rem;
  font-weight: 600;
  text-transform: uppercase;
  letter-spacing: 0.09em;
  color: var(--glow);
  margin-bottom: 0.6rem;
}
.panel p { font-size: 0.95rem; }
.panel a { color: var(--glow); text-decoration: none; }
.panel a:hover { text-decoration: underline; }

/* Requirements and languages */
.meta {
  margin-top: 2.5rem;
  padding-left: 1.1rem;
  border-left: 2px solid var(--edge);
}
.meta .label {
  font-size: 0.72rem;
  font-weight: 600;
  text-transform: uppercase;
  letter-spacing: 0.09em;
  color: var(--faint);
}
.meta p { font-size: 0.92rem; }
.meta .langs { margin-top: 0.75rem; color: var(--muted); }
.meta strong { color: var(--text); font-weight: 600; }

.footer {
  margin-top: 3rem;
  padding-top: 1.5rem;
  border-top: 1px solid var(--raise);
  font-size: 0.85rem;
  color: var(--faint);
  display: flex;
  flex-wrap: wrap;
  gap: 0.5rem 1.25rem;
  justify-content: space-between;
}
.footer a { color: var(--glow); text-decoration: none; }
.footer a:hover { text-decoration: underline; }
.footer .disclaimer {
  flex-basis: 100%;
  margin-top: 0.75rem;
  font-size: 0.78rem;
  line-height: 1.5;
  color: var(--fainter);
}

/* Language bar: the escape hatch when Accept-Language is right about the
   browser and wrong about the reader. */
.langbar {
  flex-basis: 100%;
  display: flex;
  flex-wrap: wrap;
  gap: 0.85rem;
  margin-top: 0.6rem;
}
.langbar a {
  color: var(--faint);
  text-decoration: none;
  font-size: 0.78rem;
  letter-spacing: 0.06em;
}
.langbar a:hover { color: var(--glow); text-decoration: none; }
.langbar a.current {
  color: var(--text);
  font-weight: 600;
  cursor: default;
}

@media (max-width: 480px) {
  body { padding-top: 2.5rem; font-size: 16px; }
  .hero h1 { font-size: 2.1rem; }
  .tagline { font-size: 1.15rem; }
}


/* ---- Screenshots -------------------------------------------------------------------------
   Real captures, cropped only to drop the status bar — a clock, notification icons and a battery
   at 91% are somebody's Tuesday evening, not the product. Nothing inside the app is retouched.

   A scroll strip on a phone and a row on a desktop: four portrait screenshots side by side is the
   one layout that needs no decision about which three to cut. */
/* A grid, not a horizontal strip.
   The strip was two screenshots wide on a phone with the rest off the right edge, and a sideways
   scroll inside a page that scrolls down fights the thumb and hides whatever it is holding — the
   reader has no way to know there were four. Two by two shows all of them, needs no gesture, and
   is shorter than stacking them. */
.shots {
  /* On the parent, so the four phones share one camera. Per-element `perspective()` gives each
     its own vanishing point, and four phones each seen from their own angle read as stickers. */
  perspective: 1200px;
  display: grid;
  grid-template-columns: 1fr 1fr;
  gap: 1.75rem 1rem;
  padding: 0;
  margin-bottom: 3rem;
}
.shot { min-width: 0; }

/* The device frame, drawn rather than photographed.
   A screenshot with a rounded corner reads as an image; a bezel reads as a phone, and that is most
   of the difference between this looking finished and looking like a placeholder. Two nested
   radii — the outer shell and the screen inside it — plus a hairline that catches light on one
   edge, which is what stops the black bezel merging into a black page. */
/* The device.
   Three corrections over the first attempt, in the order the eye catches them.

   **The silhouette was symmetric**, which a rotated slab cannot be. A phone turned 17° shows a
   band of its own side down one edge; a 1px rim equal on both edges is the tell, and it is read
   before any shading is. The flank is three zero-blur offset shadows — chamfer, body, terminator.
   Offset shadows copy the element's rounded outline, so the corners come out right for free; that
   is exactly what real 3D side faces cannot do without per-corner geometry. Flat bands stop
   convincing somewhere past 25°, which is well beyond where this sits.

   **The cast shadow is no longer here.** A box-shadow is painted in the element's own space and
   then transformed, so it was rotating and skewing with the phone instead of lying on the page.
   It now lives on the unrotated wrapper.

   **The glass sits in a recess.** A seam and a lip, which is most of the difference between a
   bezel holding a screen and a border around an image.

   Radii are concentric: inner = outer − bezel, as custom properties so the img, the overlay and
   the body cannot drift apart again. They had, by 1px and 2px. */
.frame {
  --r: 34px;
  --bezel: 9px;
  /* How much side face shows. Zero by default: only the hero is turned far enough to have any. */
  --edge-x: 0px;
  --edge-y: 0px;
  position: relative;
  padding: var(--bezel);
  border-radius: var(--r);
  background: linear-gradient(145deg, #4a4159 0%, #2a2436 28%, #191622 62%, #0d0b12 100%);
  box-shadow:
    inset 1px 1px 0 rgba(255, 255, 255, 0.16),
    inset -1px -1px 0 rgba(0, 0, 0, 0.6),
    2px 1px 0 0 #4c4258,
    calc(var(--edge-x) * 0.5) calc(var(--edge-y) * 0.6) 0 0 #241f2e,
    var(--edge-x) var(--edge-y) 0 0 #0e0c13;
}

/* The glass. Recessed and seamed; the specular sweep rides on top. */
.frame::after {
  content: "";
  position: absolute;
  inset: var(--bezel);
  border-radius: calc(var(--r) - var(--bezel));
  pointer-events: none;
  background: linear-gradient(118deg, rgba(255, 255, 255, 0.11) 0%, rgba(255, 255, 255, 0.03) 22%, transparent 46%);
  box-shadow:
    inset 0 0 0 1px rgba(0, 0, 0, 0.7),
    inset 1px 2px 4px rgba(0, 0, 0, 0.45);
}

.shot:nth-child(n+3) .frame {
  transform: rotateY(14deg) rotateX(3deg);
  transform-origin: 35% 50%;
}

.frame img {
  width: 100%;
  height: auto;
  display: block;
  background: var(--void);
  border-radius: calc(var(--r) - var(--bezel));
}

.shot figcaption {
  margin-top: 1.1rem;
  font-size: 0.74rem;
  letter-spacing: 0.06em;
  text-transform: uppercase;
  color: var(--faint);
  text-align: center;
}

/* ---- Wider than the reading column ------------------------------------------------------
   The page is a column of prose and stays one; only the two things that are *lists* get to use
   the width, because a paragraph set 1100px wide is unreadable and the reason the measure exists. */
@media (min-width: 900px) {
  .container { max-width: 980px; }
  .hero, .panels, .meta, .site-footer { max-width: var(--measure); margin-left: auto; margin-right: auto; }
  .features {
    display: grid;
    grid-template-columns: 1fr 1fr;
    column-gap: 2.5rem;
  }
  /* The rule under the last row would otherwise sit under one column only. */
  .features .feature:nth-last-child(-n+2) { border-bottom: none; }
  /* Four across once there is room for them; the grid needs no other change. */
  .shots { grid-template-columns: repeat(4, 1fr); gap: 1.25rem; }
}



/* ---- The close ---------------------------------------------------------------------------
   The page used to end on a trademark disclaimer, which is the least inviting sentence on it. A
   reader who has got this far has read everything and is at the one moment they might act; asking
   then is not pushy, it is the only place asking makes sense. */
.close {
  text-align: center;
  padding: 3.5rem 0 3rem;
  border-top: 1px solid var(--raise);
  margin-top: 3rem;
}
.close h2 {
  font-size: 1.35rem;
  line-height: 1.3;
  margin: 0 0 0.5rem;
  color: var(--text);
}
.close p {
  margin: 0 auto 1.6rem;
  max-width: 32ch;
  color: var(--muted);
}
.close .store { margin-top: 0; }

/* ---- Depth ------------------------------------------------------------------------------
   A dark page with no light source has nothing for content to scroll against, which is most of
   why a flat page feels flat. A single faint pool of the accent colour, fixed to the viewport, so
   the page moves over a light that does not move. Not an animation — nothing here needs a
   reduced-motion guard, which is exactly why it is the cheap half of this. */
body::before {
  content: "";
  position: fixed;
  inset: -20% 0 auto;
  height: 70vh;
  /* Zero, not -1. A pseudo-element behind its own parent's background is a pseudo-element
     nobody sees, and `body` paints --void — so this sits just above it and the content sits
     above this. */
  z-index: 0;
  pointer-events: none;
  background: radial-gradient(60% 55% at 50% 0%, rgba(196, 86, 138, 0.13), transparent 70%);
}

/* ---- The one scroll-linked moment --------------------------------------------------------
   The phones stand up as they cross the viewport and lean back as they leave.

   Scroll-*linked*, not scroll-triggered, and the difference is the whole point: progress is the
   element's position, so it reverses the instant you scroll back and never runs on a clock of its
   own. The pattern it replaces — invisible until a threshold fires, then a canned fade — is the
   one users read as the page still loading.

   Everything is behind @supports, so a browser without view timelines keeps the static tilt above
   and loses nothing. `animation` is declared before `animation-timeline` deliberately: the other
   order silently does nothing, which is the documented trap in WebKit's own guide.

   Only the bezels move. Not a paragraph on this page animates — text that arrives late is text
   somebody waited for. */
@supports (animation-timeline: view()) {
  @media (prefers-reduced-motion: no-preference) {
    .shot .frame {
      animation: stand-up linear both;
      animation-timeline: view();
      animation-range: entry 10% cover 40%;
    }
    .shot:nth-child(n+3) .frame { animation-name: stand-up-mirrored; }
  }
}
@keyframes stand-up {
  from { transform: rotateY(-14deg) rotateX(3deg); }
  to   { transform: rotateY(0deg) rotateX(0deg); }
}
@keyframes stand-up-mirrored {
  from { transform: rotateY(14deg) rotateX(3deg); }
  to   { transform: rotateY(0deg) rotateX(0deg); }
}


/* ---- The split hero ----------------------------------------------------------------------
   Copy on one side, one large phone on the other, and the phone crossing the boundary into the
   section below it. Three things happen at once: the app is finally shown at a size where it can
   be read, the page stops being a single centred column, and the overlap gives the scroll an edge
   to cross — which is what a uniformly dark page never had.

   One phone, not three fanned out. A fan needs screenshots that do not exist yet, and it is the
   detail that makes these layouts look bought rather than made. */
.hero {
  position: relative;
  padding: 1rem 0 0;
  margin-bottom: 5rem;
}
.hero-copy { text-align: left; }
.hero-copy > svg { margin-bottom: 1.4rem; }
.hero h1 {
  font-size: clamp(2.6rem, 9vw, 4rem);
  line-height: 1.02;
  letter-spacing: -0.03em;
  margin: 0 0 0.4rem;
  color: var(--text);
}
/* The second register, borrowed from the display-type pairing these layouts all use: one word
   set plainly, the rest lighter and looser. Costs nothing and stops the title reading as a
   default h1. */
.hero h1 .sub {
  display: block;
  font-size: 0.3em;
  font-weight: 400;
  letter-spacing: 0.14em;
  text-transform: uppercase;
  color: var(--faint);
  margin-top: 0.9rem;
}
.hero .tagline {
  font-size: 1.32rem;
  line-height: 1.35;
  color: var(--text);
  margin: 0 0 0.9rem;
  max-width: 20ch;
}
.hero .lead { margin: 0 0 1.8rem; max-width: 44ch; }

.hero-shot { position: relative; margin-top: 3rem; }
/* Perspective stays on the element here, unlike the row of four below.
   Shared vanishing points matter when several objects sit side by side; a lone phone has nobody
   to disagree with. And on the parent it was actively wrong: the phone is pushed to the right of
   its grid cell, so the cell's centre put the camera off to one side and the foreshortening blew
   up. */
.hero-shot .frame {
  /* Right flank on show, so that is the shadow side under a top-left light. 11px is an 8.5mm
     phone's thickness at this width times sin 17° — arrived at rather than eyeballed. */
  --edge-x: 11px;
  --edge-y: 3px;
  transform: perspective(1100px) rotateY(-17deg) rotateX(4deg) rotateZ(-1.5deg);
  transform-origin: 72% 50%;
}

/* The cast shadow, on the wrapper because the wrapper is not rotated: a shadow belongs to the
   floor, not to the object. It was a box-shadow on the phone, so it rotated and skewed with it,
   and it fell straight down while every highlight said the light was top-left. */
.hero-shot::before {
  content: "";
  position: absolute;
  left: 14%;
  right: 0;
  bottom: -1.5rem;
  height: 11%;
  /* The rightward bias lives in the gradient's own centre rather than in a translate. A translate
     pushed the box past its container and put a horizontal scrollbar on the page at every width
     below the desktop layout — 20px of it at 500px wide, which is exactly this 4%. */
  background: radial-gradient(50% 50% at 60% 50%, rgba(0, 0, 0, 0.6), transparent 70%);
  filter: blur(12px);
}
.hero-shot .frame { max-width: 300px; margin: 0 auto; }

/* The callout. Not decoration: it points at the sentence in the screenshot where the app admits
   the television refused something, which is the one claim on this page a competitor cannot copy
   by writing better copy. */

/* The tinted band the phone crosses. A pseudo-element so no wrapper is needed in eight files. */
.hero::after {
  content: "";
  position: absolute;
  left: 50%;
  transform: translateX(-50%);
  width: 100vw;
  bottom: -2.5rem;
  height: 45%;
  /* No hairline borders. The band is only a shade off the page ground, so a 1px rule on its edge
     was the only part anyone could see — it read as a stray line drawn across the page rather
     than as the top of a section. The tone change alone carries it, softened at the seam so the
     eye reads a change of ground instead of an edge. */
  background: linear-gradient(var(--ground), var(--ground));
  -webkit-mask-image: linear-gradient(to bottom, transparent, #000 3rem, #000 calc(100% - 3rem), transparent);
  mask-image: linear-gradient(to bottom, transparent, #000 3rem, #000 calc(100% - 3rem), transparent);
  z-index: -1;
}

@media (min-width: 900px) {
  .hero {
    display: grid;
    grid-template-columns: 1.05fr 0.95fr;
    align-items: center;
    column-gap: 3rem;
    max-width: 980px;
    padding-top: 2rem;
  }
  /* Bottom-anchored, not centred. The band below is positioned from the hero's bottom edge, so
     centring the phone in the row made its overlap with the band depend on how tall the copy
     happened to be — and the copy is seven translations long. Spanish runs two lines further
     than English and lifted the phone clear of the seam. */
  .hero-shot { margin-top: 0; align-self: end; }
  /* Bleeds below the band rather than sitting inside it. */
  .hero-shot .frame { max-width: 330px; margin: 0 0 -4rem auto; }
  .hero::after { height: 58%; bottom: -5rem; }
  .shots {
    grid-template-columns: repeat(3, minmax(0, 210px));
    justify-content: center;
    gap: 2rem;
  }
}
