Skip to content

Rebrand mobile app surfaces from T3 Code to TritonAI Code #24

Open
Open
Rebrand mobile app surfaces from T3 Code to TritonAI Code#24
Labels
area:t3codeIssue belongs in the T3 Code app area.automation:declinedIssue autopilot decided not to pursue this automatically.automation:needs-humanAutomation needs a maintainer decision or manual follow-up.automation:triagedReviewed by issue autopilot.

Description

@dbalders
dbalders
opened on Jun 26, 2026

Scope

The mobile app under apps/mobile still has upstream T3 Code branding and release metadata in several user-facing and distribution-facing surfaces. Before we use or distribute it in the TritonAI setup, rebrand the mobile app surfaces intentionally.

This issue is only for the mobile app rebrand. It does not cover remote host access, relay/tunnel architecture, Tailscale, or public-web connectivity.

Known surfaces to check

  • apps/mobile/app.config.ts
    • App display names: T3 Code, T3 Code Dev, T3 Code Preview
    • URL schemes such as t3code / t3code-dev
    • Bundle/package identifiers such as com.t3tools.t3code*
    • EAS owner/project metadata
  • apps/mobile/eas.json
    • App Store Connect / submit metadata
  • apps/mobile/README.md
    • Any install, build, or product references that still say T3 Code
  • Mobile icons, splash assets, widget/live-activity labels, notification labels, and scanner/pairing copy
  • Client presentation metadata and tests that expose labels such as T3 Code Mobile or related encoded client labels

Decisions needed

  • Decide whether the mobile bundle/package identifiers should be renamed now, or kept for continuity while only user-facing labels change.
  • Decide the final mobile product name: likely TritonAI Code or TritonAI Code Mobile.
  • Decide whether preview/dev variants should use TritonAI Code Dev and TritonAI Code Preview.

Acceptance criteria

  • The mobile app no longer shows upstream T3 Code branding in user-facing app surfaces.
  • Build/distribution metadata is either rebranded or explicitly documented as intentionally retained.
  • Mobile pairing/client labels match the TritonAI naming convention.
  • Relevant checks pass:
    • vp run --filter @t3tools/mobile typecheck
    • vp run --filter @t3tools/mobile test
    • APP_VARIANT=development vp run --filter @t3tools/mobile config:dev
    • vp run lint:mobile

Activity

  1. dbalders
    added
    area:t3codeIssue belongs in the T3 Code app area.
    automation:declinedIssue autopilot decided not to pursue this automatically.
    automation:needs-humanAutomation needs a maintainer decision or manual follow-up.
    automation:triagedReviewed by issue autopilot.
    on Jun 26, 2026

  2. dbalders commented on Jun 26, 2026

    @dbalders
    dbalders
    on Jun 26, 2026
    OwnerAuthor

    Issue Autopilot Review

    Status: Not pursuing automatically
    Issue: #24
    Pursue: no
    Targets: t3code
    Confidence: high

    Triage

    The issue is scoped to the T3 Code mobile app and belongs in t3code, but it explicitly depends on product/distribution decisions: final mobile product name, dev/preview naming, and whether bundle/package identifiers should change or be intentionally retained. Those choices affect App Store continuity and release metadata, so automated implementation should wait for owner confirmation.

    Implementation Plan

    Do not start implementation yet. Once decisions are confirmed, update apps/mobile branding surfaces, pairing/client labels, distribution metadata or retention documentation, and run the listed mobile checks.

    Acceptance Criteria

    • Owner confirms final mobile product name.
    • Owner confirms dev and preview variant names.
    • Owner confirms whether bundle/package identifiers and EAS/App Store metadata should be renamed now or retained with documentation.
    • After confirmation, mobile user-facing surfaces no longer expose upstream T3 Code branding.
    • Relevant mobile typecheck, test, config, and lint commands pass or failures are documented.

    Risk Notes

    • Renaming bundle/package identifiers can create a new app identity and affect App Store/Play Store continuity.
    • EAS/App Store Connect metadata may require credentials or release-owner coordination.
    • Blindly changing URL schemes or client labels may break pairing/deep-link compatibility if corresponding server/client expectations are not updated.

    Human review needed: Owner needs to resolve naming and app identifier decisions before automated code changes begin.

    Next Step

    No implementation is running from this triage result.

    Automated issue autopilot review updated 2026-06-26T23:07:43+00:00.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:t3codeIssue belongs in the T3 Code app area.automation:declinedIssue autopilot decided not to pursue this automatically.automation:needs-humanAutomation needs a maintainer decision or manual follow-up.automation:triagedReviewed by issue autopilot.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions