...
Don’t do this too quickly, yes, I am sure the users have been hassling you for this since 2018, or 2020, but if it’s not rolled out well, they will not want to do it for any other objects and then they may lose some excellent benefits. This is especially if you don’t get the Record Type behaviour 100% matching what they have now.
For teams that rely on Mobile devices heavily, I would be even extra cautious, and test everything super well before making Dynamic Forms live.
How will the record creation and record change process change for users. The weird page layout with the fields on tabs below the System Information may be difficult to deal with. People will be saying they have to scroll too far to quickly create or edit a record.
There are ways to address this but it is such an administrative burden.
Follow the progress of this idea that is part of the May 2024 Prioritisation round.
What will it look like when you jump from a record with Dynamic Forms to a record without Dyanamic Forms? Will it be too disconcerting for the users?
Read Michael’s blog post around consistency of page layouts. I think if the fields are consistently laid out, it could be OK.
What will your maintenance overhead be? Is it worth it?
No matter what you think, you will have to maintain both Page Layouts and Lightning Pages. There will be something you need that is controlled by Page Layouts. And you do want your Page Layouts to be at least a little consistent with the Lightning Page, and not just dumping everything in the one section.
What will be the effect of being “gaslightninged” every single day when you go to the Page Layout and change a field position, or add a button, then go to the Lightning Page and refresh, and take 10 refreshes, and 5 minutes to realise that Oh, this is Dynamic Forms!?
...