# ChipHarbor Multi-Page Prototype Directions Comparison

This comparison reviews six complete static site directions for ChipHarbor:

- Apple inspired
- Vercel inspired
- Google inspired
- Microsoft inspired
- GitHub inspired
- Uber inspired

Each direction now covers the requested sitemap: Landing, About, Shuttles, Templates, Pricing Calculator, and Dashboard. Uncertain operational data is mocked for prototype review, including shuttle capacity, WIP dates, pricing rules, coupon codes, user submissions, order IDs, and payment state.

## Executive Conclusions

### Most Suitable For Brand Building

**Apple inspired**

Apple is still the strongest brand-building direction. The multi-page version makes ChipHarbor feel like a premium, guided infrastructure product rather than a raw tapeout form. The landing page is especially strong for the mission-level idea: `Ship Your Chip. Set Sail with Open Silicon.`

Main risk: the restrained style can understate engineering proof unless production versions add real chip, board, signoff report, pricing, and shuttle evidence.

### Most Suitable For Conversion

**Vercel inspired**

Vercel is the strongest conversion direction. The full site makes the path from landing to template comparison, pricing, dashboard submission, and order binding feel direct. It communicates ChipHarbor as a build pipeline with visible state.

Main risk: it may feel too software-platform-like for users who need more physical manufacturing reassurance.

### Most Suitable For Developer Or Technical Audiences

**GitHub inspired**

GitHub is strongest for open-source developers, OSOC learners, and technical contributors. Repo-like panels, checks, status pills, file requirements, and WIP timelines map naturally to Submission, Signoff, Templates, and Tapeout Voyage.

Main risk: the developer workflow metaphor can underplay foundry, packaging, board, and delivery credibility without real hardware proof.

### Most Suitable For Enterprise Customers

**Microsoft inspired**

Microsoft is strongest for enterprise, lab, and commercial prototype evaluation. The dashboard and workflow pages feel like a repeatable operational workspace, with clear objects, status states, and order visibility.

Main risk: the enterprise tone may feel too corporate for open silicon community storytelling.

### Most Accessible Broad-Audience Direction

**Google inspired**

Google is the clearest broad-audience direction. It makes complex concepts like MPW/MPC, shuttles, signoff, pricing, and dashboard workflows approachable without losing the core mechanics.

Main risk: expert semiconductor users may need denser specs and proof earlier.

### Most Differentiated But Highest Risk

**Uber inspired**

Uber is the most differentiated. It uses an operational dispatch and logistics metaphor to make shuttles, lanes, WIP, and delivery status feel concrete and active.

Main risk: it can feel too transactional or abstract unless semiconductor specificity is reinforced.

## Recommended Directions To Refine Next

1. **Vercel inspired** as the primary conversion prototype.
   - Best for driving users from landing to template, price estimate, and dashboard submission.
   - Strong fit for technical builders who expect visible system state.

2. **Apple inspired** as the brand-building prototype.
   - Best for mission, premium trust, and broad first impression.
   - Useful counterweight to Vercel's sharper developer-tool feel.

Secondary candidate: **GitHub inspired** if the first launch focuses on open-source chip builders, OSOC learners, and technical communities.

## Decision Matrix

Scores use a 1-5 scale. Higher is better, except implementation complexity where 5 means harder to implement and maintain.

| Direction | Brand Expression | Conversion Efficiency | Information Clarity | Visual Differentiation | Implementation Complexity | Mission Fit |
|---|---:|---:|---:|---:|---:|---:|
| Apple inspired | 5 | 4 | 4 | 4 | 4 | 5 |
| Vercel inspired | 4 | 5 | 5 | 3 | 3 | 4 |
| Google inspired | 4 | 4 | 5 | 3 | 3 | 5 |
| Microsoft inspired | 4 | 4 | 5 | 3 | 3 | 4 |
| GitHub inspired | 4 | 4 | 5 | 4 | 3 | 5 |
| Uber inspired | 3 | 4 | 4 | 5 | 4 | 4 |

## Page Coverage

All six directions include:

- Landing page with required notice, exact headline, CTAs, metrics, generated wafer/layout media, workflow, shuttles, templates, ecosystem, incentives, dashboard preview, final CTA, and footer.
- About page with Mission, Vision, and Values.
- Shuttles page with open/planned/historical shuttles and WIP tracking.
- Templates page with Ark, Freighter, Cruise, OSOC, MPW/MPC explanation, and animated schematics.
- Pricing Calculator page with shuttle/template/area/services/coupon controls and live price preview.
- Dashboard page with My Designs, My Orders, Submit Design wizard, Create Order wizard, Signoff status, payment state, and Tapeout Voyage WIP.

## Direction Notes

### Apple Inspired

- **Methodology:** premium restraint, large type, calm sequencing, focused copy, quiet product surfaces.
- **Best use:** brand trust and mission-level storytelling.
- **Risk:** can look too polished and light on engineering proof.
- **Refine:** add real chip/board imagery, sample signoff reports, final pricing, and exact template constraints.

### Vercel Inspired

- **Methodology:** developer platform, high contrast, compact hierarchy, visible state, pipeline clarity.
- **Best use:** conversion and technical product mechanics.
- **Risk:** can feel more like software deployment than semiconductor manufacturing.
- **Refine:** add hardware proof, foundry/process documentation, and warmer community signals.

### Google Inspired

- **Methodology:** approachable product clarity, task-first IA, whitespace, chips, guided controls.
- **Best use:** broad audience onboarding across hobbyists, students, labs, and startups.
- **Risk:** may feel too high-level for expert semiconductor users.
- **Refine:** add denser template specs, exact pricing rules, report examples, and docs links.

### Microsoft Inspired

- **Methodology:** enterprise productivity, modular workspace, operational tables, dashboard credibility.
- **Best use:** enterprise customers, labs, commercial prototypes, repeatable programs.
- **Risk:** can feel too corporate for the open silicon community.
- **Refine:** add community proof, contributor stories, real lab imagery, and more open-source ecosystem context.

### GitHub Inspired

- **Methodology:** developer infrastructure, repo/check/timeline metaphors, inspectable panels.
- **Best use:** open-source technical audiences and OSOC learners.
- **Risk:** may underplay physical manufacturing and delivery.
- **Refine:** add wafer/package/board imagery and deeper Tapeout Voyage evidence.

### Uber Inspired

- **Methodology:** operational marketplace, dispatch/lane/status rhythm, logistics clarity.
- **Best use:** making shuttle movement, WIP, and delivery feel concrete.
- **Risk:** can feel transactional or metaphor-heavy.
- **Refine:** add technical validation artifacts and stronger semiconductor-specific proof.

## Mock Data Caveat

The prototypes intentionally mock uncertain data:

- Shuttle schedules, capacity, chip IDs, user designs, and WIP dates.
- Pricing formulas, service fees, exchange rates, and coupon codes.
- Signoff outcomes, payment states, uploaded files, and order records.
- Incentive eligibility and OSOC support rules.

Before production, these values should be replaced with authoritative product, engineering, operations, finance, and legal rules.