Overview
N+One runs in your browser as a Progressive Web App (PWA). You can add it to your device home screen and use parts of the app offline. This article explains what to expect, how to install the app, simple caching behavior (service worker basics), and which features require a network connection.
Note: The app shows “Beta” in the header. Some features (AI chat, new sync) require an internet connection.
Install the PWA (short guide)
We keep a full, device-specific guide at /install-pwa. Use that for screenshots and step-by-step help. These short steps cover the common flows:
- Android (Chrome): open https://www.nplusone.app in Chrome, open the browser menu, then choose “Add to Home screen.”
- iOS (Safari): open https://www.nplusone.app in Safari, tap the share button, then choose “Add to Home Screen.”
After adding the app you can launch N+One from your home screen like a native app. The PWA gives a fullscreen experience and keeps a local cache of some assets and pages so the app can work when you’re offline.
What “offline” means in N+One
- /offline — If the app detects you’re offline, it will show the /offline page. That page explains which pages are uncached and suggests next steps.
- Previously viewed pages and assets — The PWA caches core UI files and pages you’ve already opened. If you lose network access, those cached pages may still load and let you read previously viewed content.
- Limited write and sync — Creating or editing items that need server validation (new sign-ins, sync, AI requests) won’t complete while offline. Actions are queued only when the app explicitly shows an offline queue; otherwise retry when you’re back online.
In short: some read-only screens and the app shell work from cache; anything that requires fresh data or server processing needs a network.
Which features require a network connection
The following always require an internet connection:
- AI Coach (/coach) — the conversational coach needs network access to generate responses.
- Any new sync with device integrations — syncing activities or reading fresh data from Strava, Wahoo, WHOOP, Garmin requires network access and OAuth flows. See Device Integrations at /settings/integrations.
- Uploading planned workouts to external devices or services (Garmin, Wahoo) — these actions require the app to talk to external APIs.
- Signing in or signing up (/auth/login and /auth/signup) and onboarding — authentication and the onboarding chat both need a live connection.
If you try one of these while offline the app will show an error or the /offline page; retry when you have a connection.
Service worker & caching behavior — plain language
N+One uses a service worker (a small script the browser runs) to speed up the app and provide offline capability. Here’s what to expect without technical detail:
- The service worker caches core app files (HTML, CSS, JavaScript) so the app opens quickly and can show previously visited pages when you lose network.
- Pages you open while online are more likely to be available later when you’re offline. If you know you'll be without internet, open the pages you want (for example, a planned workout or a knowledge-base article) while you still have a connection.
- Not everything is cached. Dynamic content that depends on current server data — recent syncs, live readiness scores, AI chat — will not display fresh values while offline.
- Service worker updates can be applied in the background. If the app has been updated, closing and reopening the app or refreshing the page brings the new version into use.
If you need content offline regularly: open the app and the specific pages you want while online, then close the app. This increases the chance those pages are available from cache later.
Practical tips and troubleshooting
- Open key pages before you leave signal range: calendar weeks in /training, a workout detail page (/training/[id]), or a knowledge-base article.
- If the app shows /onboarding it’s because your profile isn’t complete. Onboarding requires network—complete it while online to get full offline behavior later.
- If something looks stale after reconnecting, refresh the app or reopen it from the home screen to fetch fresh data.
- Avoid clearing browser site data if you want cached pages to remain available.
- If the PWA install option doesn’t appear, go to /install-pwa for device-specific instructions and common fixes.
When to expect an error vs. graceful offline behavior
- Graceful (cached) behavior: reading previously viewed dashboards, viewing cached planned workouts or help articles.
- Error or blocked action: starting an AI chat, syncing new ride data from Strava/Garmin, connecting a new integration, or uploading a workout to a device.
The app will point you to /offline when a network is required but not present.
Links and where to get help
- Install guide: /install-pwa
- Offline info: /offline
- Device integration settings: /settings/integrations
- AI Coach (requires network): /coach
- Help & Support (faqs and contact form): /settings/support
- General FAQ: /faq
If you still need help after trying these steps, open Settings → Help & Support (/settings/support) from inside the app and send us details about your device, browser, and what you were trying to do.
Quick summary
- Install N+One from your browser to add a home-screen app experience.
- Previously viewed pages and core UI assets can work from cache; live features require a connection.
- AI Coach, syncing, authentication, and uploads always need network.
- For full instructions and device-specific troubleshooting see /install-pwa and /offline.
Keep riding — and remember: the most important ride is always the next one.
