Sample project · architecture

FerryLog runs with no server

Three small files and one data file show the next 3 ferry departures. Nothing leaves the phone.

ferrylog sample · src/app.js · src/board.js · src/schedule.json

opens pageasks next 3reads 11 sailingsPhonebrowserBoard UIapp.jsNext-3 logicboard.jsScheduleschedule.json
Fig. 1Every request stays on the device: the schedule is a static file, not an API.

Loop

The board re-renders every 30 seconds

Board UI calls the next-3 logic once on load, then again every 30 s. The countdown stays honest without a server clock or a push channel. Each render replaces the list; a sailing that leaves drops off, and the next one enters.

After the last sailing (20:00), the list is empty and the board says so: “No more sailings today.”

Gap

Offline is claimed, not yet built

The plan lists a service worker as step 3. It is not in the sample. The page works offline only after a first online load caches nothing on purpose — today, a cold offline open fails. The recap page scores this as the one open item.

Sources

sample-project/README.md · sample-project/src/app.js:8 · sample-project/src/board.js · sample-project/src/schedule.json