Path 94 · The offline fieldbook · Intermediate
Explain what is available when the network is not.
A guided, practical route through pwa offline design.
What you will be able to do
Build a small local offline-reference prototype with a scoped service worker, a cache list and an update test plan.
Plan about 11h 15m in total. Reading and practice are editorial estimates; video runtimes come from public provider metadata. Your pace will vary.
Table of Contents
Before you begin
Check your starting point
What you need
Basic HTML and JavaScript. Serve the project on localhost or HTTPS; opening file:// does not provide the required service-worker context.
The selected public provider lessons are free to view. The original case can be completed with paper, a text editor or freely available local tools. Paid exams, certificates, subscriptions and optional provider software are not required for this project.
Completing this Coursya path does not award a provider certificate. Any provider assessment, account requirement or credential must be checked separately on its official page.
Three readiness questions
Can a first-ever offline visit fetch an uncached lesson?
No.
Does a service-worker file prove offline behavior?
No. Test installation and an actual offline reload.
Should this worker control the whole production site?
No. Keep scope inside the project folder.
Use a workable pace
At 5 hours per week, allow about 3 weeks. Start with Stage 1, continue in order and reserve 2h 30m for the capstone. If a gate fails, use its repair step before advancing. At another weekly budget, divide 675 estimated minutes by your available weekly minutes and round up.
Keep a small evidence folder. A checked box means you reviewed your output; it is not a certificate or proof that a provider lesson was watched.
The working case
The offline availability sequence
A fictional fieldbook contains one static lesson and a checklist. Cache only the application shell and this public lesson. Do not cache private account responses or arbitrary external pages. The first visit still needs the files to load before offline availability can be tested.
| Resource | Offline policy |
|---|---|
| index.html | precache |
| app.js | precache |
| styles.css | precache |
| Private account data | not part of this app |

The table and explanations preserve the essential case information when the diagram is unavailable.
Your route
Five outputs, then a final handoff
- 01Define the offline promiseOffline specification
About 1h 30m including assigned learning and practice. - 02Understand worker lifecycle and scopeWorker source and scope record
About 2h 15m including assigned learning and practice. - 03Choose a serving strategyServing behavior
About 2h including assigned learning and practice. - 04Plan updates and cleanupUpdate test plan
About 1h 55m including assigned learning and practice. - 05Verify and describe the resultOffline evidence log
About 1h 5m including assigned learning and practice. - FINALCapstone reviewCombine the evidence into one inspectable handoff.
About 2h 30m.
0 of 6 outputs checked. JavaScript adds browser-only progress saving.
The complete lesson and all downloads remain available. Use the printable project workbook to track your progress.
Use the minimum useful source material
The courses behind this route
Google Learn PWA: Free Progressive Web Apps Course
The existing web.dev PWA course covers service workers, caching, serving and updates used in this bounded example.
Selected material only; this path does not claim completion of the entire provider course.
Course publication and selected public lesson metadata were checked on 13 October 2026. This is not a claim of full video playback, provider-course completion or permanent availability. Recheck the linked source if a lesson changes.
Learn, make, inspect
The five-stage workshop
Define the offline promise
Video 0m · reading budget 35m · original practice about 55m.
Start with a narrow offline experience and tell users its limits. A static reference is simpler than synchronizing edits across devices. Define which assets are available after a successful first load and which are not. The exercise stores no personal account data and makes no background network changes.
Assigned reading
Google Learn PWA: Free Progressive Web Apps Course: Foundations and assets and data.
Use the named provider navigation sections. Editorial reading budget for the named public material; not a verified completion duration
Do the work
Write the offline contract and asset inventory.
Save this output
Offline specification
Pass the review gate
The contract distinguishes first load from a later offline visit.
If you need another attempt
Remove claims that an uncached page can work without a network.
Understand worker lifecycle and scope
Video 0m · reading budget 50m · original practice about 1h 25m.
A service worker is registered for a scope and has an installation and activation lifecycle. Cache a short explicit asset list and use a versioned cache name. Do not register the worker at a broader scope than needed. Keep the example isolated so it cannot alter unrelated pages during local testing.
Assigned reading
Google Learn PWA: Free Progressive Web Apps Course: Service workers and caching.
Use the named provider navigation sections. Editorial reading budget for the named public material; not a verified completion duration
Do the work
Register the worker from the project folder and inspect its scope.
Save this output
Worker source and scope record
Pass the review gate
The worker controls only the local project path.
If you need another attempt
Use relative registration and avoid a site-root scope override.
Choose a serving strategy
Video 0m · reading budget 40m · original practice about 1h 20m.
For this static shell, a cache-first strategy is easy to inspect, with a network fallback for uncached same-origin GET requests. Do not cache every response indiscriminately. Explain how a new version becomes visible and what happens if an asset was not cached successfully. A strategy is a trade-off, not a universal best practice.
Assigned reading
Google Learn PWA: Free Progressive Web Apps Course: Serving.
Use the named provider navigation sections. Editorial reading budget for the named public material; not a verified completion duration
Do the work
Implement the bounded fetch handler and an offline status message.
Save this output
Serving behavior
Pass the review gate
Unsupported requests are not silently stored in the project cache.
If you need another attempt
Filter method and origin before handling a request.
Plan updates and cleanup
Video 0m · reading budget 40m · original practice about 1h 15m.
An updated worker can wait while an older page remains controlled. Test the lifecycle instead of forcing reloads without understanding state. Remove only caches owned by this project and preserve unrelated browser data. A cache name prefix makes that boundary explicit. The example is not a synchronization system.
Assigned reading
Google Learn PWA: Free Progressive Web Apps Course: Update and tools and debug.
Use the named provider navigation sections. Editorial reading budget for the named public material; not a verified completion duration
Do the work
Change one lesson line and rehearse the version-update steps.
Save this output
Update test plan
Pass the review gate
Cleanup targets only the project cache prefix.
If you need another attempt
Do not delete all origin caches as a shortcut.
Verify and describe the result
Video 0m · reading budget 0m · original practice about 1h 5m.
A meaningful offline test loads online, confirms worker control, disables the network and reloads. Record actual observations and any browser restrictions. Local success does not establish installability on every platform. Keep native-site review separate from this standalone prototype and do not claim a live Coursya PWA deployment.
Original application stage. Use your preceding outputs and the supplied case; there is no additional required provider lesson.
Do the work
Run the online-to-offline checklist and record the browser used.
Save this output
Offline evidence log
Pass the review gate
The log distinguishes prepared source, local test and production deployment.
If you need another attempt
Leave unperformed platform checks explicitly pending.
Make the result inspectable
Your final project
Deliver the app files, service worker, cache inventory, lifecycle notes and actual local offline test log. Demonstrate cleanup of only the project’s own cache during a version change.
The ZIP includes synthetic input data, a project workbook, worked reference, evidence log, scoring rubric and case-specific materials. Code projects include source and clearly stated local execution requirements.
Use one consistent rubric
| Criterion | Maximum | Evidence |
|---|---|---|
| Evidence and correctness | 30 | Calculations, source use and results match the supplied case; limitations are honest. |
| Required artifacts | 30 | All five stage outputs and the capstone handoff are present and inspectable. |
| Reasoning and decisions | 20 | Choices, assumptions, alternatives and the case-specific critical condition are explained. |
| Reproducibility | 10 | A reviewer can follow the stated steps and distinguish expected from observed results. |
| Clear communication | 10 | Labels, units, structure and evidence references make the work easy to review. |
Score at least 80/100, supply every required artifact, and satisfy the path-specific critical condition. Rework missing evidence before marking complete.
The critical condition
Worker scope and cache cleanup stay inside the project, and unperformed offline tests are not claimed.
Compare with a worked reference
Only the three public shell resources are precached. After a successful online installation and controlled reload, the cached lesson should be available offline. That expected behavior must be confirmed in a real browser; it is not implied merely by the presence of sw.js.
Know the boundary
This is a local static offline prototype, not a production PWA, cross-device sync service or universal installability guarantee.
Questions before you finish
Do I need to finish every source course?
No. This path names selected lessons or reading sections. Complete the full provider course only if it supports your wider goal. The path does not claim equivalence to that course.
How do I know when to advance?
Use the output and review gate in each stage. If evidence is missing or a result conflicts with the case, follow the repair step and retry before advancing.
Can I do the project without paid software?
The selected public provider lessons are free to view. The original case can be completed with paper, a text editor or freely available local tools. Paid exams, certificates, subscriptions and optional provider software are not required for this project.
What does my checklist prove?
It records your own review in this browser only. It does not verify viewing, skill, a provider credential or a real-world deployment.
What if a lesson or tool changes?
Use the linked course and provider page to inspect current availability. Record the change and revisit the relevant assignment; do not invent a replacement lesson or claim an unavailable activity was completed.
Questions & discussion
Share a useful question or correction. Comments appear after moderation. Please avoid personal or sensitive information.