ux-network
Skill21 starsChanged 5 months agoMITView on GitHub
Network and connectivity UX: offline mode, slow connection resilience, connection error states, background sync, caching strategy, and graceful degradation. Use when designing or reviewing how an app behaves under poor or absent network conditions.
In this repository17 other files it gives its agents.
- ux-accessibilitySkill
- ux-ai-automationSkill
- ux-contentSkill
- ux-error-handlingSkill
- ux-formsSkill
- ux-generalSkill
- ux-help-onboardingSkill
- ux-information-architectureSkill
- ux-navigationSkill
- ux-notificationsSkill
- ux-reviewSkill
- ux-safety-privacySkill
- ux-searchSkill
- ux-settingsSkill
- ux-user-accountSkill
- ux-utilitySkill
- ux-visual-designSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 32
Optimistic UI: Update the UI immediately to show the expected outcome, then sync in the background.
- Distinctive: line 83
When applying this checklist to a screen, flow, or codebase:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Network and Connectivity UX
Network conditions are unpredictable. An app that only works on fast Wi-Fi is not a reliable product. Design for the worst connection and fast connections will take care of themselves.
Checklist
| Item | Guidance |
| Performance on slow connections | Critical content loads first. Images lazy-load. API payloads are compressed. |
| No internet error | Inline message with a retry button. Never an empty screen with no explanation. |
| Network switch resilience | App does not crash or disconnect when switching from Wi-Fi to mobile data. |
| Offline mode | Cached content is displayed. Writes are queued and flushed when connection returns. |
| Background data sync | Data syncs in background on Wi-Fi by default. User can enable sync over mobile data. |
Offline-First Architecture
Optimistic UI: Update the UI immediately to show the expected outcome, then sync in the background. If the sync fails, show an undo option. This approach makes the app feel fast regardless of network speed.
Cache strategies:
- Stale-while-revalidate: Show cached content immediately, refresh in the background.
- Cache-first: Always show the cache, refresh only on explicit pull-to-refresh.
- Network-first: Try the network first, fall back to cache on failure.
Sync queue: Store pending writes locally and flush them when connectivity returns. Show a clear sync status indicator so users know their changes are queued and will be saved.
Error State Patterns
| Scenario | UI Pattern |
| No internet at launch | Full-screen message with an illustration and a Retry button |
| Lost internet mid-use | Top banner: "No connection — working offline" |
| Slow connection | Skeleton screens instead of spinners |
| Server error (5xx) | "Something went wrong on our end." with a Retry button |
| Request timeout | "Taking longer than usual." with Keep waiting and Cancel options |
| Partial failure | Load what worked, show an inline error for what failed |
Performance Targets
Web (Core Web Vitals)
| Metric | Target |
| Largest Contentful Paint (LCP) | Under 2.5 seconds |
| Interaction to Next Paint (INP) | Under 200ms |
| Cumulative Layout Shift (CLS) | Under 0.1 |
Mobile app
| Metric | Target |
| Cold start to interactive | Under 2 seconds |
| API response (P95) | Under 500ms |
| Offline cache hit | Under 100ms |
| Scrolling | No dropped frames at the display's refresh rate |
How to Review
When applying this checklist to a screen, flow, or codebase:
- Go through every checklist item and mark it Pass, Fail, or N/A — never skip items silently.
- Cite specific evidence for each finding: the screen, component, file, or line it applies to.
- Tag each failure with a severity: Blocker (breaks the experience), Major (hurts usability), or Minor (polish).
- End the review with the top 3 recommended fixes, ranked by user impact.
Related Skills
ux-error-handling— error message writing and retry patternsux-help-onboarding— loading indicators and skeleton screens
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.