89740f7e0a
Summary: This diff includes minor changes to the pages within the Features section of Flipper Docs. Reviewed By: passy Differential Revision: D41471000 fbshipit-source-id: 0a414d1e5e0cff5d874d3fe6eab647c3877b9caf
20 lines
1.5 KiB
Plaintext
20 lines
1.5 KiB
Plaintext
---
|
|
id: index
|
|
title: Introduction
|
|
---
|
|
import useBaseUrl from '@docusaurus/useBaseUrl';
|
|
|
|
Flipper itself only provides the architectural platform. What makes it useful are the plugins built on top of it, such as [Logs](plugins/device-logs.mdx), [Layout Inspector](plugins/inspector.mdx) and [Network Inspector](plugins/network.mdx).
|
|
|
|
Plugins can be tailored to your business logic and the use-cases you have in your app. Flipper is shipped with a couple of built-in all-purpose plugins, but you're encouraged to build your own (see below). Each plugin needs to be enabled individually.
|
|
|
|
<img alt="Plugins" src={useBaseUrl('img/plugins.png')} />
|
|
|
|
## Build your own plugin
|
|
|
|
The Flipper desktop app and the mobile native SDK establish a connection that is used to send data to and from the device. Flipper 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.
|
|
|
|
If there is no plugin that does exactly what you want, you can build your own plugin tailored to your needs. A plugin always consists of the native implementation sending and receiving data and the desktop plugin visualizing data: the native implementations are written in Java, Objective-C, or C++, the desktop UI is written in React.
|
|
|
|
To learn more and build your own plugin, see the [Creating Plugins](../tutorial/intro.mdx) section of the Flipper Docs.
|