Welcome - this is your central place to talk monday vibe
This is an open space to ask questions, share use cases, and tell us your feedback on your experience with vibe.
Our product teams are actively reading everything here and using your input to learn and improve. We’re excited to see what you’ve built and what insights you’d like to share with the community!
We’ll keep this thread pinned and open, so anyone can learn, get inspired, and take part in the conversation. 💬
Title: Building a Complete Field Operations Operating System on monday.com
Summary: We have developed a custom React application that acts as a unified “Operating System” for our field engineering and survey teams. By leveraging the monday.com Apps Framework, we transformed standard boards into two distinct, purpose-built interfaces: a Command Center for Managers and a Mobile Companion for Field Workers.
The Challenge
Managing a distributed team of engineers and surveyors requires more than just list views. We needed to solve:
Safety Compliance: Ensuring daily van checks and risk assessments (RAMS) are actually completed, not just ticked off.
Navigation & Routing: Visualizing jobs on a map to optimize travel time.
Data Fragmentation: Connecting HR (Holidays), Fleet (Vehicles), and Operations (Jobs/Surveys) into one view.
Field Simplicity: Giving workers a simple, button-driven mobile interface without exposing them to complex board columns.
The Solution
The app detects the user’s device and role to serve one of two views:
1. The Manager View (Desktop Command Center)
A glass-morphism styled dashboard that provides a 360-degree view of operations.
Visual Scheduling: A drag-and-drop timeline and a map-based view of all upcoming jobs (filtered by region: Scotland vs. England).
Fleet Management: Live GPS tracking integration for vans, plus automated tracking of MOT and Service due dates.
Financials: A “Chargeable Work” module that aggregates billable jobs, tracks PO numbers, and manages invoice statuses (Draft $\rightarrow$ Sent $\rightarrow$ Paid).
HR Integration: A holiday approval dashboard that cross-references staff availability against the schedule.
2. The Field Worker View (Mobile Companion)
A simplified, touch-friendly interface designed for use on the road.
Mandatory Workflows: The app enforces a “Daily Van Check” modal upon login. Workers cannot see their jobs until they submit their vehicle safety inspection (with photo uploads for defects).
Job Execution:
One-Tap Navigation: Deep links to Google Maps for job locations.
Safety First: A “Job Workflow” modal requires Pre-Assessment checks and RAMS generation before a job can be marked “In Progress.”
PDF Generation: The app generates professional PDF reports (Van Checks, RAMS, Survey Reports) client-side and uploads them back to monday.com automatically.
Offline-Ready Manuals: Access to technical plant manuals directly within the app.
Technical Highlights
Tech Stack: React 18, Chakra UI (v3), Leaflet Maps, Recharts, and pdfmake.
Data Architecture:
Aggregated Data: We pull from 5 different boards (Jobs, Routine Surveys, Chargeable Surveys, Vehicles, Staff Holidays) and normalize the data into a single state for the UI.
Smart Caching: Uses useMemo heavily to sort tasks, calculate KPIs, and generate map markers without performance lag.
Optimistic Updates: The UI updates immediately while the SDK handles the backend sync.
Map Integration: Custom logic correlates the “Schedule List” order (1, 2, 3…) with Map Markers, so “Job #1” on the list is always “Pin #1” on the map.
Key Features at a Glance
Smart Maps: Markers are color-coded by status (Blue=Upcoming, Orange=In Progress, Red=Overdue).
Dynamic Forms: The “Book In” tab checks staff availability in real-time before allowing a job to be scheduled.
Document Automation: We generate complex 4-page Risk Assessment documents on the fly based on job data and user inputs.
I am building a set of apps for our 3D Printing, CAD Design, Prototyping & R&D business.
We have used Monday for years - but we were just getting to the point of potentially ditching it for a more custom solution. However, this is right when VIBE was rolled out. That completely changed our trajectory.
The end goal is to turn the apps into a single source of truth for physical + digital work (And for those that don’t know - managing digital AND accompanying physical assets through the process is difficult) across the entire business. This includes tracking parts, assemblies, versions, documentation, repair logs, customer property tracking, meetings, etc in a way that stays usable even as projects evolve over months or years - while also being stable.
What I’m actively building includes:
A Parts & Assemblies system that tracks digital versions, physical versions, linked CAD files, images, and revision history.
Embedded documentation cards for technical specs, research notes, and decisions that live with the part, not in external tools
Version history timelines that show how a part or assembly changed over time (digital and physical)
Property custody tracking for customer-owned equipment and components
Resilience-focused data design, including pointer storage, ID recovery, and emergency export/import tooling so the app can survive data loss or reinstallation
UI that’s optimized for technicians and engineers, not just project managers (dense, readable, low-friction)
A big focus has been making sure data is:
Deterministic (no “magic” lookups that silently fail)
Recoverable (JSON exports + restore testing)
Explicitly linked (IDs stored intentionally, not inferred)
I’m using Vibe with small micro prompts to avoid unintended refactors, and I’m stress-testing edge cases like deleted subitems, wiped storage, and cross-device usage.
I am at the point now, I need to start understanding the data storage side of things better.
Welcome - this is your central place to talk monday vibe 
We’re excited to see what you’ve built and what insights you’d like to share with the community!
The Challenge
The Manager View (Desktop Command Center)
The Field Worker View (Mobile Companion)
Technical Highlights
Key Features at a Glance
