Hi @Stefan van Deventer ,

Your Quires on handling pages versus web blocks in OutSystems, particularly regarding the use of a single page navigation model, touches on an essential aspect of web development: optimizing user experience and application performance. Here’s an analysis of both approaches: 

Single Page with Dynamic Web Blocks

Advantages:

1. Performance: Reduces load times between navigations as the header and footer are loaded only once.
2. Consistency: Ensures a uniform look and feel across different parts of the app without the need to duplicate code.
3. Maintenance: Easier to maintain and update the UI components like headers and footers.

Challenges:

1. Complexity in State Management: Managing the visibility and state of multiple web blocks can become complex.
2. Initial Load Time: The initial load might take longer as the complete page with all possible blocks must be loaded upfront.
3. SEO and Bookmarking: Dynamically changing content might affect SEO, and users might not be able to bookmark specific states or content.

Multiple Pages with Replicated Layouts -

Advantages:

1. Simplicity: Each page is independent and can be managed easily.
2. SEO Benefits: Better for SEO as each page can be optimized for specific content.
3. Bookmarking/Caching: Users can bookmark pages, and browsers can cache pages independently.

Challenges:

1. Performance: Each page reloads the common elements like headers and footers, which can make the app feel slower.
2. Redundancy: Increases the redundancy of code, which can lead to higher maintenance overhead.

Recommendations:

1. Given your use case of a progressive web app (PWA) where the header and footer remain constant across different views, 
2. adopting a single page application (SPA) approach using one page with multiple web blocks might be more beneficial. 

This approach would:

1. Improve the perceived performance by loading the layout once and dynamically updating the content area.
2. Reduce the redundancy of having the same layout components reload with each page visit.
3. Streamline maintenance efforts as changes to the layout need to be done in one place only.
4. To address the complexities associated with this model, such as state management and initial load performance.

You might consider:

1. Lazy loading for web blocks, where blocks are loaded only when needed.
2. State management tools like React’s Context API or Redux (if using React) to handle the state of different blocks effectively.