ChipHarbor

Product design exploration

Three visual directions for open silicon tapeout.

ChipHarbor needs to feel like a trusted engineering platform, a low-friction ordering surface, and a transparent manufacturing tracker. These directions explore how those roles can share one product language.

Review directions Read conclusion

Generated concepts

Directions

01

Infrastructure Console

A calm B2B SaaS surface focused on template choice, price estimation, and order creation. It makes the commercial journey concrete without hiding the technical constraints.

  • Best fit for /templates, /pricing, and order setup.
  • Strongest elements: comparison table, calculator, service checklist.
  • Risk: can feel generic unless paired with a distinct voyage language.
Infrastructure Console UI direction with template comparison, pricing calculator, and order workflow.

02

Tapeout Voyage

A signature operational experience built around manufacturing visibility. The timeline, shuttle panel, and mask-layer progress turn an opaque foundry process into a readable journey.

  • Best fit for the brand-defining product language.
  • Strongest elements: voyage timeline, WIP status, mask-layer progress.
  • Implementation note: keep map and harbor cues subtle, not illustrative.
Tapeout Voyage UI direction with manufacturing timeline, next shuttle panel, and mask layer progress.

03

Developer Workbench

A logged-in dashboard for builders who need immediate status, signoff reports, required file checks, and order actions. It favors dense, predictable tooling over marketing composition.

  • Best fit for /dashboard and authenticated workflows.
  • Strongest elements: submissions table, inspector, report links.
  • Risk: too utilitarian for public pages, but ideal after login.
Developer Workbench UI direction with dashboard navigation, submissions table, checks, and tapeout voyage.

Recommendation

Use one product language, not one screen style.

Lead with Tapeout Voyage

Direction 2 should define ChipHarbor's identity. The strongest promise is not only cheaper tapeout, but visible progress from submission to delivered silicon.

Use Infrastructure Console for conversion

Direction 1 should shape public decision pages: templates, shuttles, pricing, services, and checkout. It helps users answer what to submit, when to join, and what it costs.

Use Developer Workbench after login

Direction 3 should shape the dashboard, where density is a feature. Users need tables, reports, file requirements, signoff state, payment state, and WIP status without extra storytelling.

Design system starter

Core UI rules

Palette

Ink Blue Pass Pending Fail

White and gray carry most surfaces. Blue is for navigation and primary actions; green, amber, and red are reserved for state.

Components

Prioritize tables, timelines, segmented controls, service checklists, shuttle panels, upload status, report links, and compact inspector panels.

Brand restraint

The harbor metaphor should appear as route lines, coordinates, and voyage naming. Avoid literal ship imagery in production UI except for small template marks.