Notes:

iOS status

@gsnedders: Have an issue. Working on fixing it with a simple solution
@jgraham I agree that just getting it working is good for now.
@gsnedders One downside is that it has run every time even if there's nothing to do.
@jgraham Blocked on anything?
@gsnedders No. Probably need a review in a few hours.
@past - Have you seen the email from MSFT? Asked for another month.
@gsnedders - Yes
@past - Feel free to chime in if anything changes.
@past - How soon is Safari on iOS coming after this ?
@gsnedders - Check back in at the end of the week

Android status

@past You can see @DanielRyanSmith 's work live now. Wondering if we should add a placeholder empty column to get a sense of the UI flow. Take a look and comment on the PR.
@jgraham At first glance, this looks nice. One thing: We need a label to indicate that this is a work in progress.
@past Once this is landed, how does someone navigate to it? Where should the link reside?
@jgraham I initially imagined it being part of the interop page. But mobile probably won't be a first class citizen for 2025.
@past If it will be a higher priority for Firefox and Apple, I can raise that on our side to prioritize it.
@jgraham I can raise it but maybe not for the end of the year.
@past When is the deadline for priorities for 2025 made?
@jgraham So far it seems like Firefox has less than a gap than Chrome and we are still waiting for results from Apple. So it will be less of a risk for us than others. For the interop 2025 selection process, we would need to have a serious conversation around mobile. Then it would be motivation to make sure things are stable.
@past I just want to make sure that no one on the Google side is blocked because they would consider a mobile feature to be part of Interop 2025.
@gsnedders Having clear examples about what people care about helps justify.
@jgraham In the meantime, I will review this PR.