# Barrio 40 — Full Site Content > This file provides complete site content for LLM and AI agent ingestion. > Source: https://barrio40.cloud | Updated: 2026-04 --- ## Home Page **URL:** https://barrio40.cloud/ **Title:** Barrio 40 — Boutique Software House ### About Barrio 40 is a boutique software house that builds sharp, purposeful digital tools. We operate at the intersection of street-level hustle and precision engineering. We build everything from enterprise Salesforce solutions to Chrome extensions, mobile apps, web apps, and AI-powered prototypes. No fluff. Just code that works. Contact: barrio40@proton.me ### What We Build **01 — Enterprise Solutions** Salesforce customization, CRM integrations, workflow automation, and back-office tooling built for the complexity of real organizations. **02 — Chrome Extensions** Browser-native tools that slot into existing workflows. Productivity, automation, data capture — built tight and deployed fast. **03 — Mobile Apps** iOS and Android. Native feel, cross-platform efficiency. We build apps people actually use — not apps that ship and stagnate. **04 — Websites & Web Apps** From marketing sites to full-stack SaaS platforms. Fast, accessible, and built to perform under real traffic. **05 — AI-Powered Prototypes** LLM integrations, intelligent automation, and rapid AI prototypes that validate ideas before you commit the budget and the roadmap. **06 — Digital Tools** Internal dashboards, data pipelines, admin panels, scripts. Whatever makes the team move faster — we build it right the first time. ### Our Approach **Principle 1 — Sharp by Design** We cut scope, not quality. Every feature earns its place. If it doesn't serve a real purpose, it doesn't ship. Purposeful, minimal, precise — that's the standard. **Principle 2 — Code That Works** No prototypes that fall apart on day two. We build with production in mind from day one — tested, observable, and maintainable by whoever comes next. **Principle 3 — Move With Urgency** Street-level hustle means bias for action. We start, iterate, and ship. Speed and quality aren't opposites — we treat them as partners, not trade-offs. ### Selected Work **Salesforce Workflow Engine** (Enterprise / Salesforce, 2024) Full Salesforce platform overhaul for a mid-market B2B company — unified CPQ, Service Cloud, and partner portal into a single coherent system. Zero downtime migration. **Salesforce Screen Recorder** (Chrome Extension, 2024) Captures reproduction steps, screenshots, and optional debug log data directly from Salesforce Lightning pages — then packages everything into a structured ZIP that developers can drop into GitHub Copilot to rapidly analyze and fix bugs. Live on Chrome Web Store: https://chromewebstore.google.com/detail/salesforce-screen-recorde/figlgicephkldedplehahegfghphhceb **Tasted** (Mobile App, 2025) Your personal sommelier, in your pocket. Log wines, spirits, beers, and cocktails — with AI-powered tasting notes, worldwide bar discovery, and zero accounts required. Everything lives on your device, ready offline, always yours. **SafeCommute** (Mobile / Web App, 2025) Community-powered urban safety platform giving commuters real-time visibility into hazards, incidents, and route conditions — across cycling, transit, e-scooters, and walking. **SubTracker** (Web App, 2025) SaaS spend intelligence for freelancers and small teams. One dashboard to track, analyse, and optimise software subscriptions — surfacing savings opportunities, renewal risks, and cost-per-project breakdowns automatically. **SF Docs Portal** (Digital Tool, 2025) Static site generator that transforms Salesforce repository metadata into a comprehensive, searchable documentation website — covering security, data models, automation, UI components, and architecture. No backend required. **AgentOps** (AI Platform, 2025) Single control plane for running, supervising, and iterating on AI agents at scale — handling scheduling, execution, budgeting, approvals, and observability across single agents or entire multi-agent teams spanning dozens of initiatives. --- ## Blog — Field Notes **URL:** https://barrio40.cloud/blog/ **Title:** Field Notes — Barrio 40 **Description:** Thoughts on software engineering, AI, and building products from the Barrio 40 studio. ### Posts 1. **How We Built the Salesforce Screen Recorder** (Chrome Extensions, 2025-03-12) URL: https://barrio40.cloud/blog/posts/salesforce-screen-recorder-how-we-built-it.html A look inside the architecture of our most-used Chrome extension — from capturing Lightning page state to bundling structured ZIPs that GitHub Copilot can actually reason about. 2. **When to Use AI Agents (and When Not To)** (AI, 2025-02-20) URL: https://barrio40.cloud/blog/posts/when-to-use-ai-agents.html Agents are powerful and overhyped in equal measure. Here's the four-question filter we apply before reaching for an agentic architecture on any client project. 3. **Offline-First Mobile: What Nobody Tells You** (Mobile, 2025-01-08) URL: https://barrio40.cloud/blog/posts/offline-first-mobile.html Building Tasted taught us a lot about offline-first architecture on React Native. Conflict resolution, sync strategies, and why "no account required" is a product decision as much as a technical one. 4. **Generating Salesforce Docs From Metadata** (Salesforce, 2024-11-30) URL: https://barrio40.cloud/blog/posts/static-site-generators-salesforce.html How we built SF Docs Portal — a static site generator that turns raw Salesforce repository metadata into a fully searchable architecture documentation site. Zero backend, zero config. 5. **Boutique Studio vs. Agency: Why We Chose Small** (Studio, 2024-10-15) URL: https://barrio40.cloud/blog/posts/boutique-vs-agency.html We could have grown into an agency. We chose not to. The case for staying small, staying sharp, and why "boutique" isn't a polite word for "we can't scale". --- ## Blog Post — How We Built the Salesforce Screen Recorder **URL:** https://barrio40.cloud/blog/posts/salesforce-screen-recorder-how-we-built-it.html **Published:** 2025-03-12 **Category:** Chrome Extensions **Tags:** Chrome Extension, Salesforce, Developer Tools, GitHub Copilot, Manifest V3 ### The Problem Bug reproduction in Salesforce is painful. A developer gets a ticket that says "the Opportunity page crashes sometimes" with a screenshot of a spinner. No steps. No console output. No org context. They spend 30 minutes just trying to reproduce it before they can even start fixing it. We've seen this pattern on every Salesforce project we've worked on. The gap isn't a skills problem — it's a tooling problem. Developers don't have a fast way to capture the full context of a bug: what page, what record, what user actions, what the Lightning component tree looked like, and what errors appeared in the console. So we built one. ### What It Captures The Salesforce Screen Recorder is a Chrome extension that sits on any Salesforce Lightning page and — on demand — packages up: - A screen recording of the reproduction steps, captured via the Chrome tab capture API - Screenshots at key moments (start, error, end) - Page metadata — the current URL, record ID, object type, and active app - Console output — errors, warnings, and debug logs from the Lightning runtime - Optional: Salesforce debug logs — Apex execution traces, SOQL queries, governor limit usage Everything gets packaged into a structured ZIP with a manifest.json at the root that describes the contents. ### The Copilot Angle We built the ZIP format with GitHub Copilot Workspace in mind. When you drop a structured ZIP into Copilot, it can reason about the whole context — not just a single file. The manifest.json tells it exactly what's in the bundle, the debug log gives it the Apex trace, and the screenshots give it visual context. Developers using the extension report that a bug that used to take 30–45 minutes to diagnose takes 5–10 minutes — mostly because the reproduction context is complete before they even open their IDE. ### The Architecture Chrome Manifest V3 constraints that shaped the architecture: - Service workers replace persistent background pages. MV3 uses ephemeral service workers — state must be persisted via Chrome's storage API across worker lifecycles. - Tab capture requires a visible popup. The chrome.tabCapture API only works from a user gesture in a popup, not from a content script or background worker. - Debug log retrieval is asynchronous and rate-limited. Pulling debug logs from the Salesforce Tooling API requires an active session and respects per-org API limits — implemented with polling and backoff. The ZIP assembly uses JSZip running in the popup context, streaming the screen recording directly into the ZIP rather than holding the whole video in memory. ### What We Learned The most surprising part wasn't the technical constraints — it was how much of the value came from structure rather than completeness. An unstructured dump of everything is useless. A structured manifest with well-named files that a model can parse is transformative. That principle has shaped how we think about developer tooling in general: the output of a tool isn't just data — it's data in a shape that the next tool (human or AI) can immediately act on.