← All projects

Part 4 of this project

Data Layer

Persist history entries to JSON

Goal for this part

Persist history entries to JSON.

Treat 04-Data-Layer as the source of truth for this checkpoint. If your local tree drifted, re-clone that folder rather than mixing files from neighbors.

What you should already know

You do not need prior Tauri experience for part 1. Later parts assume you finished the earlier snapshots on the same machine.

  • Node.js and a Rust toolchain are available for full Tauri runs
  • You can open index.html alone if you only want a quick UI peek

Why Tauri fits Lookout

Tauri wraps a system webview with a Rust core—ideal for teaching browser chrome without shipping Chromium yourself.

Address bar, tabs strip, and webview live in HTML; navigation history stays in Rust or local storage.

Checkpoint

After you run the snapshot, you should recognize the behavior described in the goal—before you move on. If the window (or server) never appears, stop and fix the run steps.

Code shape

Snapshots stay small on purpose. Look for this kind of core call as you read the folder:

window.location.assign(url);

How to run it

Clone the teaching repo, open 04-Data-Layer, install what the README asks for, then run npm run tauri dev.

git clone https://github.com/michaeldunga1/fcc-tauri-browser.git
cd fcc-tauri-browser/04-Data-Layer
npm install
npm run tauri dev

Common mistakes

  • Ignoring platform-specific install notes in the snapshot README
  • Creating tables twice with conflicting schemas
  • Forgetting to commit/close the database connection in long sessions
  • Looking for seed data in part 3 before the data layer exists

Related tutorials