Expo Data Fetching
Networking for Expo apps — fetch, React Query, SWR, four screen states, offline, SecureStore
- What
- Networking for Expo apps — fetch, React Query, SWR, four screen states, offline, SecureStore
- Cost
- Free
- Needs
- an Expo project; an API to call; expo-secure-store for token storage
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — the official networking skill for Expo apps: use `expo/fetch` over axios, wire up TanStack Query (React Query) or SWR with caching, design all four screen states (loading, error, empty, content — where loading ≠ empty), gate UI on hydration to avoid cold-start flashes, keep cached content visible during refetch failures, preserve form drafts on failed saves, store auth tokens in `expo-secure-store` (never AsyncStorage), implement token refresh, detect network status with NetInfo for offline-first React Query, cancel requests with AbortController, and configure API URLs per environment with `EXPO_PUBLIC_` variables — while warning that secrets never belong in client-exposed vars. Decision tree included for choosing fetch vs React Query vs SWR. Companion to the repo's expo-ui and expo-router skills in this catalog. By @expo, listed here with credit to its creator. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: an Expo project; an API to call; expo-secure-store for token storage Install "Expo Data Fetching" for me. Networking for Expo apps — fetch, React Query, SWR, four screen states, offline support, SecureStore auth Repository: https://github.com/expo/skills/blob/main/plugins/expo/skills/expo-data-fetching/SKILL.md 1. Fetch the SKILL.md file for the expo-skills-expo-data-fetching skill from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "expo-skills-expo-data-fetching". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.