In the screen lifecycle, does the preparation run on the browser?

The correct response is that the preparation does not run on the browser. In the OutSystems platform, the preparation phase of a screen is executed on the server-side, rather than in the client's browser. This means that when a request is made for a screen, the server processes the logic defined in the preparation stage, fetching data and performing necessary computations, and then sends the rendered HTML back to the client.

This server-side execution is crucial for ensuring that any data preparation is done with access to resources and logic on the server, maintaining security and centralizing data management. By handling the preparation in this way, OutSystems reduces workload on the client-side, allowing the browser to focus on rendering the user interface and resulting in a more efficient operation.

The alternatives suggest different conditions that are not aligned with how the OutSystems platform is designed regarding the screen lifecycle, which confirms that preparation is fundamentally a server-side process.