Skip to content

Release Samsung Privacy Display support 0.2.0#1

Draft
lech-kalinowski wants to merge 5 commits into
mainfrom
codex/samsung-privacy-display-0.2.0
Draft

Release Samsung Privacy Display support 0.2.0#1
lech-kalinowski wants to merge 5 commits into
mainfrom
codex/samsung-privacy-display-0.2.0

Conversation

@lech-kalinowski

Copy link
Copy Markdown
Contributor

Summary

  • add Android capture protection and best-effort content sensitivity controls
  • detect Galaxy S26 Ultra, Android 16, and Knox Service Plugin readiness
  • add typed Samsung Privacy Display deployment guidance for device-wide and work-profile policies
  • prepare the npm package build, declarations, tests, changelog, and MIT license
  • version the backward-compatible feature release as 0.2.0

Why

Samsung exposes Privacy Display through Knox Service Plugin managed configuration rather than a callable third-party app API. This release gives React Native applications useful standard Android protections while providing an accurate enterprise deployment path for eligible managed devices.

Developer impact

Applications can enable window capture protection, mark content as sensitive, inspect Samsung Privacy Display eligibility, obtain their Android package name, and generate validated KSP policy guidance without claiming direct control of the hardware feature.

Validation

  • npm test (4 tests passing)
  • npm pack --dry-run (26 files; release metadata reports 0.2.0)
  • native Kotlin bridge compiled against Android 16 and React Native bridge signatures

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant