FYTHUB: The Scalable Fitness Platform

The FYTHUB App addresses challenges faced by personal trainers in the Australian fitness industry, focusing on revenue generation, scalability, and client engagement. It enables trainers to expand beyond in-person sessions using customizable digital programs.

πŸ‹οΈ

Target: Professionals

Designed to empower certified trainers to scale services.

πŸ’°

Revenue Share

Trainers retain 70-80% of income for sustainable growth.

🌐

Expand Reach

Reach clients beyond geographical constraints via online programs.

User Flow Analysis: Roles & Capabilities

This section details the distinct feature sets and user journeys for the three defined roles: the self-starting **Free User**, the professionally coached **Premium User**, and the business-focused **Trainer**. Click the tabs to explore each flow.

Free User: The Self-Starter

Purpose: Free users can track their food consumption and workouts manually, or create simple, repetitive meal and workout templates. This tier serves as the primary funnel for the platform.

Meal Tracking Flow (Manual)

  • β€’Select 'Track Meal' > 'Add meal for the day'
  • β€’Enter food name (e.g., Spaghetti Bolognese)
  • β€’Enter food type (e.g., carbs, protein)
  • β€’Enter food quantity and calorie amount (Manual calculation required)
  • β€’Save, updating the daily calorie total.

Key Capabilities

  • β€’Basic manual entry for meals and workouts.
  • β€’Create simple reusable meal templates (e.g., "Daily Coffee").
  • β€’Basic progress overview and daily summary (Calories In vs. Out).

Key Feature Deep Dive

Understanding the difference between manual and premium tracking capabilities. Use the toggle below to compare the effort required for meal logging across tiers.

Meal Tracking: Manual vs. AI

Manual (Free) AI (Premium)
Goal: Log "1 bowl of Spaghetti Bolognese"

Friction Level: HIGH ⚠️

1. Name: Type "Spaghetti Bolognese"
2. Type: Type "Carb, Meat, Sauce"
3. Calories: Manual Search/Estimate (e.g., 400 cal)

Business Model & Monetization Strategy

The FYTHUB model is built on shared success. The visualizations below detail the revenue structure and the value of the Trainer Marketplace.

Trainer Revenue Share

Percentage of subscription revenue retained by the Trainer vs. FYTHUB.

The Trainer Marketplace

The Marketplace allows trainers to publish "plan packages" (e.g., 8-week Strength and Nutrition programs) that any FYTHUB user can subscribe to, generating a passive income stream for the trainer.

  • β€’Passive Income: Plans sold to users not in a direct coaching program.
  • β€’Quality Control: Admins approve all public plans before listing.
  • β€’Scalability: Allows trainers to monetize content globally, expanding reach beyond 1:1 sessions.

Technical Strategy: Backend Decision

A critical decision was made to prioritize Supabase (PostgreSQL) over Firebase (NoSQL) to ensure long-term cost predictability, handle complex trainer-client relationships, and support robust search capabilities.

Key Architectural Advantage

Comparison of critical factors for the FYTHUB business model.

Why Supabase (SQL) is Superior

  • β€’Cost Predictability: Supabase offers fixed tiers, mitigating the "Pay-per-Read" volatility of Firebase. This is crucial given the high-volume logging by free users.
  • β€’Relational Data: The Trainer (1) to Client (Many) to Log (Many) structure is natively handled by SQL, avoiding complex, costly, and error-prone NoSQL duplication.
  • β€’Native Search: PostgreSQL has superior built-in Full Text Search, eliminating the need for expensive third-party search tools (like Algolia) for the meal/exercise database lookup.
  • β€’Less Lock-in: Based on open-source PostgreSQL, providing future flexibility for migration or hybrid solutions.

FYTHUB App Backend Comparison

A comprehensive analysis of backend architecture decisions. Compare Supabase and Firebase across multiple dimensions to understand why Supabase is the optimal choice for FYTHUB's scalability and cost requirements.

Backend Selection Criteria

Table View Card View
Criteria πŸ—„οΈ Supabase πŸ”₯ Firebase
Cost Model Fixed Tiers Pay-Per-Read
Relational Data Support Native Requires Denormalization
Full-Text Search Built-in Third-Party Required
Lock-In Risk Low (Open Source) High (Proprietary)
Scalability Excellent Good (Costly)
Real-Time Capabilities Supported Excellent
Authentication Flexible Integrated

Cost Projection Analysis

Supabase Monthly Estimate

Base Plan $25
Storage (100GB) $100
Bandwidth $50
Total ~$175

Firebase Monthly Estimate*

Read Operations (1M/month) $600
Write Operations (500K/month) $200
Storage (100GB) $300
Total ~$1,100

*Assumes moderate FYTHUB usage with free users generating significant read volume

πŸ“„

Full Document

Embedded View Download Link

Embedded PDF viewer - Use controls in the document to zoom, navigate, and search