As LAT is now a hard metric for Lens approval, especially for advertising and commercial lenses, we need more robust tools for debugging LAT performance in lenses.

Common issues being seen are large differences between LAT reporting in debugging on device vs reported debugging when a Lens is submitted (often 2x or more).
Even when following the guidelines for remote assets and async prefab loading, these can seem to have little to no effect.

It would be great to have a comprehensive list of which specific technologies within Lens studio incur LAT spikes and specific mitigation steps to get these over the line. Body Tracking being a main culprit seen on the discord.

If Snap uses a specific device profile when testing LAT, which device is this? The only device I can get to report LAT even near the submission values is an iPhone SE gen 2.

Thanks!