Best Practice Question

I’ve implemented a page in FlutterFlow that displays data (non-editable) from a single record in a Firebase collection. I’ve added a toggle button on this page that switches the page into an “edit mode.” When this toggle is activated:

1. The boolean field is updated,

2. The page reloads to display editable fields and

3. A “Save” button allows users to save changes to the record.

After saving, the page reloads again, returning to the original view with non-editable fields.

I’m debating whether this approach—having a single page that toggles between view-only and edit modes—is a better practice than creating two separate pages: one for viewing data and another for editing it.

Sorry the image is not related to the post, but it required me to upload something.

Specifically, I’m considering the following factors:

• User Experience: Would a separate edit page be more intuitive for users compared to toggling between modes on the same page?

• Performance: Does reloading resources on the same page (to switch between view/edit modes) affect performance, especially as the app scales to support many companies with many users editing and viewing data?

• Scalability: Since I’m currently building this app for a manager-user setup but plan to scale it for multiple companies with numerous users, would maintaining two pages (view vs. edit) offer better long-term manageability for the app structure?

• Code Maintainability: Which approach would make the app’s codebase easier to maintain and debug as it grows in complexity?

I’d appreciate any insights or best practices regarding whether it’s better to toggle modes on the same page or split the functionality into distinct pages for viewing and editing records. Thank you!