diff --git a/README.md b/README.md
index afd0774..91b6f20 100644
--- a/README.md
+++ b/README.md
@@ -75,11 +75,11 @@ You can customize much of it through optional URL parameters:
Examples:
-- [https://linqlover.github.io/trace4d](https://linqlover.github.io/trace4d)
-- [https://linqlover.github.io/trace4d/?trace=traces/regexMatch.json&countFPS](https://linqlover.github.io/trace4d/?trace=traces/regexMatch.json&countFPS)
-- http://localhost:5173?trace=https://raw.githubusercontent.com/LinqLover/trace4d/main/assets/traces/displayScanner.json?measureStartTime
+- [https://linqlover.github.io/trace4d/app.html](https://linqlover.github.io/trace4d/app.html)
+- [https://linqlover.github.io/trace4d/app.html?trace=traces/regexMatch.json&countFPS](https://linqlover.github.io/trace4d/app.html?trace=traces/regexMatch.json&countFPS)
+- http://localhost:5173/app.html?trace=https://raw.githubusercontent.com/LinqLover/trace4d/main/assets/traces/displayScanner.json?measureStartTime
-If you have an [own trace file](#creating-a-program-trace), you first need to copy it to `assets/traces` (or to any public web server).
+If you have an [own trace file](#creating-a-program-trace), you can select it on the [landing page](https://linqlover.github.io/trace4d/).
#### Navigation
diff --git a/docs/paper/sections/05_use_case.tex b/docs/paper/sections/05_use_case.tex
index 428e57b..446c4a8 100644
--- a/docs/paper/sections/05_use_case.tex
+++ b/docs/paper/sections/05_use_case.tex
@@ -8,7 +8,7 @@ \section{Use Case: Exploring Internals of a Regular Expression Engine}
In this example, our programmer visualizes the construction of the simple regular expression \hardcode{\textbackslash{}d|\textbackslash{}w+} to gain a closer understanding of the involved subsystems and their interactions.
To create the visualization, the programmer records and exports a trace of the program \code{\textquotesingle{}\textbackslash{}d|\textbackslash{}w+\textquotesingle{} asRegex} in Squeak and loads it into the \tfd{} web app%
-\footnote{The interactive visualization of the described program trace is available at \ifanon{\url{https://user.github.io/repo/?trace=traces/regexParse.json} (blinded)}{\url{https://linqlover.github.io/trace4d/?trace=traces/regexParse.json}} and in the Wayback Machine of the Internet Archive.}%
+\footnote{The interactive visualization of the described program trace is available at \ifanon{\url{https://user.github.io/repo/app.html?trace=traces/regexParse.json} (blinded)}{\url{https://linqlover.github.io/trace4d/app.html?trace=traces/regexParse.json}} and in the Wayback Machine of the Internet Archive.}%
.
As the visualization loads, she can see about 25 objects moving around in the object map and arranging themselves into a semi-structured graph within a few seconds~(\cref{fig:teaser}).
By navigating through the scene, she discovers several meaningful objects and clusters of objects:
diff --git a/packages/frontend/package.json b/packages/frontend/package.json
index 84414aa..2709b55 100644
--- a/packages/frontend/package.json
+++ b/packages/frontend/package.json
@@ -4,6 +4,7 @@
"license": "MIT",
"dependencies": {
"@fortawesome/fontawesome-free": "^6.4.2",
+ "bootstrap": "^5.3.2",
"collect.js": "^4.36.1",
"d3": "^7.8.5",
"d3-flame-graph": "^4.1.3",
diff --git a/packages/frontend/src/app.html b/packages/frontend/src/app.html
new file mode 100644
index 0000000..42e25b1
--- /dev/null
+++ b/packages/frontend/src/app.html
@@ -0,0 +1,177 @@
+
+
+