this is solid, and to make it slightly more complex, mobile users not using a mobile app with api endpoints have to be considered too.  not all of us have dev liscenses or 800$ to throw at a mobile app deployment,
so for example my users view my site via the browser, and need backwards compatibility with the function, as well as ANY other una site operator...
so a toggle i think is a nice intermediary workaround, for those fetching the mobile page.
because it will work on some hardware, and will not work on others,
giving the site operator the ability to choose what series of detection scripting flow gets executed given the workload of "video meeting create event" , and how tis displayed based on the toggle ""push content to mobile browser users" and "hope for compatibility" versus "hide button from user if detected mobile fetch via browser" ?
i'd rather try to fetch and havec mymobile browser blow up than not have the option...
its NNAND/SSD anyway, you really can't break it.. you just have to re-set it..so theres no loss if it doesnt work, other than .. it not working. humans we are an adaptive species..
and who knows, maybe wont work now, but will work with further software/firmware updates to a particular device....
so best to just let them try i think....