Hayya

The Hayya Ecosystem

Hayya is structured as a connected product ecosystem rather than a single application.

Together, these components allow Hayya to operate as both a user-facing product and a platform that other applications can build upon.

Identity Across the Ecosystem

Selected Hayya experiences integrate with Moonlight for authentication and Single Sign-On.

Users can sign in to:

• Hayya App
• Hayya for Masjid

using their Moonlight identity.

This reduces the need for separate account systems across connected products and creates a more consistent identity experience throughout the wider ecosystem.

One identity across connected experiences.

Instead of each application maintaining its own isolated authentication layer, Moonlight acts as the shared identity foundation behind supported Hayya products.

Suggested image: Simple architecture diagram showing Moonlight → Hayya App and Moonlight → Hayya for Masjid through SSO / OAuth authentication.

Hayya API

The Hayya API acts as the shared service backbone behind the ecosystem.

It centralizes:

business rules · validation · authentication · authorization · data contracts

The API is used internally by Hayya products, but it is not limited to Hayya itself.

External developers can also integrate with the Hayya API to build their own applications, services, or community tools on top of supported Hayya data and functionality.

This creates two roles for the API:

Internal Platform Layer

Powering first-party Hayya experiences such as:

• Hayya Web
• Hayya App
• Hayya for Masjid
• Future Hayya products

Developer Platform

Allowing third-party developers to:

• Consume supported Hayya endpoints
• Build independent applications using Hayya services
• Integrate Islamic utilities into their own products
• Extend the Hayya ecosystem without recreating the same backend functionality

Suggested image: API documentation or developer dashboard with an architecture diagram connecting third-party apps to Hayya API.

Open by Design

Hayya is designed as more than a collection of first-party applications.

The platform can support three different layers:

Users interact with Hayya through web, mobile, and mosque displays.

Moonlight provides a shared identity layer across supported Hayya experiences.

Developers can use the Hayya API to build applications beyond Hayya's own interfaces.

This architecture allows the ecosystem to grow without requiring every new product to rebuild authentication, business logic, and core services from scratch.

One Product, Multiple Contexts

What makes Hayya interesting is not simply the number of applications within the project.

It is how the same ecosystem adapts across different contexts.

A user might check prayer times through the Hayya App.

The same identity can be used through Moonlight to access other supported Hayya experiences.

A mosque administrator can manage a Hayya for Masjid display.

And an external developer can build an entirely different application using the Hayya API.

This creates a broader platform model:

One ecosystem. Multiple experiences. A shared identity and platform underneath.

Why Hayya

Hayya started with a simple question:

What if essential Muslim digital experiences could live within one connected ecosystem?

The answer evolved beyond an individual application.

Today, Hayya can serve:

individuals through personal Muslim tools, communities through mosque displays, connected products through Moonlight identity, and developers through an open API platform.

The result is an ecosystem where first-party products and third-party applications can share the same underlying services while serving completely different user experiences.

Hayya

Your Muslim Companion. Built for people, communities, and the ecosystem around them.