Users could download wrong architecture build (arm64 vs x64)

[sunnypatneedi]

Problem

Users could potentially download the incorrect architecture build from GitHub Releases, resulting in:

• Performance issues: x64 build running under Rosetta on Apple Silicon Macs (slower)
• Confusion: Non-technical users don't understand "Apple Silicon" vs "Intel" terminology
• Support burden: Users report app feeling slow or not working as expected

Evidence

Download analytics show architecture confusion is a real problem, with users frequently downloading the wrong build for their Mac.

Current State

GitHub Releases page shows both builds without guidance:

• Familiar-0.0.37-arm64.dmg (Apple Silicon)
• Familiar-0.0.37-x64.dmg (Intel)

Users must manually determine their Mac architecture and choose correctly.

Proposed Solution

Create a GitHub Pages landing page that:

1. ✅ Auto-detects Mac architecture and recommends the correct download
2. ✅ Improves brand perception for non-technical users with professional landing page
3. ✅ Guides onboarding with clear setup instructions, screenshots, and FAQ
4. ✅ Reduces support burden by handling common questions upfront
5. ✅ Auto-updates version on each release via GitHub Actions

Why not universal binary?

File size concerns - separate builds allow users to download smaller packages (~50% reduction).

Implementation

See PR #7 for the implementation:

• Static landing page with hero, features, how-it-works, system requirements, FAQ
• JavaScript architecture detection with fallbacks
• Dark mode support, responsive design
• GitHub Actions auto-updates version on release

Landing page will be live at: https://familiar-software.github.io/familiar/

Alternative Considered

• Universal binary: Rejected due to 2x file size increase
• Better labeling on Releases: Insufficient - users still confused
• Detection script on download: Requires hosting, more complex

Next Steps

1. Review PR Add GitHub Pages landing page with architecture detection #7
2. Enable GitHub Pages after merge (Settings → Pages → main branch, /docs folder)
3. Update README and documentation to point to landing page
4. Monitor download metrics to verify architecture confusion decreases

---

Related: PR #7

[Hyaxia]

replied to the PR you've created, thank you very much @sunnypatneedi !