Skip to content

Commit

Permalink
add cons
Browse files Browse the repository at this point in the history
  • Loading branch information
philipphofmann committed Jun 4, 2024
1 parent 27c44c4 commit a68b563
Showing 1 changed file with 5 additions and 1 deletion.
6 changes: 5 additions & 1 deletion text/0136-mobile-tracing-without-performance-v-2.md
Original file line number Diff line number Diff line change
Expand Up @@ -54,7 +54,11 @@ it based on routes, so it should be easy to implement for React-Native.

### Cons <a name="option-1-cons"></a>

1. It doesn’t work well for declarative UI frameworks as Jetpack Compose and SwiftUI for which the
1. For single-screen applications such as social networks, the lifetime of a trace could still be
long, and multiple unrelated events could be mapped to one trace.
2. For applications running for a long time in the background, such as running apps, the lifetime of
a trace could still be long, and multiple unrelated events could be mapped to one trace.
3. It doesn’t work well for declarative UI frameworks as Jetpack Compose and SwiftUI for which the
SDKs can’t reliably automatically detect when apps load a new screen.

# Drawbacks
Expand Down

0 comments on commit a68b563

Please sign in to comment.