> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bloom.diy/llms.txt
> Use this file to discover all available pages before exploring further.

# Glossary

> Key terms and concepts used throughout Bloom.

## A

<AccordionGroup>
  <Accordion title="A/B Testing">
    A method of comparing two versions of a screen or feature to determine which performs better based on user behavior. Useful for optimizing conversion rates and user engagement.
  </Accordion>

  <Accordion title="Above the Fold">
    The portion of a screen visible to users without scrolling. Crucial for capturing attention and conveying essential information immediately.
  </Accordion>

  <Accordion title="Accordion">
    A collapsible UI component that expands or contracts to reveal or hide content dynamically. Useful for FAQs, settings, and organizing dense information.
  </Accordion>

  <Accordion title="API (Application Programming Interface)">
    A way for different services to communicate. APIs define what kind of information you can get or send between systems. Bloom uses APIs to connect your app to external services. See [API Connections](/api-connections).
  </Accordion>

  <Accordion title="API Key">
    A credential that authenticates your app when connecting to external services like OpenAI, Stripe, or analytics platforms. Bloom provides auto-provisioned keys for quick setup, or you can use your own. See [API Connections](/api-connections).
  </Accordion>

  <Accordion title="App Clip">
    A lightweight version of an iOS app that users can access instantly without downloading from the App Store. Bloom uses App Clips for [instant sharing](/instant-sharing), allowing testers to try your app by scanning a QR code.
  </Accordion>

  <Accordion title="Authentication">
    The process of verifying a user's identity. Bloom uses OAuth to let users sign in with existing accounts from Google, GitHub, or Apple. See [Authentication](/authentication).
  </Accordion>

  <Accordion title="Autocomplete">
    A text input that dynamically suggests matching results as users type, improving usability in search fields and forms.
  </Accordion>
</AccordionGroup>

## B

<AccordionGroup>
  <Accordion title="Backend">
    The server-side part of your app that handles data storage, business logic, and integrations. In Bloom, your backend is powered by Convex and is automatically configured. See [Backend Dashboard](/backend-dashboard).
  </Accordion>

  <Accordion title="Badge">
    A small visual indicator, often used on icons or buttons, to show notifications, counts, or status updates.
  </Accordion>

  <Accordion title="Bloom-managed credentials">
    API keys and OAuth credentials that Bloom provides and maintains for you. These let you get started immediately without creating accounts with external providers. You can switch to your own credentials at any time.
  </Accordion>

  <Accordion title="Breadcrumb">
    A navigational aid displaying the user's current location within an app's hierarchy, often represented as a horizontal list of links.
  </Accordion>

  <Accordion title="Button">
    A clickable element that initiates an action or event, such as submitting a form, navigating to a screen, or triggering a feature.
  </Accordion>
</AccordionGroup>

## C

<AccordionGroup>
  <Accordion title="Checkbox">
    An interactive box that users can check or uncheck to select or deselect an option, allowing multiple selections within a set.
  </Accordion>

  <Accordion title="Conversion Rate">
    The percentage of users who complete a desired action, such as signing up, making a purchase, or completing onboarding.
  </Accordion>

  <Accordion title="Convex">
    The backend platform that powers every Bloom app. Convex provides a real-time database, serverless functions, file storage, and scheduled tasks. Learn more at [docs.convex.dev](https://docs.convex.dev).
  </Accordion>

  <Accordion title="Cross-platform">
    The ability to run on multiple operating systems from a single codebase. Bloom apps are cross-platform by default, running on iOS, Android, and the web.
  </Accordion>

  <Accordion title="CRUD">
    An acronym for Create, Read, Update, Delete, the four basic operations for managing data. When you describe features to Bloom, it implements the appropriate CRUD operations automatically.
  </Accordion>

  <Accordion title="CTA (Call to Action)">
    A prompt, often in the form of a button or link, encouraging users to perform a specific action, such as "Sign Up," "Get Started," or "Learn More."
  </Accordion>
</AccordionGroup>

## D

<AccordionGroup>
  <Accordion title="D.N.A. Framework">
    Bloom's recommended approach to prompting: **D**escribe the user, **N**arrate the journey, and set the **A**tmosphere. This framework helps you communicate your vision effectively. See [Prompting Best Practices](/prompting-best-practices).
  </Accordion>

  <Accordion title="Dashboard">
    The main Bloom interface where you manage your apps, view usage, and access settings. Also refers to the Backend Dashboard for monitoring your Convex deployment.
  </Accordion>

  <Accordion title="Date Picker">
    A UI element that lets users select a date from a calendar instead of manually typing it.
  </Accordion>

  <Accordion title="Deploy">
    The process of making your app available to users. In Bloom, this can mean generating a share link (instant) or publishing to app stores (requires review).
  </Accordion>

  <Accordion title="Dialog (Modal)">
    A window that appears in front of the main content to capture user attention, often requiring an action before returning to the primary interface.
  </Accordion>

  <Accordion title="Drawer">
    A panel that slides in from the side of the screen to display navigation options or settings without disrupting the main content.
  </Accordion>

  <Accordion title="Dropdown Menu">
    A list of options that appears when a user taps a button or field, commonly used for navigation or selection.
  </Accordion>
</AccordionGroup>

## E

<AccordionGroup>
  <Accordion title="Environment Variables">
    Configuration values stored securely outside your code, typically used for API keys and secrets. Bloom lets you manage environment variables directly in the workspace. See [API Connections](/api-connections).
  </Accordion>

  <Accordion title="Expo">
    The React Native framework that powers Bloom's frontend. Expo enables cross-platform development with native performance and features like hot reload and over-the-air updates. Learn more at [docs.expo.dev](https://docs.expo.dev).
  </Accordion>

  <Accordion title="Export">
    The ability to download your Bloom project as code. You can export your Expo + Convex codebase to continue development locally or sync with GitHub.
  </Accordion>
</AccordionGroup>

## F

<AccordionGroup>
  <Accordion title="Favicon">
    A small icon displayed in the browser tab, bookmarks, and search results, typically representing your app or brand.
  </Accordion>

  <Accordion title="Footer">
    The bottom section of a screen, commonly containing supplementary information such as contact details, navigation links, and legal disclaimers.
  </Accordion>

  <Accordion title="Form">
    A structured collection of input fields allowing users to submit data, such as contact information, settings, or search queries.
  </Accordion>

  <Accordion title="Frontend">
    The user-facing part of your app, including screens, buttons, forms, and navigation. In Bloom, your frontend is built with Expo (React Native).
  </Accordion>

  <Accordion title="Full-stack">
    An app that includes both frontend (user interface) and backend (server, database, logic). Every Bloom app is full-stack by default.
  </Accordion>

  <Accordion title="Function">
    A piece of backend logic that runs on the server. In Convex, functions handle database queries, mutations, and scheduled tasks. You can view your functions in the [Backend Dashboard](/backend-dashboard).
  </Accordion>
</AccordionGroup>

## G

<AccordionGroup>
  <Accordion title="Generation">
    The process of Bloom creating or updating your app based on your prompts. Each time you describe a change, Bloom generates the necessary code and configuration.
  </Accordion>

  <Accordion title="GitHub">
    A web-based platform for version control and collaborative software development using Git. Bloom projects can be synced with GitHub for code export and collaboration.
  </Accordion>

  <Accordion title="Gradient">
    A gradual transition between two or more colors in design, often used for backgrounds, buttons, or decorative elements.
  </Accordion>
</AccordionGroup>

## H

<AccordionGroup>
  <Accordion title="Hot Reload">
    A development feature that updates your app instantly when changes are made, without losing the current state. Bloom's preview uses hot reload so you see changes in real time.
  </Accordion>
</AccordionGroup>

## I

<AccordionGroup>
  <Accordion title="Instant Sharing">
    Bloom's feature that lets you share your app immediately via link or QR code, without app store approval. See [Instant Sharing](/instant-sharing).
  </Accordion>

  <Accordion title="Integration">
    A connection between your app and an external service, like a payment processor, analytics tool, or AI model. See [Integrations](/integrations).
  </Accordion>
</AccordionGroup>

## L

<AccordionGroup>
  <Accordion title="Live Preview">
    The real-time view of your app in the Bloom workspace. Changes you make appear in the preview immediately, letting you test as you build.
  </Accordion>

  <Accordion title="Loading Spinner">
    A visual indicator that represents a process in progress, such as loading a screen or submitting a form.
  </Accordion>

  <Accordion title="Logs">
    Records of events, errors, and activity in your app. Bloom provides unified logs for both frontend and backend. See [Logs](/logs).
  </Accordion>
</AccordionGroup>

## M

<AccordionGroup>
  <Accordion title="Mutation">
    A Convex function that modifies data in the database (create, update, or delete operations). Mutations are automatically generated when you describe data changes to Bloom.
  </Accordion>

  <Accordion title="MVP">
    Minimum Viable Product. The simplest version of your app that delivers core value. Bloom is ideal for building MVPs quickly to test ideas with real users.
  </Accordion>
</AccordionGroup>

## O

<AccordionGroup>
  <Accordion title="OAuth">
    An authentication standard that lets users sign in using existing accounts (like Google or GitHub) without sharing their passwords with your app. Bloom uses OAuth for all authentication.
  </Accordion>

  <Accordion title="Optimistic UI">
    A pattern where the interface updates immediately before the server confirms the change, making the app feel faster. Bloom implements optimistic updates automatically for a responsive user experience.
  </Accordion>
</AccordionGroup>

## N

<AccordionGroup>
  <Accordion title="Navigation Bar">
    A horizontal or vertical menu providing links to essential sections of an app for easy navigation. Often appears at the top or bottom of mobile screens.
  </Accordion>
</AccordionGroup>

## P

<AccordionGroup>
  <Accordion title="Pagination">
    A method of dividing content into multiple pages, commonly used for long lists or search results to improve performance and user experience.
  </Accordion>

  <Accordion title="Persona">
    A fictional representation of a target user, based on research, to guide design and development decisions. Useful when describing users to Bloom.
  </Accordion>

  <Accordion title="Popover">
    A transient overlay that presents additional information or options related to a specific UI element, typically appearing upon user interaction.
  </Accordion>

  <Accordion title="Progress Bar">
    A horizontal bar that indicates the completion percentage of a task or process.
  </Accordion>

  <Accordion title="Progressive Web App (PWA)">
    A web app that can be installed on a device and used like a native app. On Android, Bloom apps shared via link run as PWAs.
  </Accordion>

  <Accordion title="Prompt">
    The natural language description you give Bloom to create or modify your app. Effective prompts describe the user, their journey, and the desired atmosphere.
  </Accordion>
</AccordionGroup>

## Q

<AccordionGroup>
  <Accordion title="Query">
    A Convex function that reads data from the database. Queries are reactive in Convex, meaning your UI updates automatically when the underlying data changes.
  </Accordion>

  <Accordion title="QR Code">
    A scannable code that links to your shared app. Users can scan the QR code with their phone camera to open your app instantly.
  </Accordion>
</AccordionGroup>

## R

<AccordionGroup>
  <Accordion title="Radio Group">
    A set of related radio buttons permitting users to select only one option from multiple choices.
  </Accordion>

  <Accordion title="React Native">
    A framework for building native mobile apps using JavaScript and React. Expo (which Bloom uses) is built on top of React Native.
  </Accordion>

  <Accordion title="Real-time Sync">
    The automatic synchronization of data across all connected devices. When data changes in Convex, all users see the update instantly without refreshing.
  </Accordion>

  <Accordion title="Refactor">
    The process of restructuring existing code without changing its external behavior to improve readability, maintainability, or performance.
  </Accordion>

  <Accordion title="Responsive Design">
    An approach to design ensuring that content adapts seamlessly across various device sizes and orientations, providing an optimal user experience.
  </Accordion>

  <Accordion title="Retention Rate">
    The percentage of users who continue using your app over time. A key metric for measuring product success.
  </Accordion>
</AccordionGroup>

## S

<AccordionGroup>
  <Accordion title="Schema">
    The structure of your database, defining what tables exist and what fields they contain. Bloom creates schemas automatically based on your descriptions.
  </Accordion>

  <Accordion title="Serverless">
    A cloud computing model where the provider manages servers automatically. Convex is serverless, meaning your backend scales without any infrastructure management.
  </Accordion>

  <Accordion title="Skeleton Loader">
    A placeholder UI that mimics the layout of the final content while waiting for it to load, improving perceived performance.
  </Accordion>

  <Accordion title="Slider">
    A control that allows users to set a value within a range by sliding a handle along a track.
  </Accordion>

  <Accordion title="Stepper (Wizard)">
    A component used for multi-step processes, showing users their current step and guiding them through completion.
  </Accordion>

  <Accordion title="Storage">
    A service for storing and managing files such as images, videos, and documents. Convex includes built-in file storage for your Bloom apps.
  </Accordion>

  <Accordion title="Switch (Toggle)">
    A toggle control enabling users to switch between two states, such as on or off, often resembling a physical switch.
  </Accordion>
</AccordionGroup>

## T

<AccordionGroup>
  <Accordion title="Tabs">
    A component that organizes content into separate views within a single interface, allowing users to switch between sections without navigating away.
  </Accordion>

  <Accordion title="Text Field">
    A basic UI element where users can enter text, such as in search bars, login forms, or comments.
  </Accordion>

  <Accordion title="Theme">
    A cohesive set of design choices, including colors, fonts, and layouts, that define the overall aesthetic and user experience of an app.
  </Accordion>

  <Accordion title="Toast">
    A brief, non-intrusive notification that appears temporarily to inform users of an action's outcome or provide simple feedback.
  </Accordion>

  <Accordion title="Tooltip">
    A small pop-up box that provides additional information when hovering over or focusing on an element.
  </Accordion>

  <Accordion title="Two-Factor Authentication (2FA)">
    A security measure that requires users to provide two forms of identification before accessing an account.
  </Accordion>
</AccordionGroup>

## U

<AccordionGroup>
  <Accordion title="User Journey">
    The series of steps a user takes to achieve a specific goal within your app. Understanding user journeys helps you design better experiences and write more effective prompts.
  </Accordion>

  <Accordion title="User Story">
    A short, simple description of a feature or requirement written from the perspective of an end user. Example: "As a user, I want to save my progress so I can continue later."
  </Accordion>
</AccordionGroup>

## V

<AccordionGroup>
  <Accordion title="Vibe Coding">
    A style of AI-assisted development where you describe the feel and experience you want rather than technical specifications. Bloom is designed for vibe coding.
  </Accordion>
</AccordionGroup>

## W

<AccordionGroup>
  <Accordion title="Webhook">
    An event-driven HTTP callback that notifies external applications when specific actions occur in your app.
  </Accordion>

  <Accordion title="Workspace">
    The main Bloom interface for building your app, including the chat, code view, preview, and backend tools. Everything you need is in one place.
  </Accordion>
</AccordionGroup>

***

## Missing a term?

<Card title="Contact Support" icon="headset" href="/support">
  Let us know if there's a term you'd like us to add to the glossary.
</Card>