fbbf8cf16b
fbshipit-source-id: b6fc29740c6875d2e78953b8a7123890a67930f2 Co-authored-by: Sebastian McKenzie <sebmck@fb.com> Co-authored-by: John Knox <jknox@fb.com> Co-authored-by: Emil Sjölander <emilsj@fb.com> Co-authored-by: Pritesh Nandgaonkar <prit91@fb.com>
1.3 KiB
id, title, sidebar_label
| id | title | sidebar_label |
|---|---|---|
| understand | Understanding Sonar | Understanding Sonar |
The Sonar desktop app and the mobile native SDK establish an rsocket connection which is used to send data to and from the device. Sonar does not make any restrictions on what kind of data is being sent. This enables a lot of different use-cases where you want to better understand what is going inside your app. For example you can visualize the state of local caches, events happening or trigger actions on your app from the desktop.
Plugins
Sonar itself only provides the architectural platform. What makes it useful are the plugins built on top of it: Logs, Layout Inspector and Network Inspector are all plugins. Plugins can be built very specific to your business logic and the use-cases you have in your app. We are shipping Sonar with a couple of built-in all-purpose plugins, but we encourage you to build your own.
A plugin always consists of the native implementation sending and receiving data and the desktop plugin visualizing data. Learn more on how to create a plugin. The native implementations are written in Java, Objective-C, or C++, the desktop UI is written in React.