Application embedding versus public embed

I’ve spent the morning unravelling the mysteries of JWT with C# (details in another post) to embed dashboards using application embedding rather than public embedding.
I’d hoped that it would give my users extra functionality to filter lists, but they can still only sort columns.
The final dashboard embedded in an IFRAME appears to have no advantages over using the much simpler public link.
Other than the potential security advantage of having a really long string for security, is there any other reason to embed in this way?

You can lock parameters from the side of the embedding application - and thus e.g. based on the currently logged in user restrict what they can see in the embedded Metabase iframe.