Skip to content

Latest commit

Β 

History

History
96 lines (71 loc) Β· 5.36 KB

README.md

File metadata and controls

96 lines (71 loc) Β· 5.36 KB

Insta360 SDK/API Developer Docs

Developer documentation for the Insta360 X / Go / ACE / Wave / Link series SDKs / APIs (built with VitePress, deployed on GitHub Pages).

Online docs (recommended)

🌐 https://insta360develop.github.io/Insta360-Developer_Docs/

⚠️ If the Pages site above is unreachable (some networks have unstable access to github.io), you can browse the in-repo Markdown docs below as a fallback β€” readable as long as you can access this repository.


πŸ“š Documentation (in-repo Markdown Β· fallback)

Source files live under docs/en/sdk/ (English) and docs/ch/sdk/ (Chinese) β€” see Repository structure.

X / ACE / GO API & SDK β€” one shared doc set for all three series

Doc set Overview Release Notes API Reference Used by
Android SDK Overview Β· Dev Environment Β· Camera Integration Β· Media Integration Release Notes Camera SDK Β· Media SDK Β· Legacy 1.x.x (X only) X Β· ACE Β· GO
iOS SDK Overview Release Notes API X
Desktop SDK Overview Release Notes Camera SDK Β· Media SDK X
OSC Protocol Overview β€” API X

Link SDK β€” for the Link series

Doc set Developer Guide Download Used by
UVC Camera SDK Developer Guide Insta360Develop/Link-SDK Link

Wave SDK β€” not yet available.

Series overviews: X Β· ACE Β· GO Β· Link Β· Wave


Repository structure

Content and routing are deliberately separated, so an SDK shared by several series is written once.

docs/{ch,en}/
β”œβ”€ index.md              home page β€” product series cards
β”œβ”€ x/  ace/  go/         series overview + thin per-series page shells
β”œβ”€ link/                 series overview + page shells (UVC Camera SDK)
β”œβ”€ wave/                 series overview only β€” no SDK published yet
└─ sdk/                  ← the single source of truth for all SDK content
    β”œβ”€ x-ace-go/         shared by the X, ACE and GO series
    β”‚   β”œβ”€ android/  guide.md Β· changelog.md          (platform-wide overview / release notes)
    β”‚   β”‚            environment.md Β· camera-integration.md Β· media-integration.md
    β”‚   β”‚            camera-api.md Β· media-api.md     (V2.x.x β€” X Β· ACE Β· GO)
    β”‚   β”‚            legacy-api.md                    (V1.x.x β€” X series only)
    β”‚   β”œβ”€ ios/      guide.md Β· changelog.md Β· api.md
    β”‚   β”œβ”€ desktop/  guide.md Β· changelog.md Β· camera.md Β· media.md
    β”‚   └─ osc/      guide.md Β· api.md
    └─ link/            Link series
        └─ uvc/      guide.md                         (UVC Camera SDK developer guide)
  • docs/{ch,en}/sdk/** holds the actual content. It is excluded from routing (srcExclude in docs/.vitepress/config.mts), so these files generate no pages of their own. Edit documentation here.
  • docs/{ch,en}/<series>/<platform>/…/index.md are one-line shells: <!--@include: ../../../sdk/x-ace-go/android/camera-api.md-->. They own the URL and keep the sidebar in that series' context. A single edit to a shared source updates every series.
  • Navigation is generated from sdkGroups and seriesList in docs/.vitepress/configs/shared.mts β€” the single source of truth for nav and sidebars. A doc set either lists its pages explicitly via pages (what Android does) or falls back to the default overview β†’ changelog β†’ api pattern. A page may carry series: ['x'] to appear for some series only β€” that is how the legacy Android API doc stays out of the ACE / GO sidebars.

Common tasks

Task What to do
Fix or extend an SDK doc Edit the file under docs/{ch,en}/sdk/… β€” all series pick it up
A series gains a platform (e.g. ACE adds iOS) Add the key to that series' platforms in shared.mts, then add the shell pages under docs/{ch,en}/ace/ios/
Add a whole new SDK Add a group to sdkGroups, put the content in docs/{ch,en}/sdk/<group>/, and reference it from seriesList

Developer resources

Local development

npm install
npm run dev     # local preview
npm run build   # build the static site into docs/.vitepress/dist