Skip to content
Fernando
Email Me
← All projects
Product Lab Needs confirmation

Fudomy

Built and integrated restaurant operations software across dashboard UI, API services, and customer reward and check-in flows with payment and messaging infrastructure.

Business SoftwareNode.js APIFirebaseStripeWhatsApp IntegrationAdmin Dashboard
Dashboard Domain↗
dashboard.fudomy.com
Fudomy case study screenshot

Overview

Fudomy is a product-lab business software platform for restaurant operations, combining dashboard tooling, API services, and customer-facing reward and check-in flows.

The Problem

Loyalty, messaging, and billing operations are often fragmented across disconnected tools and manual workflows.

The Solution

The platform centralizes operational modules for clients, rewards, messaging, visits, and billing, with API-backed services and integration plumbing.

My Role

Owner / Lead Developer

Repository structure suggests substantial engineering ownership, but project role and showcase permissions should be confirmed before stronger claims.

Current Status
Large practical codebase with production and test infrastructure hints. Public availability and live usage outcomes need confirmation.
Closing Takeaway

"Fudomy is evidence of integration-heavy business software execution, especially around backend architecture and operator-facing workflow tooling."

Key Features

Multi-entity admin workflows for restaurants, branches, users, clients, and visits.

Rewards and redeemed rewards lifecycle operations.

Template-based messaging and scheduled automation flows.

Invoice and wallet operations with card management hooks.

WhatsApp sender setup and template handling.

App Clip-style reward and check-in journey integration.

Technical Implementation

Frontend / Mobile

  • Firebase-hosted dashboard with modular scripts by operational domain.
  • Environment-aware test and production frontend behavior.
  • Separate iOS App Clip codebase for customer reward and check-in moments.

Backend / API

  • Express and TypeScript route groups for auth, users, clients, rewards, visits, messages, templates, wallet, and invoices.
  • Service and repository architecture with middleware auth and role checks.
  • Production and test endpoint separation patterns.

Database / Storage

  • Firestore repository pattern for operational entities.
  • Firebase Storage repository for assets and media.

AI / Integrations

  • No core AI model integration identified in the provided Fudomy source summary.

Deployment / Security

  • Token-based auth middleware and role authorization checks.
  • Firebase Hosting deploy paths for test and production targets.

Product & Design Decisions

  • ✓

    Separate domain modules for clearer operational ownership.

  • ✓

    Use service and repository layering instead of ad hoc route logic.

  • ✓

    Keep distinct test and production routing for safer rollout behavior.

Challenges & Tradeoffs

  • ⚠

    Managing broad multi-tenant operational workflows with consistent authorization behavior.

  • ⚠

    Balancing breadth of modules with dashboard usability.

  • ⚠

    Coordinating payments, messaging, and background-task integrations.