Very nice summary. I do hope one day we get the option to make flows load faster or at least specify how much screen space to use while loading. The blank may be acceptable, but screen jumping around isn't so acceptable.

I often use a flow component on screen on mobile when the equivalent desktop component isn't supported. (GRRR). It allows me to keep one page design for desktop and mobile more frequently which really cuts down on work and improves adoption of mobile. You just make the desktop and flow both conditionally visible on opposite device criteria.

I use display-only flows often to replace rich text components when I really need customization with merged data values from the record. I really wish in such cases they loaded faster however.

I use flows to narrate a summary of records all the time. So much better, frankly, than list views. You can put text around them, condense, highlight, etc.

Putting flows in tabs is also great and even better now that tabs can be conditionally visible. I'm loving that new feature for UX for sure!

Thanks for yet another really useful blog! Keep them coming!

--Terry