Icon design
The application icon was chosen among five concepts drawn in code. This document records the concepts, the evaluation, the construction of the chosen one and the assets that ship.
All artwork is generated by Scripts/icon.swift with Core Graphics (swift Scripts/icon.swift <outdir>,
default design/icon). There is no hand-edited source file: the script is the source.
The five concepts
All five share the same plate (see Construction) so that only the mark differs.
| 1. Storage ring with a swept quarter | 2. Treemap | 3. Disk sector |
|---|---|---|
| 4. Layers | 5. Monogram with a notch | Final icon |
|---|---|---|
| # | File | Idea |
|---|---|---|
| 1 | concept-1-storage-ring-sweep.png |
The ORIX "O" as a storage ring. Three segments of decreasing length hold data; the last quarter has been swept and is only a faint trail, with a spark where the sweep ended |
| 2 | concept-2-treemap.png |
A geometric treemap of five blocks, with one emptied cell drawn as a dashed outline holding a spark |
| 3 | concept-3-disk-sector.png |
A disk with one sector cleared and a hub in the centre |
| 4 | concept-4-layers.png |
Three stacked storage sheets with a spark on the top one |
| 5 | concept-5-monogram-notch.png |
A plain ORIX ring with a clean notch and a dot |
Evaluation
The ratings below are a design judgement made on the rendered files at 1024, 320, 32 and 16 pixels. They are not the result of a user study, and contrast was judged by eye, not measured.
| Criterion | 1. Ring sweep | 2. Treemap | 3. Disk sector | 4. Layers | 5. Monogram notch |
|---|---|---|---|---|---|
| Originality | High: the segmented ring with a swept gap is specific to this product | Medium: block grids are common for disk tools and dashboards | Low: reads as a generic pie chart | Low: the stacked-layers glyph is widely used | Medium: a notched ring is distinctive but abstract |
| Recognisability (storage and cleaning) | High: used segments, then an emptied part | High for "storage map", weaker for "cleaning" | Medium: "a part removed", but also "chart" or "timer" | Low: reads as layers or a stack, not as disk space | Low: reads as a letter or a progress ring |
| Small-size readability | Medium: at 16 px the segments merge into a ring and the trail disappears; the gap and the spark remain | Medium: blocks hold, the dashed cell is lost | High: one shape, one cut | High: three flat shapes | High: one stroke and a dot |
| Balance | High: centred ring; the gap gives direction without tilting the mark | Medium: weight sits in the upper-left block | High: centred and symmetric apart from the cut | High: centred and symmetric | Medium: the dot pulls to the upper right |
| Brand consistency | High: the "O" of ORIX, in the teal-to-indigo family colours | Medium: family colours, no "O" | Medium: circular, single colour | Low: no link to the ORIX mark | High: the "O" itself, in the family gradient |
| Contrast on the dark plate | High: light teal, cyan and indigo segments, white spark | High: saturated blocks | Medium: one mid-tone blue; the cleared sector merges with the plate | Medium: translucent lower sheets | High: bright gradient stroke |
Why concept 1 was chosen
- It is the only concept that carries all three ideas in one shape: the ORIX "O", storage in use (the segments) and the result of cleaning (the swept quarter).
- It shows the outcome, free space, rather than a tool or an alarm. This matches the tone of the product:
factual, no urgency (see
brand-guidelines.md). - Concept 2 describes the Storage Map feature well but says "analysis" more than "reclaim", and its grid is the least distinctive silhouette next to other disk utilities.
- Concepts 3 and 4 are legible but generic.
- Concept 5 is the closest to a pure family monogram; it would suit a family mark but does not say what this application does.
Accepted weakness: concept 1 is the most detailed of the five and loses the most at 16 pixels. The ring, the gap and the spark survive; the three separate segments and the trail do not.
Construction
The canvas is 1024 by 1024 pixels, sRGB, with transparency. Coordinates below are in canvas pixels with the origin at the bottom left, as in Core Graphics.
Plate
| Element | Value |
|---|---|
| Shape | Rounded square, 824 by 824, origin (100, 100), centred on the canvas |
| Corner radius | 185.4 |
| Fill | Vertical gradient, #1B2340 at the top to #070A16 at the bottom |
| Drop shadow | Offset (0, -10), blur 22, black at 35 % |
| Glow | Radial gradient of #2DD4BF, 28 % at the centre (512, 540) to 0 % at radius 430, clipped to the plate |
| Edge highlight | 3-pixel stroke of white at 10 % along the plate outline, clipped to the plate |
The 824-pixel plate on a 1024 canvas leaves a 100-pixel margin on each side for the shadow, which is the usual macOS application icon grid.
Mark (concept 1)
Angles are in degrees, clockwise from 12 o'clock. The ring is centred at (512, 512) with radius 250.
| Element | Angles | Stroke width | Caps | Colours |
|---|---|---|---|---|
| Track | 0 to 360 | 20 | butt | white at 7 % |
| Segment 1 | 14 to 112 | 118 | round | #5EEAD4 to #14B8A6 |
| Segment 2 | 142 to 206 | 118 | round | #22D3EE to #0891B2 |
| Segment 3 | 236 to 268 | 118 | round | #818CF8 to #5B5BF0 |
| Swept trail | ten dashes of 3.4 degrees starting at 290, one every 6.2 degrees | 20 | round | #CCFBF1, opacity rising from 16 % to 83.5 % |
| Spark | on the ring at -6 degrees | four-point star, half-size 62 | white | |
| Centre spark | (512, 512) | four-point star, half-size 30 | #5EEAD4 at 90 % |
The segments span 98, 64 and 32 degrees: each is shorter than the one before, so the ring reads as "emptying" in the clockwise direction. Each segment is filled with a diagonal linear gradient across the bounding square of the ring. The star is drawn with four quadratic curves whose control points sit at 22 % of its half-size, which gives the concave sides.
Assets generated
| File | Pixels | Use |
|---|---|---|
design/icon/concept-1-storage-ring-sweep.png … concept-5-monogram-notch.png |
1024 | Concept renderings |
design/icon/ORIXClean-1024.png |
1024 | Final icon; the script draws concept 1 a second time under this name |
App/Resources/Assets.xcassets/AppIcon.appiconset/icon_1024.png |
1024 | 512 pt @2x |
…/icon_512.png |
512 | 512 pt @1x, 256 pt @2x |
…/icon_256.png |
256 | 256 pt @1x, 128 pt @2x |
…/icon_128.png |
128 | 128 pt @1x |
…/icon_64.png |
64 | 32 pt @2x |
…/icon_32.png |
32 | 32 pt @1x, 16 pt @2x |
…/icon_16.png |
16 | 16 pt @1x |
docs/assets/icon.png |
256 | Documentation |
docs/assets/icon-512.png |
512 | Documentation |
Seven PNG files fill the ten slots of the macOS AppIcon set (Contents.json). Scripts/icon.swift writes
only the 1024-pixel files; the step that produced the smaller sizes is not scripted in the repository, and the
small sizes are scaled versions of the same drawing, not separately simplified artwork.
The same plate colours and the tagline are reused on the disk-image background drawn by
Scripts/dmg-background.swift (660 by 420 points at 2x).
What was not produced
- No Icon Composer layered icon. The layered format introduced for macOS 26 and later (separate layers with system-applied material, tint and appearance variants) was not produced. The application ships the classic asset-catalogue icon: flat PNGs with the plate, shadow and highlight baked in. How the system presents such an icon next to layered icons on macOS 26 and 27 has not been reviewed beyond the development machine.
- No dark, tinted or clear variants. There is one rendering.
- No size-specific drawings. A simplified 16- and 32-pixel version (ring, gap and spark only) would address the small-size weakness noted above.
- No vector master (SVG or PDF) other than the generator script.
Regenerating
swift Scripts/icon.swift design/iconThis rewrites the five concepts and ORIXClean-1024.png. The asset-catalogue sizes and the two files in
docs/assets/ must then be regenerated from ORIXClean-1024.png by hand.