Sapeans

Your communities, wherever participation happens.

Use responsive web, installable community experiences, push controls, and the native app surfaces that are currently implemented and available.

Mobile participation should not become a different product.

People move between discovery, profiles, feeds, events, messages, tasks, learning, Library content, and community administration. Sapeans treats the current responsive website as the source of truth, then uses installed web and native platform adaptations for safe areas, keyboards, permissions, sharing, files, notifications, and application lifecycle where necessary.

What it makes possible

Use the responsive web experience

Public discovery, profiles, community routes, feeds, Spaces, Members, Events, Library, tools, and admin surfaces adapt through the current responsive breakpoints and established mobile shell behavior.

Install an eligible community

Supported Android and iPhone browser paths can expose install guidance or a browser install prompt. Installed community identity, icons, metadata, and route handling are synchronized by the current PWA context.

Manage device notifications

Delivery preferences expose push state, permission, registration, and pause behavior for the current device. App badges and service-worker communication remain dependent on browser and operating-system support.

Keep familiar mobile navigation

The community mobile shell uses the established header, safe-area handling, contextual search, route-aware bottom dock, and eligible quick composer. Fullscreen and detail routes hide shell elements according to the same route flags.

Follow native parity, not reinvention

The Expo application implements a growing set of public, profile, community, Library, Course, Task, Marketplace, Promotions, Payments, and administrative routes. Its design contract requires website parity and documents remaining verification work instead of claiming universal completion.

How it works

Open

Use Sapeans in a mobile browser with the responsive public or community layout.

Install when supported

Follow the current browser prompt or device-specific install guidance for an eligible community.

Choose delivery

Enable or pause push on the current device when configuration and permission allow it.

Continue consistently

Return through deep links and notifications to the same community identity and access model.

Controls for community builders

PWA identity

Community name, logo, colors, manifest metadata, and installed routing derive from the current community branding and host context.

Responsive parity

Mobile web retains all relevant member and admin features rather than silently hiding controls because of width.

Native change control

Any native visual or behavioral difference must be documented and traced to the current website or an explicitly allowed operating-system adaptation.

Plans, permissions, and availability

Responsive web is the authoritative mobile experience. Installability and push depend on browser, device, configuration, permission, and community context. This page does not claim public App Store or Play Store availability unless verified at release time.

Frequently asked questions

Can I install a Sapeans community like an app?

On supported browsers and eligible community routes, Sapeans can provide a browser prompt or device-specific install guidance. Availability varies by device and browser.

Do push notifications always work?

Push requires platform configuration, browser or installed-app support, user permission, a registered token, and an enabled device preference.

Is Sapeans available in public app stores?

This page makes no store-availability claim unless it is verified at the time of release. The repository’s native implementation status is not the same as public distribution.

Does the native app use a different design?

No intentional redesign is authorised. The native app follows the responsive website as its source of truth, with only documented operating-system adaptations.