Mobile app deep links

Deep links connect public moschee.io content to the browser and, where the deployed app configuration supports it, the official moschee.io mobile app. They are generated by public pages and notification payloads; there is no general dashboard form for manually inventing a deep-link URL.

Supported public paths

The application contains these public link families:

• Live rooms: /open/room/[roomName]
• Events: /open/event/[organizationId]/[eventId]
• News: /open/news/[organizationId]/[articleId]
• Restream output: /open/egress/[token]
• Donation pages: /donate/[slug] and /donate/[slug]/[id]

The app-facing equivalents under /app/open and /app/donate are used by the application’s own open flows. The exact final URL can include encoded identifiers, so copy a link from the public page or notification rather than constructing an identifier by hand.

How a visitor uses a link

1. Publish the event, news item, donation project, or live room.
2. Copy the public link from the relevant page or share action.
3. Open it on a mobile device.
4. Confirm that the browser fallback renders correctly.
5. If the official app is installed and the deployed smart-link configuration matches, confirm that the app handoff opens the same content.
6. Test the link while signed out, because public visitors and app users may not have dashboard access.

For a live room, the open page can show a waiting state before the room starts, the browser player when it is live, or a not-found state for an invalid room.

Use deep links in notifications

When configuring live-room or organization notifications, use the application-generated room or content link. Validate the link with the same audience that will receive it:

• Test a public event with no dashboard session.
• Test a donation link with the correct organization host.
• Test a live-room link before the broadcast and while the broadcast is active.
• Test an app notification on both a device with the app and a device using browser fallback.

Do not put private dashboard URLs in public notifications.

Troubleshooting

• A link opens the wrong content: copy a fresh link and check the organization or item identifier.
• The app does not open: confirm the official app is installed and that the deployed smart-link configuration is current; the browser route remains the fallback.
• A room is waiting: the room is scheduled or not live yet.
• A donation link fails: confirm the project is public and use the organization’s public host.
• A restream link fails: verify that the egress token is current and that the destination is still running.

Store URLs and app handoff behavior depend on the deployed mobile app configuration. Verify the current App Store and Google Play destinations before publishing them in a website footer, poster, or campaign.