QQQ 4.1 RC1 Quickstart

QQQ 4.1 RC1 with Next 1.0 RC11

This prerelease pairs QQQ 4.1.0-RC.1 with Next 1.0.0-RC.11. Next is served by the Java application by default. See the QQQ release notes and Next release notes for the exact artifacts and limitations. The stable 4.0 quickstart remains available.

Prerequisites

Use a Java 21 JDK, Git, curl, unzip and Bash on macOS, Linux or Windows WSL. The launcher checks these tools and port 8000 before starting. Maven Wrapper downloads Maven automatically. This RC quickstart needs no Docker, Node.js installation, database setup or provider account; one Java process serves the API and dashboard with synthetic H2 data and local mock authentication.

Start the editable sample

curl -fsSLo quickstart.sh https://raw.githubusercontent.com/QRun-IO/qqq/quickstart-4.1.0-RC.1/quickstart.sh
bash quickstart.sh

The script creates a new qqq-sample directory, checks out the candidate source, resolves the exact published dependencies and compiles the sample. It opens localhost:8000/app/person. Choose another new directory with bash quickstart.sh my-qqq-app; existing directories are not overwritten. Explore seeded Person records, open a record, edit it, and try Actions → Greet Interactive.

Stop, edit and restart

Press Ctrl+C in the launch terminal. Edit Java source under qqq-sample/qqq-sample-project/src/main/java, then rebuild and restart:

cd qqq-sample
./quickstart.sh

The in-memory H2 data is recreated on restart, so local record edits do not persist. Build and application output is in quickstart.log. The editable checkout remains on disk. For the compatible Material dashboard, run QQQ_FRONTEND=material ./quickstart.sh; stop the previous process first so port 8000 is free.

Timing and troubleshooting

The target is a usable seeded application within 90 seconds after prerequisites are installed, including application downloads. The earlier 4.0 benchmark is not an RC1 measurement. Machine resources and network speed affect startup; the launcher prints its measured readiness time. Prerequisite installation is outside that target.

If a required tool is absent or the port is occupied, follow the launcher's message. If compilation or startup fails, inspect quickstart.log, correct the reported problem, and rerun from the same checkout. A failed attempt does not require a second clone. Do not use local mock authentication for a publicly exposed application.

Known Next RC11 limitations and future candidates

The accepted RC1 limitations include Firefox/WebKit/tablet failures, base-path hosting, Google Drive picker integration, report/query parity, input blocks/icons, script autocomplete and remaining visual comparisons. They remain open follow-ups; this candidate does not certify every browser or feature. The ESB phone/tablet test-selection correction and its browser verification are tracked in #990. See the acceptance decision and tracking.

Each newly published Next RC gets a new QQQ 4.1 RC with exact dependency pins, relevant compatibility and quickstart checks, updated notes and known limitations. Earlier candidates remain immutable. Final 4.1 general availability is a separate release decision.