# FinClip Introduction
FinClip consists of three main components: Cloud, Client, and Developer Tools:

- Cloud refers to the
FinClip Management Console(opens new window), which manages the entire lifecycle of Mini-Programs, including development and publishing; - Client refers to the
FinClip Mini-Program SDK, representing mobile Apps or various smart devices integrated with the FinClip Mini-Program SDK, providing them with the capability to run Mini-Programs; - Developer Tools are primarily used for writing, debugging, uploading, and previewing Mini-Program code.
# How Does the FinClip Mini-Program SDK Work?
The FinClip Mini-Program SDK provides a Security Sandbox and Host Environment capable of running Mini-Program business code:
- The
Security Sandboxis responsible for protecting the business applications within Mini-Programs, transmitting data in a secure and trusted environment to avoid interference and eavesdropping by third parties; - The
Host Environmentis responsible for executing the Mini-Program JS business logic code and using WebView to render and display Mini-Program pages (Learn More).
# What is the FinClip Mini-Program Security Sandbox?
The FinClip Mini-Program SDK also serves as the Security Sandbox for Mini-Program execution. Within the Host Environment of a Mini-Program, mobile or desktop applications need to interact with both the Logic Layer and the View Layer separately. These two layers cannot communicate directly and can only exchange data through the Host-App.

Because of this architecture, FinClip can also ensure the security and reliability of the Mini-Program Runtime:
- The FinClip Mini-Program SDK provides a closed, secure Runtime for business code, effectively preventing risks such as interference from external code and data leakage. Hosts on third-party network platforms can only launch the Runtime through interfaces actively exposed by the SDK;
- The FinClip Mini-Program SDK can fully control the Runtime environment required by business applications and their necessary external communications, employing various mechanisms to ensure network communications are not intercepted or interfered with;
In desktop and Android environments, we additionally use the following methods and means to ensure the security and reliability of the Mini-Program Runtime:
- The desktop version utilizes the
Chromium Embedded Frameworkbrowser kernel. Its Runtime is completely isolated from the system browser, enabling robust data isolation and data protection based on this kernel.
# Android SDK Integration Guide
- Integration Guide
- Common APIs
- Android Mechanism Explanation
- Android SDK Common Issues
- Android SDK Update Log
# Others...
If you need to view related DEMO examples, you can check our Github (International) (opens new window) and Gitee (China) (opens new window) repositories.