I would vote against such a change as wasted development effort
For example - my workflow is such that I start using OBS Studio long before I'm going to start Streaming/Recording. Once I'm done streaming, it is time for me to move onto something else (and often shutting down PC). So telling me AFTER streaming/Recording is over is a BAD time
- This idea seems more oriented to appealing to ADD dysfunction, than a functional need
if anything, (and I don't really like this) maybe have a non-default General Settings Option for an update check at time of clicking Exit. If there is an update, a notice can popup, with an option to stop the exit and update instead?
And yes, I'm in the manual update OS and apps crowd, as after decades of experience, I simply know better than to trust auto-updating
An update availability check when any app starts (OBS Studio included) is most logical and easiest to implement. And for users awaiting a required (function/security, etc) fix, earliest possible notification is appropriate. and users (especially of FOSS) should be planning an update (system backup or other plan to cleanly back out update, aware of implications/dependencies (like UI change with v28 and plugin impact, etc)), and testing afterwards, rather than 'letting it happen'.
For me, in last 3+ years, I've yet to have an OBS Studio update that I needed to apply the day (and often the week) it was released. And as a NDI user, some updates have dependencies meaning month+ waits. so, I'm struggling to see exact timing of an OBS Studio update availability notice being all that important