Skip to content
Vidivo Docs

Changelog

V1.0 --- Launch Release

Section titled “V1.0 --- Launch Release”

Phase 3: Payment UX (Current)

Section titled “Phase 3: Payment UX (Current)”
  • Date range filtering on all payment and payout list endpoints
  • Data export in CSV, XLSX, and PDF formats for payments and payouts
  • Invoice generation with PDF invoices auto-generated on payment capture, stored in Cloudflare R2
  • Payment notifications with in-app notifications and email receipts on payment capture
  • Admin payments page with full payments management, filters, export, and invoice download
  • Web app date pickers and export components for payment and payout history

Phase 2: Features

Section titled “Phase 2: Features”
  • Call history status filter for filtering by waiting, ringing, active, completed, missed, failed
  • Payment model simplified to platform-managed payouts (hosts paid via Stripe Payouts)
  • Follow system allowing users to follow hosts, with host broadcast to followers
  • Real-time chat with WebSocket messaging and file sending; hosts message anytime, users only during active calls
  • Notification enhancements with FCM push delivery via Firebase
  • Support ticket system with in-app tickets and threaded messages

Phase 1: Foundation

Section titled “Phase 1: Foundation”
  • All 12 microservices scaffolded with Clean Architecture
  • Shared packages (auth, config, errors, response, middleware, etc.)
  • 18 database migrations
  • GORM models for all 16+ tables
  • Web app scaffold (React 19 + Vite 7 + Tailwind CSS 4)
  • Admin panel scaffold (React 19 + Vite)
  • TURN server (pion/turn v4 with HMAC auth)
  • Docker dev environment with Traefik, PostgreSQL, Redis, Prometheus, Grafana

Roadmap

Section titled “Roadmap”

Features planned for upcoming releases:

  • iOS native app (Swift + SwiftUI)
  • Android native app (Kotlin + Jetpack Compose)
  • Screen sharing via WebRTC getDisplayMedia()
  • Call recording (opt-in, with both party consent)
  • Group calls (SFU-based, for 3+ participants)
  • Whiteboard (via WebRTC data channels)
  • Two-factor authentication (TOTP/Passkeys)
  • Public API for integrations