Allow customizing Remote UI PWA name and icon per machine

[zainfathoni]

This was generated by AI during triage.

Motivation

When Tycho is installed as a PWA from multiple machines, each installed app currently looks the same. This makes it hard to distinguish which machine/session a PWA window belongs to.

I would like a lightweight way to customize the Remote UI/PWA identity per local Tycho installation, so machines can have distinct app names/icons.

Proposed approach

Add optional Remote UI config:

remote_ui:
  app_name: "Tycho — Framework Laptop"
  short_name: "Tycho FW"
  icon:
    emoji: "🟣"
    background: "#1f1b2e"

Tycho would use these values when serving the Remote UI web app manifest and icon assets.

Suggested behavior:

• Preserve the current Tycho name/icon when config is absent.
• Use remote_ui.app_name and remote_ui.short_name in the manifest when present.
• Generate a simple SVG icon from remote_ui.icon.emoji and remote_ui.icon.background.
• Reference the generated icon from the manifest with a config-derived cache-busting version/hash so PWA installs pick up identity changes predictably.
• Show the configured app name subtly in the Remote UI header, so browser tabs and non-installed sessions are distinguishable too.

Non-goals for the first implementation

• Uploading icons.
• Cropping/resizing arbitrary images.
• Supporting arbitrary icon file paths.

Emoji + background color should be enough for the initial use case: distinguishing installed PWAs across machines.

Rationale

Keeping this under remote_ui scopes the feature to browser/PWA behavior. Generating an SVG from an emoji and background color avoids image storage and processing complexity while solving the main problem.

[firewalker06]

This is a good idea. The use case is clear: when Tycho is installed as a PWA from multiple machines, the installed apps need a visible machine identity.

One concern with the proposed icon approach is relying on SVG-only generated icons. SVG is useful for the browser favicon/manifest path, but installed PWA icon behavior varies across platforms, launchers, and cached installs. To keep this robust, I would recommend supporting both SVG and PNG outputs from the start:

• generate or serve an SVG for lightweight favicon/browser use
• also provide PNG variants for the existing PWA icon sizes, especially 192x192, 512x512, and maskable 512x512
• include the config-derived version/hash in all icon URLs so identity changes can invalidate cached manifest/icon assets

The first milestone could still stay small: configurable remote_ui.app_name, remote_ui.short_name, and generated icon assets from emoji/background, while preserving the current Tycho defaults when no config is present.