Novagora on mobile and on the web

One account, two surfaces. The mobile app for iOS and Android is the primary one; the web app runs in any current browser. Almost everything is in both.

What differs#

The web shows your plan, entitlements, credit balance, and full history, and lets you gift credits — it just does not sell plans or credits. Spending credits you already hold works on both: you can promote a post, article, or event, and stop a running promotion, in the app or on the web.

Everything else — feeds, Spaces, posts, articles, chat, events, tasks, notes, polls, files, moderation, settings — is on both.

Permissions the app asks for#

The app asks for a permission the first time you use the feature that needs it, never at startup, and each one is optional:

If you refused one and change your mind, grant it in your device's own settings. Where Novagora can tell that a permission is switched off at the system level, it says so and offers to open those settings rather than failing quietly.

Links that open the app#

A Novagora link tapped on a phone with the app installed opens in the app; otherwise it opens in the browser. Both are supported destinations — a link never dead-ends because the app is missing.

Links resolve for posts, articles, events, polls, tasks, notes, chat conversations, profiles, Spaces, invitations, notifications, your account standing, and email verification.

A link is not a permission. Opening one that points at something you cannot see tells you it is not available to you; it does not let you in.

Working offline#

The app keeps what it has already loaded, so an interrupted connection is not a blank screen.

• You're offline. Some content may be out of date. — you are reading what was loaded before.
• You're offline. Connect to load content. — there was nothing cached for this screen.
• You're offline. Your action is waiting to be sent. — what you did is queued and goes out when the connection returns.
• Pulling to refresh while offline says it did not refresh, rather than pretending it did.

The web app keeps what it has loaded in the same way, and says so in its own words.

Documentation and versions#

This documentation is published per release, and a published version never changes afterwards. Help opened from inside the app links to the documentation for the version you are running — so an install you have not updated in months describes the build in your hands, not the newest one.

The version selector on any page moves you between releases, staying on the same page where that release has it and saying so where it does not. Older releases stay readable and are marked as archived.

A correction to a released page lands in the next version rather than being edited into a shipped one.

Every release also has a page describing what changed in it, listed newest first and marked as current, superseded, archived, or withdrawn. Each one groups its changes and links to the documentation frozen for that same version, and never changes after it is published. In the app, Settings names the version you are running and opens that version's notes — carried inside the app, so they read the same with no connection.

Known limitations in this release#

• Buying a plan or credits is mobile-only. There is no way to buy a plan or a credit pack on the web.
• The web sends no push notifications. Use the app for those.