Soundhaven Meeting #1 - Wiki

Meeting Notes

Who: Andrea Duran and Mason Earl
Where: Sunset Coffee
Date: 3.26.26
Time: About 11:00 AM to 12:00 PM
Length: About one hour
Context: A lot was covered quickly; this page simplifies the next steps

Fastest Path Forward (Recommended)

The fastest route is web first: get a live product online, collect feedback, then decide if native iOS should be next.

Core stack links: Cursor, React, GitHub, Vercel.

Decision: Need traction quickly?

Yes -> Web first (recommended)

1) Cursor + React

↓

2) Create GitHub repo

↓

3) Deploy on Vercel

↓

4) Connect domain + launch

Need App Store now?

iOS path (more setup + more cost)

↓

Apple Developer Program

↓

Xcode + App Store Connect

Web first cost: Domain + hosting, usually lower initial cost.
iOS first cost: Apple Developer Program + App Store process overhead.
Speed: Web launches faster; iOS usually takes more setup and review time.

Path A: Get a Product Live Fast (Web First)

If the goal is to get momentum and a working product quickly, this is the best first path.

Build in Cursor: Keep using React and ship small updates often.
Use GitHub: Save versions, create backups, and track progress cleanly.
Deploy with Vercel: Push to GitHub and get a live URL fast.
Buy a domain: Use Squarespace or Cloudflare, then connect it to Vercel.
Domain ideas: Try `soundhaven.io`, `soundhaven.com`, or `soundhavenai.com`.

GitHub: Brass Tacks

Create one repo for Soundhaven.
Commit changes after each working milestone (small and clear).
Use simple commit messages like: "add onboarding flow" or "fix audio player bug".
Push daily so work is always backed up.
When stuck, ask Cursor directly: "How do I create a branch?" or "How do I resolve this merge?"

DNS Setup (Simple Version)

Buy the domain in Squarespace or Cloudflare, then point it to your Vercel project.

Step 1: Buy domain (for example `soundhaven.io`).
Step 2: In Vercel Domains, add your domain.
Step 3: In your DNS provider, create the DNS records Vercel tells you to add.
Step 4: Wait for DNS propagation, then verify in Vercel.
Step 5: Turn on HTTPS (Vercel handles this once DNS is correct).
Step 6: Re-test the live URL and share it for feedback.

Cursor tip: ask "Walk me through connecting my domain DNS to Vercel step-by-step" and paste your registrar + current DNS screen when needed.

Path B: If You Are Set on iOS App Store First

Join Apple Developer Program: Required to publish to the App Store.
Install Xcode: Learn basic project setup, simulator testing, and signing.
Test core permissions: Audio, notifications, and any account flows.
Archive build in Xcode: Upload to App Store Connect.
Complete App Store Connect: App info, screenshots, privacy details, age rating.
Submit for review: Respond quickly to review notes and resubmit if needed.
Then iterate: Keep building in Cursor and ship updates in versions.

Simple Product Workflow (From the Sketch)

The whiteboard flow looks like a lightweight loop: onboarding, a short guided session, then a quick self-check before repeating.

1) Onboarding
Quick setup + explain value

↓

2) Pre-Session Check
Stress level (1-10) + choose soundscape

↓

3) Session
Focused audio run (5-15 minutes)

↓

4) Post-Session Check
Self-rate again + short reflection

↓

5) Save Progress
Store result and suggest next action

Loop: "Go Again" returns user to Step 2 with one tap

Onboarding: Help the user start quickly and understand the value.
Session: Run a focused soundscape session (around 5-15 minutes).
Close: Ask for a simple self-rating (for example 1-10).
Loop: Offer "go again" and keep the experience frictionless.
Gap filled: Add "save progress + short note" so users can track what works.

Reference App

A strong benchmark for emotional check-ins and stress support is How We Feel. Study how it guides users through small daily actions without overwhelming them.

Canva + App Store Preview Assets

Canva is a strong low-cost option for creating App Store screenshots, preview layouts, and basic product mockups.

How to Resize in Canva (Fast Version)

Open Canva -> Create a design -> Custom size.
Set dimensions in pixels, based on the current App Store Connect screenshot requirements.
Create one master layout style, then duplicate and swap each screen image.
Export PNG files and upload to App Store Connect.

Minimum-first strategy: ship with the minimum required screenshot set first, get the app submitted, then iterate with stronger visuals in the next version.

Haptic Feedback for Breathing Exercises

Yes, this is a great feature idea. Your instinct is right: haptics are more limited on the web, especially on iPhone Safari.

Web reality: There is no reliable full haptics API across all browsers/devices. Most web apps use `navigator.vibrate()` and get best results on Android.
iPhone web limitation: iOS Safari support is limited, so vibration/haptic calls may not work the way you want for guided breathing.
Permission model: Web haptics generally do not use a pop-up permission like camera/mic; trigger haptics only after a user tap/click and provide fallback UI if unsupported.
Best web fallback: Pair subtle audio cues + animation timing rings when haptics are not available.

Quick web check pattern: test `if ("vibrate" in navigator) { navigator.vibrate(50); }` after a user gesture.

If She Goes iOS Route (Stronger Haptics)

Expo (React Native): install `expo-haptics`, import `* as Haptics from "expo-haptics"`.
React Native (bare): install `react-native-haptic-feedback`, import `ReactNativeHapticFeedback` from `"react-native-haptic-feedback"`.
Capacitor hybrid app: install `@capacitor/haptics`, import `{ Haptics, ImpactStyle }` from `"@capacitor/haptics"`.
Native iOS (Swift): use `UIImpactFeedbackGenerator` and advanced patterns with Core Haptics (`CHHapticEngine`).

If haptics are a core part of the breathing experience, a native iOS path (or React Native/Capacitor wrapped app) will be more dependable than a pure web app.

Next Moves (Do These First)

Pick Path A (web first) or Path B (iOS first) for the next 2 weeks.
Set one milestone: "working first user flow" by end of week.
Ship one tiny improvement every day to keep momentum.

Schedule a Time with Mason

If Andrea wants a follow-up session, she can book directly here.

Schedule a time with Mason

Final Advice: Iterate Fast

Last thing: move quickly and do not overthink early versions. A lot of this can be sped up by copying context into Cursor and asking it to implement one clear step at a time.

Use Cursor as an execution engine: Paste requirements and ask "integrate this into the app" or "build this screen now."
Break work into tiny tasks: Build one flow, test it, then ship and repeat.
Ask speed-focused prompts: "What is the fastest way to ship this?" and "Give me the minimum viable version first."
Templates help: Explore Figma Community for UI kits, app templates, and visual ideas.
Free media: Use Pexels for photos/videos and LottieFiles Free Animations for lightweight motion assets.

Build momentum first, polish second. Shipping fast feedback loops will beat perfect planning every time.

Soundhaven - Meeting #1