Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions app/ios/Runner/Info.plist
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,8 @@
<true/>
<key>CFBundleDevelopmentRegion</key>
<string>$(DEVELOPMENT_LANGUAGE)</string>
<key>ITSAppUsesNonExemptEncryption</key>
<false/>
<key>CFBundleDisplayName</key>
<string>StreamBeam</string>
<key>CFBundleExecutable</key>
Expand Down
6 changes: 3 additions & 3 deletions distribution/store-listings.json
Original file line number Diff line number Diff line change
Expand Up @@ -4,8 +4,8 @@
"name": "StreamBeam",
"language": "en-US",
"website": "https://streambeam.eu",
"supportEmail": null,
"privacyPolicyUrl": null,
"supportEmail": "support@streambeam.eu",
"privacyPolicyUrl": "https://streambeam.eu/privacy/",
"googlePlay": {
"shortDescription": "Share screens and control your devices over your local network.",
"fullDescription": "Bring your screens together with StreamBeam. Watch a Windows or Mac desktop on your Android phone or tablet, or share your Android screen with another paired StreamBeam device.\n\nPair once using a QR code or an approved connection request. Saved devices let you reconnect without repeating setup. Connections run directly over your local network.\n\nUse touch controls and the on-screen keyboard to control a compatible paired device. Choose streaming quality to suit your screen and network. Audio playback depends on the sending device; Android screen sharing currently sends video without system audio.\n\nOptional Android remote control uses AccessibilityService to apply taps, swipes and keyboard input from your paired device. To edit text, StreamBeam reads and changes the focused text field locally. Accessibility text is not uploaded to StreamBeam servers; a paired viewer can see text visible in your shared screen. Enable or disable this access in Android Settings. Android asks you to choose what to share each time you start screen sharing.\n\nStreamBeam currently requires devices on the same local network and a compatible StreamBeam app on the other device. This early release does not include internet relay access.",
Expand Down Expand Up @@ -39,7 +39,7 @@
"validation": "Partner Center identity, packaged runtime and Store certification are pending."
},
"submissionChecklist": [
"Confirm publisher account, support email and a public privacy policy URL.",
"Deploy https://streambeam.eu/privacy/ and make support@streambeam.eu deliverable before any submission. Store-by-store steps: docs/STORE_SUBMISSION.md.",
"Capture screenshots of the actual release on each supported platform; do not use concept mockups as app screenshots.",
"Complete Play AccessibilityService and screen-capture foreground-service declarations with a real demonstration video.",
"Review Data safety and Apple App Privacy against the shipped SDK versions and actual data flows.",
Expand Down
1 change: 1 addition & 0 deletions docs/PROGRESS.md
Original file line number Diff line number Diff line change
Expand Up @@ -119,6 +119,7 @@ Per-platform beam/watch/control status lives in [PLATFORMS.md](PLATFORMS.md).

## Decisions log

- 2026-11-05 — **Store submission prerequisites.** Added the public privacy policy page (`site/privacy/`, data stays device-to-device; ML Kit diagnostics disclosed), `scripts/create-android-upload-key.sh` for a dedicated Play upload key (Play App Signing holds the app key, so GitHub preview APKs and Play builds stay separate signers), `ITSAppUsesNonExemptEncryption=false` (standard TLS/QUIC only, mass-market exempt) and [STORE_SUBMISSION.md](STORE_SUBMISSION.md) with per-store publisher steps and suggested form answers. Mac App Store and Flathub are out of scope: the macOS app is not sandboxed and Linux is an experimental shell.
- 2026-10-21 — **Record user-confirmed Proton Pass storage.** The publisher confirmed saving all four prepared files: Apple-compatible distribution P12, its password, App Store provisioning profile and private backup inventory. No vault restore test was performed. The missing App Store Connect API `.p8` is not backed up and still blocks upload access; retain local originals.

- 2026-10-21 — **Deploy the verified Windows artifact with an explicitly approved process-only exception.** The publisher approved one execution-policy exception for the prepared updater; persistent AllSigned remains unchanged. Installed exact `5a99a27` artifact `12348791793` on Mancave with a rollback copy retained. Worker SHA-256 `30f42e412d10e3aad0e8d7c7a8b2b981c654080ca868d97aea0895028e2eb94d`, app and Rust DLL match the artifact; the existing supervisor, worker configuration, host identity and pairings are unchanged. The supervisor confirmed the new worker stayed up, with UDP 47989 listening. A real updated-Mac to updated-Mancave stream displayed nonblank 3840×2160 AV1; stopping returned to Ready with MANCAVE still Saved. No remote-input or subjective-audio acceptance is claimed. Proton Pass is the chosen key-backup destination; login and vault selection remain pending.
Expand Down
2 changes: 2 additions & 0 deletions docs/RELEASING.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,8 @@ video/audio/control bridge separately. See [DESKTOP_RELEASES.md](DESKTOP_RELEASE
[IOS.md](IOS.md) and [WEB.md](WEB.md). Build artifacts do not establish production
signing, actual install/upgrade behavior, physical input, cameras or live latency.

Per-store accounts, forms and publisher steps: [STORE_SUBMISSION.md](STORE_SUBMISSION.md).

## Current store status — 2026-10-21

The Apple bundle identifier and App Store Connect app record have been created:
Expand Down
148 changes: 148 additions & 0 deletions docs/STORE_SUBMISSION.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,148 @@
# Store submission guide

What it takes to get StreamBeam into each store, which parts are already in the
repo, and which parts only the publisher can do (accounts, payments, legal
answers). Build, signing and upload mechanics live in [RELEASING.md](RELEASING.md)
and [DESKTOP_RELEASES.md](DESKTOP_RELEASES.md); listing texts live in
[`distribution/store-listings.json`](../distribution/store-listings.json).

Status on 2026-11-05:

| Store | Account | App record | Signed build | Upload path | Listing/forms |
|---|---|---|---|---|---|
| Apple App Store (iOS) | Argu B.V., team `Q9WPWRTU7G` | ✅ app 6825263933 | ✅ IPA 0.1.0 (4) | ⛔ needs App Store Connect API `.p8` | draft text; privacy/age/screenshots open |
| Google Play | ⛔ none | ⛔ | ⛔ no upload key | script ready, needs service account | draft text; declarations open |
| Microsoft Store | ⛔ none | ⛔ | MSIX job ready, needs identity | manual upload in Partner Center | draft text |
| Mac App Store | not planned: app is not sandboxed. macOS ships as notarized Developer ID ZIP |
| Linux (Flathub) | not planned: Linux build is an experimental shell |

Shared prerequisites, all stores:

- Privacy policy: `https://streambeam.eu/privacy/` (source `site/privacy/index.html`).
Must be deployed before any submission. Re-read it whenever data handling changes
(clipboard, internet relay, crash reporting).
- Support contact: `support@streambeam.eu` is used on the privacy page and listings.
The mailbox or forward must exist before submitting.
- Screenshots of the real release build on each platform (no mockups).

## Google Play

### Publisher steps (cannot be automated)

1. **Create a Play Console developer account** at
<https://play.google.com/console/signup> as an **organization** (Argu B.V.),
one-time USD 25. Use the D-U-N-S number already used for Apple. An organization
account skips the rule that new *personal* accounts must run a closed test with
12 testers for 14 days before production. Identity verification takes days.
2. **Create the upload key** on your Mac: `scripts/create-android-upload-key.sh`.
Save the `.p12`, password and alias in Proton Pass, then set the four
`STREAMBEAM_KEY*` secrets and the `STREAMBEAM_UPLOAD_CERT_SHA256` variable it prints.
3. **Create the app** in Play Console: name `StreamBeam` (fall back to
`StreamBeam Remote Desktop` to match Apple), default language en-US, App, Free.
Package name is fixed by the first upload: `io.streambeam.streambeam`.
Keep **Play App Signing** on (Google generates the app-signing key).
4. **First AAB by hand**: the API cannot create the first release. Run
*Signed store candidates and uploads* with platform `android`,
`upload_store: false`, build number 3 or higher, download the AAB and upload
it to an **Internal testing** release in Play Console.
5. **Service account for CI uploads**: Google Cloud project, enable the Google Play
Android Developer API, create a service account with a JSON key, invite its
email in Play Console (Users and permissions) with release rights for this
app. Store the JSON as secret `GOOGLE_PLAY_SERVICE_ACCOUNT_JSON`. From then on
`upload_store: true` creates internal drafts.
6. **App Links**: copy the *App signing key* SHA-256 from Play Console
(Test and release, App integrity) into `site/.well-known/assetlinks.json`,
replacing the `REPLACE_WITH_…` entry, and deploy the site.

### App content forms (suggested answers, publisher confirms)

- **Privacy policy**: `https://streambeam.eu/privacy/`.
- **Ads**: no ads.
- **App access**: all functionality needs a second device running StreamBeam.
Give reviewers instructions plus the demo video; there is no login.
- **Target audience**: 18+ (avoids Families policy; the app is a general tool).
- **Content rating (IARC)**: utility, no user-generated content shared publicly,
no violence etc. Answer "yes" only to "users can interact/exchange content"
if the questionnaire counts device-to-device screen sharing; that usually
stays Everyone/PEGI 3.
- **Data safety**: no data collected or shared by StreamBeam itself. Data flows
only device-to-device on the LAN, end-to-end encrypted, not to the developer;
Google's guidance excludes that from "collection". Disclose ML Kit if Google
still lists its diagnostics as collected by the SDK: "App info and performance:
diagnostics, collected, not shared, not optional, purpose analytics" is the
conservative answer. Encrypted in transit: yes. Deletion request: data is
deleted by uninstalling.
- **Foreground service declaration** (`FOREGROUND_SERVICE_MEDIA_PROJECTION`):
type *Media projection*, use case "the user shares their screen with their own
paired computer or phone". Needs a short video of starting screen sharing.
- **Accessibility API declaration** (`RemoteTouchService`): StreamBeam is *not*
an accessibility tool (`isAccessibilityTool` stays false). Purpose: let a paired
device the user approved control this phone remotely (taps, swipes, typing),
as TeamViewer/AnyDesk-style remote support. Point to the in-app prominent
disclosure shown before opening Accessibility settings. Needs a video showing
that disclosure, the consent, enabling the service and a remote tap.
This is the declaration most likely to be rejected; ship without remote
control first if review stalls (watching/sharing works without it).
- **Government / financial / health / news**: not applicable.

### Release path

Internal testing → closed testing (optional) → production with a staged
rollout. Preview APKs on GitHub use a different signer, so a phone with a
GitHub preview cannot upgrade to the Play build in place; uninstall first and
pair again.

## Apple App Store (iOS/iPadOS)

### Publisher steps

1. **App Store Connect API key** (Users and Access, Integrations, Team Keys,
role App Manager). Download the `.p8` once, save it with key ID and issuer ID in
Proton Pass, then set `APP_STORE_CONNECT_KEY_ID`, `APP_STORE_CONNECT_ISSUER_ID`,
`APP_STORE_CONNECT_PRIVATE_KEY`. The same key can serve macOS notarization
(`APPLE_NOTARY_*`). Without it, upload IPAs with Transporter by hand instead.
2. **Physical device check** via TestFlight: install, Local Network and camera
consent, pairing, moving video, audio, touch input.
3. **App Privacy** questionnaire: *Data Not Collected*. Device-to-device LAN
traffic that never reaches the developer is not "collected" under Apple's
definition.
4. **Age rating**: all "None" → 4+.
5. **Encryption**: `ITSAppUsesNonExemptEncryption` is now `false` in
`Info.plist`: the app only uses standard TLS 1.3/QUIC (rustls) to protect
user data, which falls under the mass-market exemption, so App Store Connect
stops asking per build. Confirm this answer as publisher; France distribution
needs no extra declaration for exempt use.
6. **Review notes**: the app needs a computer running StreamBeam on the same
network. Provide a demo video and offer a reachable test host or a call.
Apple rejects apps it cannot exercise (guideline 2.1), so this matters.
7. Screenshots: 6.9" iPhone and 13" iPad are required sizes.
8. Submit version 0.1.0 for review, manual release.

## Microsoft Store (Windows)

1. **Partner Center account** at <https://partner.microsoft.com/dashboard>,
company account for Argu B.V., signed in with a Microsoft Entra ID work account.
Company registration is free since May 2026 (it used to be USD 99), see
[Microsoft's announcement](https://blogs.windows.com/windowsdeveloper/2026/05/07/publish-to-microsoft-store-as-a-company-now-with-free-registration-and-faster-onboarding/).
Business verification can take days.
2. **Reserve the name** `StreamBeam` (Apps and games, New product, MSIX).
3. Copy Product identity values into repository variables
`WINDOWS_STORE_IDENTITY_NAME`, `WINDOWS_STORE_PUBLISHER`,
`WINDOWS_STORE_PUBLISHER_DISPLAY_NAME`.
4. Run *Desktop distribution candidates* with `windows-store` and an unused
version like `0.1.3.0`, run the Windows App Certification Kit on the MSIX,
then upload it in a submission.
5. Capability justification: the package declares `runFullTrust` (Flutter desktop
apps need it). Explain: "desktop streaming host that captures the screen and
injects input for the user's own paired devices".
6. Privacy policy URL, age rating (IARC questionnaire, utility), screenshots,
category Productivity/Utilities.

The MSIX leaves out the SYSTEM secure-desktop service (see DESKTOP_RELEASES.md).

## What the repo still needs before public launch

- Real screenshots per platform, and the two Play declaration videos.
- Physical acceptance on iPhone/iPad and on a clean Windows PC.
- Deployed `site/privacy/` and a working support address.
- Play app-signing fingerprint in `assetlinks.json`.
55 changes: 55 additions & 0 deletions scripts/create-android-upload-key.sh
Original file line number Diff line number Diff line change
@@ -0,0 +1,55 @@
#!/usr/bin/env bash
# Create the long-term Google Play *upload* key for StreamBeam and print the
# values to store in the password manager and GitHub secrets.
#
# Run on your own machine, never in CI. Nothing here is committed or uploaded.
# Google Play App Signing keeps the real app-signing key; this key only proves
# uploads come from you, and Google can reset it if it is ever lost.
#
# scripts/create-android-upload-key.sh [output-dir]
set -euo pipefail

out_dir="${1:-$HOME/streambeam-play-upload}"
alias_name="streambeam-upload"
keystore="$out_dir/streambeam-upload.p12"

command -v keytool >/dev/null || { echo "keytool not found (install a JDK, e.g. via Android Studio)" >&2; exit 1; }
[[ -e "$keystore" ]] && { echo "$keystore already exists; refusing to overwrite" >&2; exit 1; }

mkdir -p "$out_dir"
chmod 700 "$out_dir"
password="$(openssl rand -base64 30 | tr -d '/+=' | cut -c1-32)"

# PKCS12 uses one password for store and key.
keytool -genkeypair -v \
-storetype PKCS12 -keystore "$keystore" \
-alias "$alias_name" -keyalg RSA -keysize 4096 -validity 10000 \
-storepass "$password" -keypass "$password" \
-dname "CN=StreamBeam upload key, O=Argu B.V., C=NL" >&2
chmod 600 "$keystore"

sha256="$(keytool -list -v -keystore "$keystore" -storepass "$password" -alias "$alias_name" \
| awk -F': ' '/SHA256:/ {print $2; exit}')"
base64 < "$keystore" | tr -d '\n' > "$keystore.base64"
chmod 600 "$keystore.base64"

cat >&2 <<INFO

Created $keystore

1. Save in Proton Pass (one item, "StreamBeam Play upload key"):
- attach $keystore
- password: (printed below)
- alias: $alias_name
2. Add GitHub Actions secrets on the repository:
STREAMBEAM_KEYSTORE_BASE64 = contents of $keystore.base64
STREAMBEAM_KEYSTORE_PASSWORD = the password
STREAMBEAM_KEY_PASSWORD = the same password
STREAMBEAM_KEY_ALIAS = $alias_name
and repository variable
STREAMBEAM_UPLOAD_CERT_SHA256 = $sha256
3. Delete $keystore.base64 afterwards; keep the .p12 until the vault restore is tested.

INFO
printf 'password: %s\n' "$password" >&2
printf 'upload cert SHA-256: %s\n' "$sha256" >&2
Loading
Loading