Skip to Content (Press Enter)
Back to Ideas
69
Like
Follow Idea
Improve intermodule screen navigation
554Views
4Comments
New
Frontend (App Interfaces)

Hi,

In Reactive Web Apps I've noticed that when navigating to public screens from other modules the transition is very slow - it shows a blank screen first, then it starts loading the screen and the CSS, causing a Flash of unstyled content.

This takes about 2 to 4 seconds, making it a horrible experience. 

Upon further investigation, I've discovered that OutSystems is treating the navigation as a navigation to a totally different application, loading again all the necessary resources (JS, HTML, CSS). This is very atypical for a Single Page Application.

This makes segregating front ends a major trade-off.

Can this be improved?

Thanks,

Tiago

23 Nov 2022
Copy link to comment

Absolutely right. 

I also facing same issue. May be it a bug from user point of view.

It should be improve.

Nice idea.

26 Nov 2022
Copy link to comment

Hey

That is a very good observation.

28 Nov 2022
Copy link to comment

Hi everyone,

I wanted to echo something Tiago mentioned.

When building a super app with multiple modules in Reactive Web Apps, going from multiple screens in one module to another feels really slow. It’s like loading a totally different app (which it is):

  • CSS and JS reload, causing a flash of unstyled content

  • The overall experience is just jarring, not the smooth app you’d expect

For apps meant to feel like a single, unified experience, this makes module segregation a big trade-off. Ideally, navigation should be seamless, sharing already loaded resources instead of doing a full reload every time.

Has anyone found a good workaround for this? Or is this something OutSystems plans to improve?

Thanks!

03 Oct 2025
Copy link to comment

This is even visible in OutSystems' own products, for example ODC Portal. Notice how long it takes me to navigate from the /deployments module to the /performanceanalytics module.

03 Oct 2025
Copy link to comment