GitaVedanta Design Principles

Single source of truth for design direction across marketing website and Flutter app surfaces.

1. Purpose of the Design System

The GitaVedanta design system exists to create a cohesive brand experience that honors both ancient wisdom and modern technology. It bridges two distinct but complementary surfaces:

Marketing Website

Role: Discovery layer, trust builder, conversion pathway
Goal: Introduce visitors to the GitaVedanta vision, establish credibility, and guide users to download the app
Focus: Emotional resonance, visual premium feel, clear value proposition

Flutter App

Role: Actual product experience for ongoing usage
Goal: Deliver a calm, focused reading and conversation environment
Focus: Reading comfort, session continuity, navigational clarity

Both surfaces must feel like one brand. The website is the storefront; the app is the home. The design language should flow naturally from marketing context to product context—different expressions of the same philosophy, not different brands wearing similar colors.

2. Brand Attributes

The design should consistently express these core adjectives:

Calm — The interface never rushes the user. Every interaction has room to breathe.
Sacred but Modern — Honor the spiritual tradition without making it feel archaic or museum-like.
Premium — Quality without ostentation. Restrained elegance.
Minimal — Everything present serves a purpose. Remove the unnecessary.
Trustworthy — What users read here matters. The UI supports that importance.
Reflective — Design encourages contemplation, not distraction.
Intelligent — The AI and technology feel capable, not flashy. Silent competence.
Warm — Despite the spiritual context, the experience is inviting, not cold or clinical.
Uncluttered — Negative space is active. It guides attention, not just holds it.
Reverent without Ornamental — Sacred text is honored through placement and typography, not through decorative religious motifs.

3. Design Philosophy

Core Philosophy: Modern Sanctuary for Ancient Wisdom

The GitaVedanta design philosophy is grounded in a single idea: technology should feel invisible and supportive, not dominant. We are not building a tech product that happens to display scripture—we are building a digital sanctuary where scripture can be encountered undisturbed.

Key philosophical pillars:

Simplicity over decoration — Every element must justify its presence. If it doesn't serve the user's understanding, reflection, or next step, remove it.
Clarity over noise — Information hierarchy is everything. Users should never wonder what matters most on any screen.
Quiet confidence over flashy visuals — We do not need animation loops, gradients, or gamified elements to prove value. The scripture itself is the product. Let it speak.
Spiritual depth without visual heaviness — The tone is reverent, but the interface is light. Users should feel calm, not overwhelmed.
Technology as invisible support — AI features should feel like a knowledgeable companion, not an overlay. The interface recedes; the conversation emerges.

Liquid Glass: Cupertino-Inspired Design Language

The GitaVedanta design system draws inspiration from Apple's Liquid Glass design language introduced in iOS 26, iPadOS 26, and macOS 26. This aesthetic represents a evolution toward interfaces that feel fluid, translucent, and materially alive—aligning beautifully with our philosophy of creating a digital sanctuary where content can breathe and users can focus.

What is Liquid Glass?

Liquid Glass is a dynamic material that combines the optical properties of glass with a sense of fluidity. It creates a distinct functional layer for controls and navigation elements that adapts in response to various factors including:

Contextual translucency — Elements sample colors from background content beneath them, creating visual harmony without sacrificing legibility.
Fluid morphing — UI elements respond subtly as content changes, with smooth transitions that feel organic rather than mechanical.
Soft edges and layering — Navigation bars, tabs, and toolbars float in a translucent glass layer, letting content peek through elegantly.
Depth without skeuomorphism — Creates spatial relationships using purely digital tools, not physical metaphors.

Liquid Glass Principles Applied to GitaVedanta

Principle	Implementation
Fluid material	Use translucent surfaces for navigation bars and floating controls that let scripture content breathe beneath
Context-aware blur	Apply backdrop blur effects that adapt to the content behind them—warmer in reading mode, subtler in navigation
Soft navigation layer	Tab bars and toolbars float in glass material, receding with scroll to prioritize content
Immersive transitions	Smooth morphing animations between states—hero images collapsing into compact nav bars, verse cards expanding fluidly
Restrained glass	Apply glass effects judiciously—too many translucent elements reduces impact; let content remain the focus
Pop-out interfaces	Consider floating panels and bottom toolbars that emerge organically, not abruptly
Responsive to focus	Glass elements can subtly intensify when focused, providing visual feedback without harsh borders

Implementation Notes

Use CSS backdrop-filter: blur() with variable blur amounts (10-20px typically) for glass effects.
Add subtle warmth to glass surfaces to maintain the contemplative identity—avoid cold blue-tinted translucency.
Ensure text legibility remains high on glass layers—use sufficient contrast and optional dark/light scrims.
Animate glass transitions at 300-400ms with ease-out curves for organic feel.
On mobile, glass bottom toolbars work especially well for thumb-friendly navigation.

Alignment with Existing Philosophy

Liquid Glass complements rather than contradicts our existing design principles:

It enhances the "technology as invisible support" pillar—the glass layer serves without announcing itself.
It supports "whitespace is active"—glass surfaces define space without blocking it.
It reinforces "scripture remains the visual center"—glass navigation recedes to let content shine.
It aligns with "interactions should feel gentle"—fluid morphing animations are calm and measured, not bouncy.

4. Experience Principles

These principles guide every design decision:

Readability comes first — Every screen is legible. No cramped text, no low-contrast elements, no busy backgrounds competing with content.
Whitespace is a feature, not wasted space — Generous margins and padding are not luxury—they are necessity. They create focus.
Content should feel guided, not crowded — Use spatial hierarchy to lead the eye. Don't force the user to parse dense information.
Interactions should feel gentle and intentional — Buttons respond smoothly. Transitions are present but subtle. Nothing jumps, bounces, or startles.
AI should feel grounded and safe — Vedavaani is not a chatbot; it's a digital acharya (teacher). The UI should reflect this—calm, measured, respectful.
Scripture should remain the visual and emotional center — Whether it's a verse card or a reading view, the scripture content is always the hero.
Use motion sparingly and meaningfully — Animation exists to clarify relationships between states, not to delight for its own sake.
Every screen should reduce friction and increase trust — Remove obstacles. Make the next action obvious. Never make users feel uncertain.

5. Visual Language

Overall Feel

Soft, warm, earthy, spiritual-modern palette
Calm surfaces with premium contrast
Rounded corners that feel soft but not playful (no sharp edges, no bouncy shapes)
Subtle borders and restrained shadows — no heavy drop shadows
Elegant typography hierarchy with serif headings and sans-serif body
Spacious layouts with generous breathing room
Iconography: Simple, refined, non-gimmicky. Line-based or filled solid. No complex illustrations unless specifically commissioned for the marketing site.
Cards: Quiet containers, not loud UI blocks. They hold content, not demand attention.

Visual Hierarchy Model

┌─────────────────────────────────────────┐
│  Scripture Content     (Primary focus)  │
│  ───────────────────────────────────────│
│  Commentary           (Secondary focus) │
│  ───────────────────────────────────────│
│  AI / UI elements    (Tertiary/UI)       │
└─────────────────────────────────────────┘

6. Color Principles

Background Philosophy

The base background is warm, earthy, and calm—reminiscent of natural paper or light-filtered rooms in traditional Indian architecture. This is intentional: scripture deserves a backdrop that feels contemplative, not digital.

Primary Light Theme Palette

Role	Hex Value	Reasoning
Background	`#f4f2ed`	Warm off-white. More forgiving than pure white, evokes natural paper.
Elevated Surface	`#fdfbf7`	Slightly brighter for modals, dropdowns, floating elements.
Card Surface	`#faf8f4`	Subtle warmth for content cards. Not stark white.
Primary Text	`#1a1a1a`	Near-black for comfortable long-form reading. Avoid pure black (#000).
Secondary Text	`#4a4a4a`	Clear reading text that doesn't compete with headings.
Muted Text	`#7a7a7a`	For timestamps, helper text, less critical information.
Border	`rgba(26, 26, 26, 0.08)`	Soft, visible only when needed. Never harsh.
Accent / CTA	`#f47c24`	Warm orange — the signature GitaVedanta accent. Used sparingly.
Accent Foreground	`#ffffff`	Text on accent buttons. Maximum contrast.
Success	`#3d7a5a`	Muted forest green. Calm, not alarmist.
Warning	`#c48b2e`	Warm amber. Noticeable but not urgent.
Error	`#b8464a`	Muted brick red. Serious but not aggressive.

Dark Theme (If Supported)

If a dark theme is implemented, it must preserve the same emotional identity—sacred, premium, calm. It should NOT be a generic dark mode with inverted colors.

Role	Hex Value	Reasoning
Background	`#0e0d0b`	Warm near-black. Avoid pure black (#000000).
Elevated Surface	`#161512`	Slightly lighter for hierarchy.
Card Surface	`#1a1916`	Subtle warmth, not cold gray.
Primary Text	`#f0ede8`	Warm off-white for readability.
Secondary Text	`#b8b5ad`	Muted warm gray.
Muted Text	`#7a776f`	Subtle information.
Border	`rgba(240, 237, 232, 0.08)`	Soft, visible only when needed.
Accent / CTA	`#f47c24`	Same accent — consistency matters.
Accent Foreground	`#1a1916`	Dark text on accent for contrast.

Key invariants across themes:

The accent color (#f47c24) never changes.
The emotional tone (warmth, calm) remains consistent.
Scripture reading areas maintain comfortable contrast in both themes.
Borders remain subtle in both modes.

Accent Color Behavior

Primary buttons: Filled accent background.
Secondary buttons: Outline with accent border.
Links: Accent color text with underline on hover.
Selection states: Accent background with contrasting text.
Never use accent for backgrounds of large sections — it competes with content. Use it for actions.

7. Theming Guidance

Light theme is the primary expression of the brand. Most marketing materials, screenshots, and first impressions should use the light theme palette.
Dark theme is optional but supported — If users prefer low-light reading, the app should accommodate without betraying the brand's warmth.
Dark theme rules:
- Never use pure black backgrounds. Warm, earthy darks maintain the contemplative identity.
- Ensure text contrast remains comfortable for long reading sessions.
- Keep the same accent color—consistency reinforces brand recognition.
- Scripture should remain legible and honored.
Cross-theme consistency:
- Border style and thickness should match.
- Spacing system remains identical.
- Typography scale does not change.
- Component states (hover, active, disabled) follow the same patterns.

8. Typography Principles

Typeface Selection

Headings: Cormorant Garamond or Playfair Display (serif) — evokes classical text, feels timeless.
Body: Inter or system-ui (sans-serif) — clean, readable, modern.
Scripture text: Consider a third serif variant for verse display if readability demands it.

Heading Hierarchy

Element	Style	Feel
H1 / Hero	Serif, 48–72px, font-medium	Grand but grounded. The most important statement on the page.
H2	Serif, 32–48px, font-medium	Clear section breaks. Significant but not shouting.
H3	Serif, 24–32px	Sub-sections. More detail, same tone.
H4	Serif or sans, 18–20px	Less prominent, but still a heading.

Body Text

Base size: 16px minimum (18px preferred for reading surfaces)
Line height: 1.6–1.75 for long-form content. Relaxed, not cramped.
Line length: 60–75 characters per line ideal. Never exceed 80 characters.
Paragraph spacing: 1.5–2x the line height. Give paragraphs room to breathe.

Scripture vs. Commentary vs. AI

Content Type	Visual Treatment
Scripture (verses)	Serif font, highest contrast, centered or left-aligned, generous margins, possibly larger size. The visual throne.
Commentary	Sans-serif, slightly smaller or same size as body, clearly distinguished from verse text via spacing and weight.
AI (Vedavaani) responses	Sans-serif, clearly distinguished from scripture, perhaps slightly muted color to indicate origin. Not competing with scripture.

Readability Rules

Never use text smaller than 14px for critical content.
Avoid all-caps for body text — harder to read.
Use font weight to create hierarchy, not color. Primary text is dark; secondary is muted, not bold.
Ensure line length is constrained on wide screens — use max-width containers.
Paragraphs should not feel like walls of text — break them visually with spacing.

9. Component Philosophy

Each component should embody the brand attributes. Below is how common components should feel and be used.

Buttons

Variant	Feeling	Usage
Primary	Warm, confident, inviting	Main CTAs (Download, Start Reading, Ask Vedavaani)
Secondary	Calm, composed	Secondary actions (Learn More, See All)
Outline	Light, unobtrusive	Tertiary actions, links
Ghost	Invisible until needed	Inline actions, close buttons

Always use rounded corners (pill or fully rounded) — never sharp.
Minimum touch target: 44px height (Flutter: Material guidelines).
Hover states: Subtle shift in background or shadow. No jarring color jumps.
Primary buttons: Use the accent color with a subtle glow on hover.

Cards

Feel: Quiet containers, not loud blocks. They hold content, they don't announce themselves.
Padding: Generous. 24–32px minimum.
Borders: Subtle or none. Use shadow sparingly.
Rounded corners: 16–24px radius. Soft but not circular.
Interaction: Hover can lift slightly or add subtle border, but avoid dramatic transforms.

Bottom Sheets

Feel: A drawer, not a popup. Grounded, not floating dramatically.
Background: Same as card or elevated surface.
Handle: Subtle drag indicator, not a large bar.
Animation: Smooth slide-up, ease-out. No bounce.

Input Bars

Feel: Calm entry point, not a form field.
Style: Minimal border, subtle background. Focus state should add accent border or glow.
Placeholder: Muted text color, never empty-looking.
Submit button: Adjacent or inside. Clear call to action.

Tabs

Feel: Navigation that feels like stepping stones, not a segmented control.
Active state: Accent underline or subtle background. Not dramatic.
Inactive: Muted text, not gray-out.
Interaction: Smooth underline slide or fade transition.

Chips

Feel: Small, helpful filters. Not primary UI.
Spacing: Tight but not cramped.
Rounded: Fully rounded (pill) or small radius.
Use for: Filters, tags, small categories.

Verse Containers

Feel: The shrine within the UI. Highest reverence.
Treatment: Serif font, centered or distinguished alignment, generous whitespace around the verse.
Background: May have subtle differentiation (very light accent tint) or remain on the same surface.
Typography: Larger than body text, clear verse/chapter marking.
Never clutter — This is the core product.

Commentary Blocks

Feel: Supporting voice, not competing.
Treatment: Sans-serif, slightly smaller or same size, clear visual separation from verse.
Spacing: Clearly separated from verse text—either below, in a different column, or in a distinct panel.
Color: Secondary or muted, not primary.

AI Chat Bubbles / Response Containers

Feel: A conversation with a respected teacher. Not a support chat.
Distinction: Clearly separated from user messages and scripture.
Style: Calm, measured. No flashy animations.
Interaction: Show thinking states gracefully—don't use loading spinners if possible. A subtle pulse or typing indicator is enough.
Background: Different from user bubbles but consistent with overall palette.

Modals

Feel: Focused attention, not interruption.
Backdrop: Subtle dimming (not black overlay). Maintain warmth.
Animation: Fade in, scale up slightly. Gentle, not snappy.
Close: Clear X, click-outside to close, ESC key support.

Settings Rows

Feel: Organized, scannable, not overwhelming.
Layout: Icon + label + value/toggle. Row-based.
Dividers: Subtle borders between rows.
Interaction: Whole-row tap targets where possible.

Empty States

Feel: Inviting, not barren. "There's nothing here yet" should feel calm.
Illustration: None or very minimal. Don't over-illustrate.
Message: Helpful, guiding. "No verses saved" → "Save verses to revisit them here."
CTA: If applicable, guide the user to add content.

Loading States

Feel: Preparing, not waiting. Never show a blank screen with nothing.
Skeleton screens: Preferred for content areas. They suggest content is coming.
Spinner: Minimal, subtle. Accent color if spinning.
Text: "Loading..." is rarely necessary. A skeleton or subtle pulse is better.

10. Motion and Interaction Principles

Transitions

Duration: 200–400ms for most transitions. Slower feels premium; faster feels responsive.
Easing: Ease-out or ease-in-out. Avoid linear. Avoid bounce-in.
Purpose: Every transition should communicate a relationship between states. If it doesn't, don't animate it.

Specific Guidelines

Avoid excessive bounce — It feels playful and unrefined.
Avoid flashy motion — No pulsing, no attention-seeking loops.
Feedback should feel polished — Button press should respond instantly. Loading should show progress.
Motion should support clarity — Moving elements should guide attention, not distract.
Hover states: Subtle lift, border change, or shadow. Never dramatic.

Flutter-Specific

Use AnimatedContainer for layout changes.
Use FadeTransition or SlideTransition for reveals.
Avoid AnimatedOpacity with long durations (can look like lag).
Respect system animations settings (accessibility).
Touch feedback: Ripple effect should be subtle, accent-tinted.

11. App-Specific Translation of Website Philosophy

The Flutter app should inherit the website's philosophy, but adapted to a product context. This is NOT about copying web sections—it's about translating emotional intent.

Translation Map

Website Concept	App Translation	Emotional Match
Hero elegance	Onboarding calmness	First impression is inviting, not overwhelming
Premium trust	Reading comfort	Users trust what they read; the UI supports trust
Conversion clarity	Navigation clarity	Next action is always obvious
Visual warmth	Session continuity	The app feels like the same brand, different room
Website polish	Interaction confidence	Every tap feels deliberate and premium

Principles for App Design

Inherit, don't copy — The app should feel like a natural continuation of the website experience, not a static replica of it.
Adapt to platform conventions — Use Material 3 or iOS-style components as appropriate. The philosophy is consistent; the implementation is native.
Reading comes first — The app is primarily a reading and conversation device. Navigation should be secondary and unobtrusive.
Conversation is intimate — Vedavaani in the app should feel like a private audience, not a public chat.
Gestures are supported — Tap, swipe, scroll. But always with clear affordance. No hidden gestures.
Offline matters — The app should work without network. Design states for offline gracefully.

12. Do / Don't Guidelines

Do

Use breathing room — Generous margins, padding, whitespace. It signals premium.
Highlight key actions clearly — Primary CTAs should stand out. Use accent color and size strategically.
Keep scripture content visually respected — Larger font, serif, centered or prominent placement, generous whitespace.
Use restrained accent colors — The orange accent is strong. Use it for actions, not for decoration.
Maintain consistency across pages — The same patterns should appear everywhere. This builds trust.
Make Vedavaani feel like a teacher — Calm responses, thoughtful timing, no "chatbot" tropes.
Use subtle shadows — A little depth helps hierarchy. Too much looks heavy.
Test readability — Every text element should pass contrast and legibility checks.

Don't

Overuse gradients — One gradient per section maximum. Avoid gradient-heavy backgrounds.
Make the UI look like a generic SaaS dashboard — This is not a productivity tool. Avoid grid-heavy, data-dense layouts.
Overdecorate with religious motifs — Om symbols, lotus motifs, ornate borders—avoid these. The reverence is in the typography and space, not decoration.
Make cards too dark or heavy — Cards are containers, not anchors. Keep them light and calm.
Use too many competing highlight colors — The palette is restrained. One accent. Don't add green, blue, pink highlights everywhere.
Make Vedavaani feel like a conventional chat app — No "typing..." with dots bouncing, no bubble-heavy interface, no "AI" badges.
Use pure black (#000) — Never use pure black for backgrounds or text. It feels harsh.
Crowd the interface — If it feels cramped, add space. Trust the whitespace.

13. Flutter Implementation Notes

Design Tokens

Tokenize everything. Use semantic names, not hardcoded values.

Color Tokens (Light Theme Example)

// Semantic roles — use these, not raw colors
color.background      = '#f4f2ed'
color.surface         = '#faf8f4'
color.surfaceElevated = '#fdfbf7'
color.textPrimary     = '#1a1a1a'
color.textSecondary   = '#4a4a4a'
color.textMuted      = '#7a7a7a'
color.border          = 'rgba(26, 26, 26, 0.08)'
color.accent         = '#f47c24'
color.accentText      = '#ffffff'
color.success        = '#3d7a5a'
color.warning        = '#c48b2e'
color.error          = '#b8464a'

Spacing Tokens

spacing.xs   = 4
spacing.sm   = 8
spacing.md   = 16
spacing.lg   = 24
spacing.xl   = 32
spacing.xxl  = 48
spacing.xxxl = 64

Radius Tokens

radius.sm    = 8
radius.md    = 16
radius.lg    = 24
radius.full  = 9999  // Pill shape

Typography Tokens

fontSize.caption = 12
fontSize.body    = 16
fontSize.h4      = 18
fontSize.h3      = 24
fontSize.h2      = 32
fontSize.h1      = 48
fontSize.hero    = 64

lineHeight.tight  = 1.2
lineHeight.normal = 1.5
lineHeight.relaxed = 1.75

Theme Extensions

Create a shared theme extension that maps tokens to ThemeData:

// Recommended structure
class GitaVedantaTheme {
  static ThemeData get light => ThemeData(
    colorScheme: ColorScheme.light(
      primary: AppColors.accent,
      onPrimary: AppColors.accentText,
      surface: AppColors.surface,
      onSurface: AppColors.textPrimary,
    ),
    scaffoldBackgroundColor: AppColors.background,
    cardTheme: CardTheme(
      color: AppColors.surface,
      elevation: 0,
      shape: RoundedRectangleBorder(
        borderRadius: BorderRadius.circular(Radius.lg),
      ),
    ),
    // ... map all tokens
  );
}

Reusable Components

Build these once, reuse everywhere:

VerseCard — Scripture display with proper typography and spacing.
ReadingSurface — The main reading area with correct contrast and margins.
AIResponsePanel — Styled container for Vedavaani responses.
PrimaryButton / SecondaryButton — With consistent radius, shadows, hover states.
AppBottomSheet — Consistent bottom sheet with rounded top corners.
SectionContainer — Standard padding and max-width for page sections.

Consistency Strategy

Shared design tokens package — If the codebase grows, consider a shared package for tokens used by both web and Flutter.
Use semantic naming — Don't name tokens orangeButton. Name them accent and accentOn.
Document in-code — Use Dart doc comments to explain the philosophy behind each token.

14. Future-Proofing

This document should support growth without losing brand identity. Keep these considerations in mind:

Additional scriptures — The design system should accommodate future texts (e.g., Upanishads, Brahma Sutras). Verse containers and reading surfaces should be content-agnostic.
Multilingual surfaces — The palette and spacing should work for English, Hindi, Sanskrit, and other scripts. Test typography with Devanagari.
More Vedavaani experiences — New conversation modes or AI features should inherit the same calm, grounded presentation. Don't create "AI mode" visual tropes.
Tablet layouts — The system should support responsive expansion. Use the same tokens; adjust layout grids.
Premium features — If future paid features are added (e.g., expert sessions, courses), they should feel like natural extensions, not upsell-heavy.
Web app / dashboard surfaces — If an admin or analytics dashboard is added later, it should use the same tokens but adapted for data density. Don't lose the warmth.

15. Mini Starter Token Table

Colors (Light Theme)

Token	Hex	Usage
`background`	`#f4f2ed`	Page background
`surface.elevated`	`#fdfbf7`	Modals, dropdowns
`surface.card`	`#faf8f4`	Cards, panels
`text.primary`	`#1a1a1a`	Headings, body
`text.secondary`	`#4a4a4a`	Subtitles
`text.muted`	`#7a7a7a`	Timestamps, hints
`border`	`rgba(26, 26, 26, 0.08)`	Dividers, outlines
`accent`	`#f47c24`	CTAs, highlights
`accent.foreground`	`#ffffff`	Text on accent
`status.success`	`#3d7a5a`	Positive feedback
`status.warning`	`#c48b2e`	Caution states
`status.error`	`#b8464a`	Error states

Spacing

Token	Value
`spacing.xs`	4px
`spacing.sm`	8px
`spacing.md`	16px
`spacing.lg`	24px
`spacing.xl`	32px
`spacing.2xl`	48px
`spacing.3xl`	64px

Radius

Token	Value
`radius.sm`	8px
`radius.md`	16px
`radius.lg`	24px
`radius.full`	9999px

Elevation (Shadows)

Token	CSS/Tailwind	Feel
`elevation.none`	none	Flat, calm
`elevation.sm`	0 1px 2px rgba(0,0,0,0.05)	Subtle lift
`elevation.md`	0 4px 12px rgba(0,0,0,0.08)	Cards, modals
`elevation.lg`	0 8px 24px rgba(0,0,0,0.12)	Floating elements

Typography

Element	Font	Size	Weight	Line Height
Hero	Serif	64px	500	1.1
H1	Serif	48px	500	1.2
H2	Serif	32px	500	1.25
H3	Serif	24px	500	1.3
Body	Sans	16px	400	1.6
Body Large	Sans	18px	400	1.75
Caption	Sans	14px	400	1.5

Design North Star

The GitaVedanta experience should feel like entering a calm, well-lit room where ancient wisdom is waiting—nothing flashy, nothing拥挤, just clarity, respect, and presence. The UI should never compete with the content it holds. Technology serves the conversation between the user and scripture. Every pixel exists to make that conversation easier to have, and easier to return to.

Last updated: April 2026 This document applies to the marketing website and all Flutter app surfaces.