BublHub
Event ticketing + community ecosystem (web + mobile + backend)
Overview
BublHub is a platform for organisers to publish events, sell tickets, and build communities that drive repeat attendance. It combines ticketing with a retention layer that helps event brands grow over time.
Problem
Organisers often stitch together multiple tools for promotion, ticketing, attendee management, and community engagement. That creates friction, inconsistent UX, and weak retention loops.
Highlights
- Built the platform end-to-end across mobile, web, and backend workflows
- v1 launched in 2023 as a working ticketing baseline
- v2 started in Sept 2024: redesign, rebrand, and database migration to support richer features
- Migration designed for future portability beyond Appwrite
Timeline
How the project evolved — decisions, migrations, and capability growth.
Built and tested the core journeys early: event creation, browsing, and ticket purchase. The focus was learning what mattered and proving the flow end-to-end.
- Iterated on event structure, profiles, and navigation patterns
- Validated the basic ticketing journey with real usage
- Learned where the data model needed to evolve for the long-term vision
Launched v1 as a working baseline. The aim was a stable ticketing foundation that could be built on, with clear UX and reliable core flows.
- Shipped a usable ticketing baseline and core user journeys
- Improved UX consistency and release readiness
- Established the product direction beyond basic ticketing
Started v2 work to modernise the UI, rebrand the product, and plan the database redesign required to support a more capable platform.
- New UI direction and rebrand work in Figma + Adobe
- Planned the database redesign for richer features and relationships
- Set the portability goal: reduce lock-in and keep migration options open
Ongoing v2 build: migrating from Firebase to Appwrite, redesigning the data model, and building new capability on top of the improved foundations.
- Database migration and redesign: Firebase → Appwrite
- Expanded data model to support features beyond the original ticketing system
- Added clearer workflow boundaries and service structure to keep the system maintainable
- Portability mindset: vendor code stays contained, product logic stays stable
- Payments work: Stripe onboarding and purchase flow hardening
Approach
- Designed user journeys first, then built reusable UI patterns to keep web and mobile consistent
- Rebuilding the UI around a new brand direction so the product feels cohesive and scalable
- Redesigning the data model and migrating from Firebase to Appwrite to reduce lock-in and support a more complex platform
- Keeping portability in mind: vendor-specific code stays contained, product logic stays stable
v2 objective
v2 is a redesign + migration + build-out phase: modernise the UI, rebuild backend foundations, and add richer platform features on top of a more expressive data model — while keeping future portability realistic.
- New UI and rebrand in Figma and the Adobe suite
- Database migration and redesign: Firebase → Appwrite
- More complex data model to support new platform features
- Designed for future migrations beyond Appwrite
Technical overview
The backend direction is to keep product logic stable and keep vendors contained: thin endpoints, services owning domain rules, and adapters wrapping vendor SDK calls.
- Thin endpoints: authenticate, validate, delegate
- Service layer: business rules + orchestration
- Vendor isolation: DB/storage/payments behind small interfaces
- Workflow reliability: state-first flows and idempotency where it matters
Demo
A test-mode purchase flow that mirrors the intended production journey end-to-end.
Future roadmap
The next layer builds retention and organiser capability on top of solid ticketing foundations.
- Organiser tooling: dashboards, comms, and event ops workflows
- Community layer for retention and identity
- Discovery + personalisation improvements
- Operational hardening: monitoring and failure handling
- Performance and release cadence improvements
I build end-to-end: UI that feels intentional, backends that are predictable, and workflows that map to real operations. If you’ve got a role or project in mind, I’m happy to talk.