Skip to content

Align app icon guidance and starter with the OctoSense family - #233

Merged
guofoo merged 1 commit into
mainfrom
feature/octosense-icon-authoring
Oct 21, 2026
Merged

guofoo merged 1 commit into
mainfrom
feature/octosense-icon-authoring

Conversation

@guofoo

@guofoo guofoo commented Oct 21, 2026 •

Copy link
Copy Markdown
Contributor

New apps currently inherit a starter icon with baked rounded corners, and the icon guide recommends padding that differs from the approved OctoSense family. Align new app artwork with the approved format: a 64-point square master, central 66% foreground, restrained illustrated objects and colors, and platform framing owned by the shell.

Update the icon-topic owner and its Chinese twin, root/template agent instructions, first-app guides, template READMEs and the starter SVG. Authors must replace the starter identity with a distinct app icon, declare one canonical bundle asset, and review 64/40/24 px and platform frames. Store apps retain their own artwork and do not enter OctoSense's built-in overlay. Admission compatibility, catalog data and published bundles are unchanged.

The visual system is pinned to the approved source from OctoSense PR #555. App Flow has a matching authoring/template update.

Validation:

  • Relative Markdown link checks: 0 broken, 0 pending; whitespace checks pass.
  • The SVG parses, uses a full-bleed square background without baked corners, is byte-identical to App Flow's starter, and has raster-measured foreground bounds within the central 66%.
  • Static macOS/Android/iOS frame previews were inspected at 64/40/24 px.
  • A current pinned Hub CLI was built from the OctoSense workspace. A disposable copy of the card starter passes icon file checks and retains only its expected entry/listing refusals. No screenshot placeholders were added.

Native UI and device rendering were not exercised for this documentation/template change. Design conformity remains a visual-review requirement, not a new gate refusal.

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