Meridian
Product roadmap

Meridian

A hospitality services demo, moving toward a real product

A practical view of what is in the project today, what is still a demonstration, and the steps needed before Meridian can support real hotel or cruise operations.

01 / Today

What is in the project

  • Home, demo dashboard, dining, experiences, entertainment, shop, concierge, IPTV, spa and multimedia pages.
  • ARIA with predefined answers and a multilingual interface; voice features use browser APIs.
  • A Room Service demo with a cart and payload preview; orders are not sent to an external system.
  • A PWA manifest and QR codes generated in the interface.
  • Sample content for restaurants, experiences, products and IPTV channels.

There is no application backend, persistent order or booking storage, guest authentication, PMS integration, generative AI, or offline service worker. Displayed data and counters are not operational metrics.

02 / Next steps

From demo to dependable service

Make the demo clear and consistent

  • Clearly distinguish sample content from real data.
  • Remove unverified statistics, availability, prices and operational promises from text and interfaces.
  • Keep the documentation aligned with the implemented features.
  • Check navigation, accessibility and layouts on supported devices.

Connect ARIA to real services

  • Define a backend for AI requests; never expose keys or secrets in the frontend.
  • Ground prompts and context in data that is actually available.
  • Handle service errors and outages explicitly.
  • Consider external voice services only if needed; browser speech synthesis and recognition are already present.

Add a backend and persistent data

  • Define APIs and a database for guests, content, orders and bookings.
  • Implement authentication and authorization before handling personal or cabin data.
  • Save requests and make them available for follow-up, with clear states and error handling.
  • Define staff roles and needs before building an operations dashboard.

Integrate hospitality systems

  • Select systems for a pilot based on real project needs and vendor documentation.
  • Build and test integrations for orders, bookings and staff requests.
  • Do not describe partners or integrations as available until implemented and verified.

Prepare for on-site and kiosk use

  • Evaluate kiosk use and installation on real devices.
  • Identify which content must work offline and implement an appropriate strategy.
  • Add notifications or synchronization only when the required backend services exist.

Evaluate how to scale

  • Consider multi-property configuration and white-labeling after validating a real pilot.
  • Measure operational benefits during a pilot; no impact results or percentages have been verified yet.
  • Consider a native app only if the requirements cannot be met by the PWA.
03 / Definition of done

When a feature is complete

  • The flow is implemented, not just a screen or sample data.
  • Integrations have been tested with their target systems.
  • Errors, limitations and dependencies are documented.
  • Numbers, outcomes and claims are supported by measured data.