[Idea]: Let users customize the T3 Code app icon without leaving official updates

[lhhdh]

Problem

T3 Code currently ships a fixed app icon for each channel. Users who want a personal icon have to modify the installed bundle, use a launcher shortcut, or maintain a custom-signed build. Those workarounds are fragile:

• Editing the installed app can be overwritten by an update and may interfere with signing or platform identity.
• A shortcut can change the launcher image, but the app switcher and other system surfaces still show the official icon.
• A personal build requires rebuilding after every upstream release, which makes users choose between customization and reliable official updates.

I would like an officially supported way to personalize the app icon while continuing to use the normal App Store / TestFlight / desktop update channels.

Proposed behavior

Add an Appearance → App icon setting, with the official icon as the default. The selected icon should be stored in T3 Code user data and reapplied after an update, rather than requiring a modified app bundle.

Possible scope per platform:

• macOS/desktop: allow choosing a local image and apply it to the app icon through the supported Electron/macOS APIs. Keep the app's bundle identifier, signing identity, and updater unchanged.
• iOS/iPadOS: offer a curated set of declared alternate icons using CFBundleAlternateIcons / UIApplication.setAlternateIconName. Arbitrary imported icons may need to remain a later extension because iOS only switches among assets compiled into the app.
• Android: if practical, let the launcher icon use a user-selected icon/alias while keeping the same installation and update identity.
• Web: no app-binary change is required; the existing web branding can remain separate.

The important constraint is that changing appearance must not fork the application identity or disable updates.

Why this matters

Some users run several automation tools side by side or want better visual recognition on the Dock/Home Screen. A supported icon preference removes the need for forks and brittle post-update scripts without changing any T3 Code functionality.

Suggested first increment

Ship the desktop/macOS picker first because it can be implemented without changing the release binary or updater. Then evaluate a smaller built-in alternate-icon set for iOS/Android if that fits product scope.

Questions for maintainers

• Is runtime icon customization on desktop something you would accept?
• For mobile, would a small curated alternate-icon set be preferred over arbitrary imported images?
• Should this live under global Appearance settings or a separate Personalization section?