Update docs/platforms/native/advanced-usage/backend-tradeoffs/index.mdx

Co-authored-by: Bruno Garcia <[email protected]>

Author: supervacuus

docs/platforms/native/advanced-usage/backend-tradeoffs/index.mdx

@@ -49,7 +49,7 @@ Both backends are comparable in how they differ from `crashpad`. However, there
 
 ### So when do I choose `inproc`?
 
-`inproc` is currently the backend of choice for `Android` because it allows us to couple it with our own fork of a powerful platform unwinder `libunwindstack` (rather than relying on a user-space interface). This allows us to support very old Android versions.
+`inproc` is currently the backend of choice for `Android` because it allows us to couple it with our own fork of a powerful platform unwinder `libunwindstack` (rather than relying on a user-space interface). This allows us to support very old Android versions. In addition, stack walking on device on Android is preferred since we don't have all system symbols available for server-side symbolication. A [best-effort symbol collection exists](https://github.com/getsentry/symbol-collector), but that'll never be as reliable as stackwalking on device.
 
 `inproc` is the right choice if you