Rullst AcademyRullst Academy/Lesson
Applications with Rullst I · Lesson 01 / 14

An application you can hold

Aurora station needs to organize fictional repairs without losing the list when the browser closes.

Learning paths14 min

Let's discover together

  1. 1

    This Building track brings together Rust II, HTML, JavaScript and SQL I. Check your entry skills: explain a function returning Result, a SELECT with WHERE and a GET request. If one is missing, use the linked tracks and return; you do not need the entire catalog.

  2. 2

    Our contract: create a mission with title and priority 1–3, list up to 100 and mark completion. Use invented data only. There are no accounts, payments, personal data, deletion or public hosting. This boundary leaves room to understand each decision.

  3. 3

    The browser displays and sends; the server decides whether input is valid; SQLite stores records. Closing a tab does not delete the database file. An unsent draft can disappear: typing in the form is not saving on the server.

  4. 4

    Download the activity kit and read README.md. The complete app is a reference to investigate, not a finished original submission. Phones support reading and answering; compiling and running requires a computer with Rust. Record predictions, changes and help in NOTES.md.

Your application workbench

The kit includes a complete app to investigate and modify. The excerpt below explains this step; the editor contains the indicated file. Rullst Academy does not compile or run this server in your browser.

File to study and modify

NOTES.md

Browser → HTTP → Rullst → SQLite
GET /api/missions
POST /api/missions
PUT /api/missions/1/completion

Extract the kit to a new folder and open a terminal beside Cargo.toml. Use Rust 1.96+; the first build may download dependencies and take time. Then open http://127.0.0.1:3010. Stop with Ctrl+C and run again after editing.

cargo test --locked
cargo run --locked
My files and GitHub

Download your draft and replace the indicated file in your extracted copy. The editor saves one file in this browser; your account saves assessments and XP. The ZIP excludes your edits. GitHub sends only the confirmed file; use Git manually for the whole app, excluding databases, backups and secrets.

Official links and next step

✦
YOUR MISSION

Bound a small problem and distinguish interface, server and persistence.

Now it's your turn

Discovery workshop

Decide before running

Bound a small problem and distinguish interface, server and persistence.
Build your answers and check when you are ready.
A moment to understand

Which demonstration verifies the minimum contract?

I need a hint

A finished appearance does not verify persistence. The contract needs an observable action and a check after restarting.

Loading your journey…

Take it with you

Write a three-action contract for a different problem, such as organizing fictional experiments. Also name two things your app will not do. Explain where saved data and drafts live.

At your own pace

My files and GitHub

Every lesson can become your own record: code, notes or a practice plan. Saving a file to GitHub is optional and does not change your XP.

Student guide

The editor and downloads open when this lesson is available to your account. Check access below or return to the track map.

Checking your access to this lesson…

Rullstpetbot

AI can make mistakes. Check the lesson material.