Multi-page app architecture in No-Code - Step-by-Step Execution

Concept Flow - Multi-page app architecture

User opens app URL

↓

Browser requests page 1

↓

Server sends full HTML page 1

↓

User interacts with page 1

↓

User clicks link/button

↓

Browser requests page 2

↓

Server sends full HTML page 2

↓

User interacts with page 2

↓

Repeat for each page

↓

User closes app

The app loads a full new page from the server each time the user navigates, showing one complete page at a time.

Execution Sample

No-Code

1. User opens homepage URL
2. Server sends full homepage HTML
3. User clicks 'About' link
4. Browser requests About page
5. Server sends full About page HTML

This shows how each page is loaded fully from the server when the user navigates.

Analysis Table

Step	User Action	Browser Request	Server Response	Page Displayed
1	Open app URL	Request homepage	Send homepage HTML	Homepage
2	Click 'About' link	Request About page	Send About page HTML	About page
3	Click 'Contact' link	Request Contact page	Send Contact page HTML	Contact page
4	Click 'Home' link	Request homepage	Send homepage HTML	Homepage
5	Close app	No request	No response	App closed

💡 User closes app, no further requests made

State Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
Current Page	None	Homepage	About page	Contact page	Homepage	App closed

Key Insights - 3 Insights

Why does the whole page reload when I click a link?

Because in multi-page apps, each navigation sends a new request to the server, which responds with a full new page, as shown in execution_table rows 2 and 3.

Does the app keep any data in memory between pages?

No, each page is loaded fresh from the server, so any data in memory is reset unless stored externally (like cookies). This is seen as the page changes completely in execution_table.

Is the user experience slower because of full page reloads?

Yes, because the browser must load the entire page again from the server each time, unlike single-page apps that update parts dynamically.

Visual Quiz - 3 Questions

According to the execution_table, what page is displayed after step 3?

A Contact page

B Homepage

C About page

D No page

💡 Hint

Look at the 'Page Displayed' column in row 3 of the execution_table.

At which step does the browser request the About page?

A Step 1

B Step 2

C Step 4

D Step 3

💡 Hint

Check the 'Browser Request' column in the execution_table for the About page request.

If the user never clicks any link, how many server requests are made?

A Two

B Zero

C One

D Multiple

💡 Hint

Refer to the execution_table row 1 where the homepage is requested once.

Concept Snapshot

Multi-page apps load a full new page from the server on each navigation.
Each page is a separate HTML document.
User actions cause browser requests for new pages.
Server responds with complete HTML pages.
This causes full page reloads and resets app state.
Simple but can be slower than single-page apps.

Full Transcript

Multi-page app architecture means the app shows one full page at a time. When the user opens the app, the browser asks the server for the homepage. The server sends the full homepage HTML. When the user clicks a link, the browser requests the new page from the server. The server sends the full new page HTML. This repeats for each page the user visits. Each page load resets the app state because the browser loads a new document. This is simple but can feel slower because the whole page reloads every time.