← All work
Travel & experiences

Conecta Puerto Vallarta

From discovering an experience to planning a reservation. One connected journey.

Product in development · test paymentsNext.js / React / TypeScript / Supabase / Stripe TEST
Conecta Puerto Vallarta
Actual Conecta interface · local preview · test payments
Actual Conecta interface · local preview · test payments
Context

A system, in context.

A tourism platform for Puerto Vallarta, with experience discovery, reservation planning and an operational back office.

The challenge

The workflow behind the screen.

A booking journey needs more than a beautiful catalog: dates, travelers, availability confirmation and payment state must remain connected.

Experience detail and reservation information
Experience detail and reservation information
Approach

From rules to interfaces.

Separate the public, statically rendered experience from authenticated account workflows. Keep monetary rules in a domain layer and reconcile test payments through server-side functions.

My role

Product and frontend implementation, with booking workflows and backend integration represented in the repository.

Capabilities
  • 01Experience catalog and detail routes
  • 02Date and traveler booking intent
  • 03Account and operational panel
  • 04Stripe test checkout and reconciliation
  • 05WhatsApp follow-up and reservation lookup
Next.jsReactTypeScriptSupabaseStripe TEST
Secondary conceptual workflow
01

Discover

02

Plan

03

Confirm

04

Track

What changed

The capability this version adds.

A visitor can move from the catalog to a reservation intent with dates, travelers and a visible test-payment state. Live payments and commercial adoption are not claimed.

Verified scope

The repository implements the catalog, booking intent, account shells and test-payment infrastructure. Live payments are disabled; catalog fixtures are marked as demo. No revenue or adoption claim is made.

Original schematic below. Not a production screenshot. Payment integration is test-only.

Engineering decision
Payment success and confirmed availability are different states. The interface must communicate both explicitly.
A similar challenge?

Running a booking-based business?

Let’s explore your workflow ↗WhatsApp ↗
Explore another systemOrders & billing ↗Healthcare platforms ↗