→ open the app
Creative brief · ParaPolar 3.0

From dashboard
to flight.

Today ParaPolar is a correct chart with sliders. The next version is a small sky you fly with your thumb — where the polar curve is the instrument panel, not the product.

FIELD OF PLAY: PARAPOLAR.COM · EN / DE / FR / NL · 14 JUL 2026

ALT 3000 m the thesis

Nobody falls in love with a graph. They fall in love with what it lets them feel.

Every paragliding student meets the polar curve the same way: a static figure in a theory book, memorized for the exam, forgotten at the landing field. Yet the ideas behind it — speed to fly, wind gradient, MacCready — are the difference between gliding home and landing in a tree.

ParaPolar's edge is that it can close the gap between the figure and the feeling. The redesign has one organizing rule: the consequence view is the hero; the chart is the instrument. You watch a wing fly over terrain, you push the bar, you feel the trade — and the polar graph explains what you just felt, not the other way around.

"A flight simulator for understanding, not for controls."

ALT 2500 m who we fly for

Four riders on one thermal

Each audience arrives with a different question. The product should answer it within a minute — then invite the next one.

The student

passing theory · not dying

Cramming for the A‑license exam (DHV, FFVL, KNVvL…). Knows the words, hasn't felt them.

Exam-aligned lesson mode: each polar concept as a 90-second interactive scene with a check question.

The instructor

the multiplier

Teaches 50–300 students a year. Projects slides in a clubhouse. Would kill for a live demo.

Classroom mode (big type, presenter-friendly) + embeddable widgets for school sites. One instructor = hundreds of users.

The XC pilot

gliding farther

EN‑B/C, flirting with MacCready theory. Asks concrete questions: "bar or no bar into this valley wind?"

Scenario challenges with real numbers, glider comparison overlays, shareable "beat my glide" links.

The curious

wonder

Tandem passengers, sim pilots, physics teachers, people who watched one YouTube video too many.

Zero-jargon simple mode that is genuinely fun to poke — the toy is the funnel.
ALT 2000 m reach — the loop, not the megaphone

Growth is a ridge lift: set up the cycle and stay in it

The current site is a JavaScript app with almost no indexable text — to a search engine, parapolar.com is nearly a blank page with a good title. Fixing that is the single highest-leverage SEO move, and it doubles as real user value:

Learn pages

Pre-rendered articles in all four languages — "What is a polar curve?", "Speed to fly, explained", "MacCready without tears" — each with the live widget embedded mid-article. Static HTML for crawlers, playground for humans.

Embeds for schools

A one-line iframe embed of any scenario. Flight schools and blogs get a free teaching widget; ParaPolar gets the backlinks that actually move rankings in a niche this small.

Share cards

Permalinks already encode full state. Render them as OG images (worker-generated) so a shared "look, negative groundspeed!" link unfurls as a picture in WhatsApp/Telegram — where pilot communities actually live.

Challenges

"Cross this valley losing the least height." Score, retry, send to your club group. Each challenge link is a lesson wearing a game's clothes — and another inbound link.

Distribution to seed the loop: instructor outreach (schools in DE/FR/NL/AT/CH first — the domains already speak their languages), r/freeflight and paraglidingforum threads that show rather than tell, and one collaboration with a paragliding YouTube channel walking through backwind flight on the tool.

And one subtraction: replace Google Analytics with a cookieless option (Cloudflare Web Analytics or Plausible). The cookie banner is the first thing every new visitor sees today — the worst possible first impression for a toy. Delete the banner, gain three seconds of magic.

ALT 1500 m the UX spine

One scene, one loop, layers of depth

Scene first
The ground view fills the screen; the polar graph docks as a translucent inspector (desktop) or a pull-up sheet (mobile). Both are views of the same moment — hover the polar, the wing responds; watch the wing, the dot rides the curve.
Direct manipulation
Kill the slider farm. Drag the wing itself forward/back to change speed. Drag the windsock to set wind. Drag the thermal to set lift. The controls live in the world they affect — sliders remain as a precision fallback in the inspector.
Ten-second aha
On first load: wing flying at trim, a gentle prompt — "a headwind is coming" — wind rises, groundspeed melts, the ghost of the best-glide tangent appears. One scripted beat, then it hands you the controls. No modal, no tour, no banner.
Progressive depth
Simple mode = speed + wind, nothing else. Every advanced concept unlocks in context: the first time your groundspeed goes negative, a card offers the "Backwind" lesson. Curiosity pulls the curriculum, not a settings toggle.
Felt consequences
Stall isn't a number turning red: the wing pitches back, shudders, drops — the screen dips with it (respecting reduced-motion). Speed-to-fly isn't a row in a table: it's a notch on the speed control you can feel the knob snap to.
Numbers with dignity
Readouts styled as flight instruments — tabular numerals, unit-aware (m/s, ft/min, kt), glanceable. Data is never decoration; every visible number is one a pilot would actually check.
ALT 1000 m design language — "alpine dusk instrument"

Less dashboard, more cockpit at golden hour

The current UI is competent Tailwind vernacular: white cards, slate borders, rounded pills. Nothing wrong — nothing memorable. The replacement borrows from the two most beautiful things pilots already stare at: the evening sky and their instruments.

Night flight #0E1A2B · ground (dark), HUD glass
Glacier light #EDF1F4 · ground (light), cold not cream
Thermal #E8833A · the accent: lift, action, STF
Skywash #4FA3C7 · air mass, sink, secondary data
Horizon rose #C96F5E · dusk gradients only, never UI chrome
Display · geometric sansFly the curve, not the numbers
Body · charter serifLessons and learn-pages read like a good flight manual, not like app chrome.
Data · mono, tabularGR 8.4:1 · GS 27.5 km/h · VARIO +1.20 m/s

Sky gradients are state, not wallpaper: calm evening for the default scene, cumulus blue for thermal scenarios, moody grey-green for the strong-wind lessons. Terrain is a quiet dark silhouette so the physics reads against it. Motion budget is spent in exactly one place — the scene; the chrome around it barely moves.

Ridge dayThermalBackwind
Polar · EN-B
Glide
8.4:1
Ground
27.5 km/h
Vario
+1.20 m/s
BrakesSpeed
Desktop concept — scene as hero, polar as docked inspector, speed-to-fly as a physical notch (STF) on the control rail.

Mobile is not the desktop squeezed. The scene fills the phone; instruments condense to a strip; the primary control becomes a thumb arc anchored to the bottom corner — the one screen region a hand actually owns. The polar lives one swipe up, in a bottom sheet that half-docks so scene and chart can be watched together.

Tablet inherits the desktop layout plus a classroom toggle: 1.4× type, high-contrast lines, hidden chrome — built for a projector in a clubhouse and an instructor's pointing finger.

GR
8.4
GS
27
Vario
+1.2
thumb arc · speed
Mobile concept — thumb arc control.
ALT 500 m interaction by device

Meet the hand where it already is

DevicePrimary inputLayoutSpecial care
Phone Thumb arc for speed · drag windsock · tap-hold for tooltips Scene full-bleed, instrument strip top, polar in half-docking bottom sheet 44px+ targets, haptic tick at stall & STF notch, portrait-first (no "rotate your device" nagging)
Tablet Same touch model, two-handed: left thumb speed, right hand scrubs polar Desktop layout at touch density Classroom mode: projector contrast, big type, laser-focus cursor for the instructor
Desktop Drag wing or scrub polar · arrow keys = brakes/bar · scroll on scene = wind Scene hero + docked inspector + collapsible lesson rail Hover states everywhere (tangents explain themselves on hover), shareable state in URL at all times
GROUND · LZ the landing — what to build, in order

Roadmap: three glides

Now — the feel

weeks, not months
  • Kill the cookie banner (cookieless analytics)
  • Scene-first layout: ground view hero, polar as inspector, linked highlighting between them
  • Direct manipulation v1: drag wing = speed, drag windsock = wind, STF notch on the control
  • Design language pass: dusk palette, instrument pods, type system

Next — the pull

the growth loop
  • Learn pages ×4 languages, pre-rendered, widget embedded (this is the SEO play)
  • OG share cards from permalinks (worker-rendered)
  • Embed mode + outreach kit for flight schools
  • Ten-second scripted opening beat

Later — the game

retention & love
  • Lesson mode: 8–10 scenes from "what is a polar" to MacCready, exam-aligned per country
  • Challenges with scores and share links ("cross the valley", "escape the venturi")
  • Glider comparison overlay · classroom mode
  • Sound design: wind volume = airspeed (vario already sings)

How we'll know it works: median session > 3 minutes; ≥ 30% of sessions touch a lesson or challenge; shared-link opens per week; embeds live on ≥ 10 school sites; "polar curve paragliding" top-3 in DE/FR/NL. All measurable without a single cookie.

"Students should leave the exam and keep the tab open."