Business cases could include:attaching additional data to default
lifecycle eventsdisabling events without value justifying their
costdelaying the transmission of an event for proper sequencingOur
current pressing issue is #1/#2. We have a slew of information we need
to transmit when a user launches the app; however, we can't include it
in the launch event. This renders it nearly worthless to us since we are
forced to make a trackState call for every launch. It's similar to
having to make two s....
We should have the ability to control default lifecycle metrics behavior
in the Mobile SDK configuration. This would include toggling whether or
not events such as app launches automatically trigger lifecycle
tracking, so that they might be manually sent or disabled entirely.