Skip to content

Glossary

This glossary defines the core terminology used throughout our home bar organization system. Using these terms consistently ensures clear communication across all contexts.

A scheduled gathering for which a custom drink menu is created. Events have themes, guest lists, and specific menu requirements.

The stylistic concept that unifies an event and its corresponding menu. Themes influence recipe selection, ingredient choices, and presentation styles.

A collection of people invited to an event, including their RSVP status and preferences.

An individual attending an event, with tracked preferences, dietary restrictions, and feedback history.

Recorded likes, dislikes, and allergies of specific guests to inform menu planning.

The projected number of guests expected to attend an event, used for calculating ingredient quantities.

The physical location where an event is held, containing one or more bars and storage areas.

A designated area within a venue for keeping inventory, such as a dry storeroom or a cold cellar.

The physical space where drinks are stored, prepared, and served. Includes the counter space, storage areas, and display elements.

A curated collection of drink offerings created specifically for an event. Menus align with event themes and guest preferences.

An individual cocktail entry on a menu, including name, ingredients, and preparation method.

A highlighted cocktail given special prominence on a menu, often theme-aligned.

The analysis of a menu’s overall flavor profile distribution, ensuring variety and cohesion.

Evaluation of a menu’s flavor profile distribution across all drinks to ensure variety and cohesion.

Detailed instructions for preparing a specific cocktail, including measured ingredients, techniques, and required tools.

A specific ingredient used in a recipe, including its measurement and any special preparation instructions.

A classification for recipes based on preparation method, base spirit, or drink style.

The analysis of a recipe’s flavor components to ensure it is well-balanced and harmonious.

A mapping between a recipe and the specific tools required to prepare it properly.

A scaled version of a recipe designed for preparing multiple servings at once.

The characteristic taste elements that define a drink’s overall sensory experience.

Quantified taste characteristics across 8 dimensions: Sweet, Sour, Bitter, Umami, Spicy, Herbal, Floral, and Fruity, each rated 0-10.

A specific taste attribute like sweet, sour, bitter, umami, spicy, etc.

The documented flavor characteristics of a specific ingredient and how it contributes to cocktails.

Recommended ingredient adjustments to improve a recipe’s flavor profile.

Radar/spider chart visualization displaying an ingredient’s or recipe’s flavor profile across all 8 dimensions.

Interactive component with sliders for adjusting each of the 8 flavor dimensions when creating or editing ingredients.

Bidirectional relationship between ingredients with similar flavor profiles, suggesting alternatives when an ingredient is unavailable.

A keyword or category label that can be applied to various entities in the system for organization and searching.

An interface implemented by entities that can have tags applied to them.

The complete collection of all ingredients, tools, equipment, and glassware available for use in the bar.

A specific item in inventory, such as a bottle of spirits, bitters, or other ingredients.

A unique identifier for scanning and identifying products.

Information about a product, including brand, type, pricing, and other metadata.

The current quantity of a product in inventory, tracked for shopping list generation.

Visual component showing the current inventory level of a product as a percentage (0-100%) with color coding (green/yellow/red).

A compilation of ingredients needed for an upcoming event based on the planned menu and inventory shortages.

Automated creation of procurement lists based on event menus, guest counts, and current inventory levels.

Process of combining duplicate ingredients across multiple recipes and calculating total quantities needed.

Barcode standard used for product identification, scanned via the device camera for quick inventory addition.

Camera-based feature for identifying products by scanning their UPC codes to automatically populate product information.

Feature allowing multiple products to be scanned in sequence and queued for processing.

The configuration of tools, ingredients, and equipment needed for a specific event.

The specific arrangement of tools, ingredients, equipment, and glassware needed for an event.

A physical implement used in drink preparation (shaker, jigger, strainer, bar spoon, etc.).

Larger items required for bar operation (blenders, ice machines, coolers, etc.).

A classification of bar tools based on their function (measuring, mixing, straining, etc.).

A prepared large-format version of a cocktail ready for service at an event.

A utility that determines appropriate quantities when scaling recipes for large groups.

A standard unit for measuring ingredients (oz, ml, dash, etc.).

A utility for converting between different measurement units when scaling recipes.

Alcoholic base for cocktails (whiskey, gin, vodka, rum, tequila, etc.).

Non-alcoholic liquid ingredient used to complement spirits in cocktails (tonic water, soda, juice, etc.).

Ingredient that changes the flavor profile of a cocktail (vermouth, bitters, liqueurs, etc.).

Decorative and flavor-enhancing addition to a cocktail (citrus peel, herbs, fruits, etc.).

Ingredient used to add sweetness to a drink (simple syrup, honey, agave nectar, etc.).

Any component used in a recipe, categorized as spirit, mixer, modifier, garnish, or sweetener.

The manner in which drinks are presented and served to guests.

Guest opinions and ratings collected after an event to improve future experiences.

External service for ordering ingredients and supplies.

External database of product information accessible via barcode scanning.

Tool for identifying products by scanning their barcodes.

External service for communicating with guests about events.

The Elixir/Phoenix backend server that provides the GraphQL API and data persistence for Bartendie.

Authentication and user management service integrated into Shaker for secure login and session handling.

The mobile application component of Bartendie, built with React Native and Expo for iOS and Android platforms.

Cross-platform mobile framework for building native iOS and Android applications using JavaScript and React.

Development platform and tooling for React Native applications, providing managed workflow and native modules.

File-based navigation system for React Native apps, providing type-safe routing and deep linking.

Collection of native modules and APIs provided by Expo for camera, secure storage, image handling, and other device features.

Encrypted local storage module for sensitive data like authentication tokens.

Native camera module used for barcode scanning functionality.

Module for triggering device vibration and haptic feedback.

Statically-typed superset of JavaScript used throughout Shaker for type safety and improved developer experience.

Bottom navigation bar with 5 main sections (Dashboard, Events, Recipes, Inventory, Settings) for primary app navigation.

Hierarchical navigation pattern where screens are stacked on top of each other, allowing users to drill down into details.

Overlay screen that appears on top of the current view, typically for focused tasks or confirmations.

URL-based navigation that allows external links to open specific screens within the app (e.g., shaker://recipes/123).

Interactive area of a UI element, with a minimum size of 44pt × 44pt for accessibility.

Loading placeholder that shows the structure of content before data is loaded, improving perceived performance.

Tactile vibration responses triggered by user interactions to provide physical confirmation of actions.

React component that catches JavaScript errors in child components and displays fallback UI instead of crashing.

UI and behavior adjustments for iOS vs Android platform conventions and design guidelines.

The NeoBrutalism-inspired design system used in Shaker, featuring bold colors, thick borders, and solid shadows.

Design aesthetic characterized by bold, high-contrast colors, thick black borders (3-6px), solid shadows without blur, and a playful, energetic feel.

Tailwind CSS implementation for React Native, enabling utility-first styling in mobile apps.

Centralized configuration values for colors, typography, spacing, borders, and shadows that ensure visual consistency.

Type-safe component variant system for creating reusable styled components with multiple visual states.

Web Content Accessibility Guidelines Level AA compliance standard, ensuring color contrast and accessibility features.

GraphQL client library used for state management, data fetching, and normalized caching in the mobile app.

Query language and API specification used for communication between Shaker and the Well backend.

WebSocket-based real-time communication system for live updates and subscriptions.

Apollo Client’s data storage strategy that eliminates duplication by storing entities once and referencing them by ID.

Pattern where the UI updates immediately based on expected results before server confirmation, improving perceived responsiveness.

Architecture pattern where the app functions with local data when offline and syncs changes when connectivity is restored.

TypeScript-based data structures for recipes, ingredients, and reference data that work without network connectivity.

GraphQL subscription that pushes live updates from the server to the app via Phoenix Channels.

Secure token format used for API authentication between Shaker and Well backend.

The person organizing the event and planning the menu.

The person responsible for preparing the bar setup and making drinks.

The people attending the event and consuming the drinks.