SceneView for companies

The facts a team checks before it adopts an SDK: the license, what the code sends over the network, which platforms are production-grade, how often it ships and where to report a vulnerability.

Last checked: September 26, 2026 · SceneView 4.40.0

Apache-2.0 Commercial and closed-source use allowed. The MCP server is MIT.
No telemetry No analytics, no accounts. One documented web default, below.
Android stable iOS, web and the cross-platform bridges are alpha.
22 releases in the last 90 days, 75 since 4.0.0 in April 2026.

License in plain words

SceneView is released under the Apache License 2.0. In practice:

  • You can use it in commercial and closed-source apps, and modify it, without paying or asking.
  • You get a patent grant from every contributor for their contributions.
  • When you redistribute it, keep the license text and the NOTICE file, and mark the files you changed.
  • No trademark rights: the license does not let you use the SceneView name or logo to brand your product.

The mcp/ directory (the sceneview-mcp server for AI assistants) is under the MIT License. The 3D models used in the samples, docs and this website are third-party works under their own licenses, listed in assets/CREDITS.md; they are not needed to use the SDK.

What the SDK sends over the network

No analytics, no telemetry, no advertising identifiers and no accounts. The SDK opens network connections only for the URLs your app gives it, such as a model to load.

One exception, on the web. sceneview-web fetches its default lighting environment from sceneview.github.io when a viewer starts. To avoid that request, host the environment yourself: with the Kotlin/JS builder, environment(iblUrl, skyboxUrl) or noEnvironment() skip the default; with the JavaScript API, viewer.setEnvironment(url) replaces it once the viewer is running.

Android permissions declared by the libraries and merged into your manifest:

  • INTERNET (sceneview), to load models from a URL.
  • VIBRATE (sceneview), for optional haptic feedback. Remove it with tools:node="remove" if you do not use it.
  • CAMERA (arsceneview only), for augmented reality.

Platform AR services. On Android, AR runs on Google Play Services for AR (ARCore), under Google’s terms. On Apple platforms, AR uses ARKit and RealityKit on the device.

This page is about the SDK. The sceneview.github.io website itself uses Google Analytics, as described in the privacy policy.

Platforms and maturity

Only Android is marked stable today. Alpha platforms ship and are usable, with fewer guarantees: their APIs may still change between 4.x releases.

PlatformStatusBuilt on
AndroidStableJetpack Compose, Filament, ARCore. API 24+, OpenGL ES 3.0.
Android TVAlphaCompose TV, Filament.
iOS, macOS, visionOSAlphaSwiftUI, RealityKit. iOS 18, macOS 15, visionOS 2.
WebAlphaFilament.js on WebGL2 / WASM.
Compose MultiplatformAlphaViewer subset, no AR.
Desktop (JVM)AlphaCompose Desktop, Filament.
Flutter, React NativeAlphaNative bridges to the Android and Apple SDKs.

Source: the platform table in the README.

Release cadence

75 releases from 4.0.0 (April 13, 2026) to 4.40.0 (September 26, 2026), 22 of them in the last 90 days. Android artifacts are published on Maven Central, the web and React Native packages on npm, the Flutter plugin on pub.dev and the Apple package through Swift Package Manager.

Source: final v4.* tags, counted with git tag on September 26, 2026. Full history: GitHub releases and the changelog.

Versioning and support today

  • Semantic versioning. A binary-compatibility check (apiCheck) runs in CI on pull requests that touch the Android libraries, so their public API cannot change by accident.
  • Deprecations before removals. Deprecated APIs carry a ReplaceWith hint your IDE can apply, and upgrades are documented in the migration guide.
  • Fixes ship in the next 4.x release. There is no long-term-support branch and no service-level agreement: stay on a recent 4.x release to get fixes.

Where to get help is listed in SUPPORT.md, and how the project is run in GOVERNANCE.md.

Reporting a vulnerability

Report security issues privately, never in a public issue, following the security policy. It lists the supported versions, what to include in a report and the coordinated disclosure process.

Third-party notices

The NOTICE file credits the third-party code SceneView includes or derives from, with its license. Filament, Google’s rendering engine, is used as published by Google. The authors and licenses of every sample 3D model are in assets/CREDITS.md.

Where it shows up

Private code is invisible from the outside, so this list only shows what teams published themselves.

Found in public code and posts from teams at

    Each name links to that team’s own public repository, library or blog post. A name here is not an endorsement.

    More public numbers, with their sources, are on the home page.

    Contact

    All contact happens in the open, on GitHub: