# LifeLoveMe Current Status — May 8, 2026

## 1. Purpose of this document

This document captures the current working state of LifeLoveMe before further development. Deployment testing revealed how important checkpoints, local-first testing, and controlled deployment flow are for preserving stability and avoiding accidental regressions.

## 2. Current development principle

Development must first work on the Mac local server before deployment.  
Deployment should only happen after local development works, a checkpoint is created, the deploy folder is rebuilt, and the deploy folder is tested locally.

## 3. Current local testing URLs

Use full local-network URLs because they work on both Mac and iPhone.

### Development server

- `http://192.168.254.207:8770/home/index.html`
- `http://192.168.254.207:8770/apps/rcm-hub/index.html`
- `http://192.168.254.207:8770/apps/rcm-explorer/index.html`
- `http://192.168.254.207:8770/apps/experience-player/index.html`

### Deploy test server

- `http://192.168.254.207:8780/home/index.html`
- `http://192.168.254.207:8780/apps/rcm-hub/index.html`
- `http://192.168.254.207:8780/apps/rcm-explorer/index.html`
- `http://192.168.254.207:8780/apps/experience-player/index.html`

**Note:** The IP address is currently `192.168.254.207` and usually remains stable on the current Wi-Fi, but it can change if the network changes.

## 4. What is working

- Home, Life, Love, Me pages work locally.
- Books page is dynamic from Excel -> JSON.
- Poems page is dynamic from Excel -> JSON.
- Creations page is dynamic.
- RCM Hub exists as the visual front door.
- RCM Explorer works.
- RCM Explorer search works.
- Theme search now works.
- Grouped results work.
- Related AIR episodes appear uniquely.
- Clicking Play on a related AIR episode scrolls the left pane to the matching passage and highlights it.
- RCM MP3 files can play locally.
- The public Netlify test site opened successfully.
- Direct public MP3 path worked at:
  - `https://delicate-beignet-c9686f.netlify.app/apps/experience-player/media/AIRRamayan_mp3/EPI-10.mp3`

## 5. What is unstable or needs caution

- Chrome showed issues with wellness narration and slider, while Safari worked.
- Wellness narration/Test TTS behavior needs browser-specific checking.
- Experience Player is sensitive because it handles both Wellness and RCM.
- The RCM audio path mismatch was found:
  - working path: `/apps/experience-player/media/AIRRamayan_mp3/EPI-XX.mp3`
  - non-working path: `/apps/experience-player/media/rcm/audio/AIRRamayan_mp3/EPI-XX.mp3`
- The deploy folder was accidentally incomplete during testing.
- `prepare_deploy.sh` needs repair and validation before future deployment.
- Netlify deployment should be paused until local app is fully stable.

## 6. Do not deploy yet

Do not deploy again until:

- Mac local development server on `8770` passes tests.
- Safari and Chrome are checked.
- iPhone Safari is checked.
- A working checkpoint copy is created.
- `deploy/web_public` is rebuilt.
- `deploy/web_public` is tested on `8780`.
- Deployment validation passes.

## 7. Immediate next development priorities

### A. Stabilization

- Create working checkpoint copies.
- Repair `prepare_deploy.sh`.
- Add `validate_deploy.sh`.
- Add deployment checklist.

### B. RCM Explorer

- Add Open Full Prasang.
- Add Show Surrounding Lines.
- Add result filters by Kand/Prasang/Episode.
- Add Random Reflection.
- Add Sundarkand mode.
- Add Copy for WhatsApp.

### C. RCM Hub

- Make all cards functional.
- Add Active/Coming Soon badges.
- Add Start Here path.
- Add Today's Reflection.

### D. Experience Player

- Keep Wellness and RCM controls separate.
- Add separate RCM audio progress slider.
- Preserve wellness slider and narration.
- Add audio diagnostics.
- Do not touch this file unless necessary.

### E. Prashnavali

- Planned future feature.
- 15x15 Ram Shalaka grid.
- Result chaupai.
- Meaning and reflection.
- Link to RCM LineID.
- Play related AIR episode.
- Read full Prasang.

## 8. Deployment plan later

- `beta.lifeloveme.com` remains the intended beta domain.
- Deploy only from `deploy/web_public`.
- Do not deploy private books.
- Do not deploy the full LifeLoveMe project folder.
- Use Netlify after local and deploy-folder tests pass.

## 9. Lessons learned

A working local app should not be rushed to deployment. Deployment needs its own checklist and must be treated as a distinct, disciplined phase rather than an extension of coding. A copy/checkpoint should always be created before major changes so recovery is immediate when regressions appear. Browser differences are real and must be tested intentionally across Safari, Chrome, and iPhone Safari before release decisions are made. Most importantly, the process itself should reduce memory burden: the system should carry the sequence, status, and safeguards so progress does not depend on fragile recall. In that sense, LifeLoveMe is not only an app ecosystem but also an external memory and process system for reliable, repeatable development.

“Before moving forward, we must preserve what works, document what changed, and proceed only from a known stable checkpoint.”