Repository navigation
Align app icon guidance and starter with the OctoSense family - #233
Merged
Merged
Conversation
This was referenced Oct 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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:
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.