⛪ MTC Counter - MarThoma Church Attendance Tracker

A modern, bilingual (English/Malayalam) Progressive Web App for tracking church service attendance.

✨ Features

• 📊 Real-time Counter - Track male/female attendance
• 👥 Co-Celebrants Support - Optional field for multiple celebrants
• 🌐 Bilingual - Full English and Malayalam support
• 🌙 Dark/Light Mode - Easy on the eyes
• 📱 Mobile Optimized - Swipe gestures, haptic feedback
• 💾 Offline Support - Works without internet
• 📄 Export Options - PDF & Text export
• 📅 History Tracking - View and load past records
• 📖 Scripture Reference - Track sermon details

🚀 Quick Start

Option 1: Open Directly (Easiest)

Just open index.html in your browser. All data saves locally!

Option 2: Install as App (Recommended)

See DEPLOYMENT_GUIDE.md for detailed instructions on:

• Installing on iOS & Android
• Hosting on GitHub Pages (FREE)
• Deploying to web servers

📱 How to Install on Your Phone

iPhone/iPad:

1. Host the app online (see deployment guide)
2. Open in Safari
3. Tap Share → "Add to Home Screen"

Android:

1. Host the app online (see deployment guide)
2. Open in Chrome
3. Tap Menu → "Install app"

🎯 Usage

1. Select Date - Pick the service date
2. Enter Details - Parish, celebrant, sermon info
3. Count Attendance - Use +/- buttons for male/female counts
4. Save Record - Store for future reference
5. View History - Access past records anytime
6. Export Data - Generate PDF or text reports

🌍 Language Support

Switch between English and Malayalam by clicking the ML/EN button in the top right corner.

💾 Data Storage

All your data is stored locally in your browser using localStorage. Your records are private and never leave your device unless you choose to export them.

📦 What's Included

• index.html - Main application file
• manifest.json - PWA configuration
• sw.js - Service worker for offline functionality
• icon-192.png - App icon (192x192)
• icon-512.png - App icon (512x512)
• DEPLOYMENT_GUIDE.md - Complete deployment instructions

🔒 Privacy

• ✅ No data collection
• ✅ No tracking
• ✅ No external servers
• ✅ Everything stays on your device
• ✅ Offline-first design

🛠️ Tech Stack

• Pure HTML, CSS, JavaScript
• jsPDF for PDF generation
• Service Workers for offline support
• Progressive Web App (PWA) standards

📝 License

Free to use for any MarThoma Church parish.

---

Made with ❤️ for MarThoma Church communities

☁️ Cloud backup (Google Drive)

The app can back up its records automatically to the user's own Google Drive (a hidden app-data folder — the app cannot see any other Drive files) after every save, and restore/merge them on any device. It is off until a Google OAuth Client ID is configured. One-time setup, about 10 minutes:

1. Go to https://console.cloud.google.com and create a project (e.g. "MTC Counter").
2. APIs & Services → Library → enable Google Drive API.
3. APIs & Services → OAuth consent screen → External → fill in the app name and support email → add the scope https://www.googleapis.com/auth/drive.appdata → save, then Publish the app (this scope is non-sensitive, so no Google verification is needed).
4. APIs & Services → Credentials → Create credentials → OAuth client ID → Application type Web application → under Authorized JavaScript origins add https://jsam316.github.io (and http://localhost:8000 if you test locally) → Create.
5. Copy the Client ID (ends in .apps.googleusercontent.com) into src/config.js:

   export const GOOGLE_CLIENT_ID = 'xxxxxxxx.apps.googleusercontent.com';
   

6. Commit and deploy. The Cloud backup card in the History tab now shows Connect Google Drive.

Notes

• The Client ID is a public identifier, not a secret; the origin list is what protects it.
• Restore merges: records are matched by date and the newer one wins; nothing is ever deleted by a restore.
• If the phone is offline when a save happens, the backup is marked pending and uploads automatically when the connection returns.

🚀 Deploying (GitHub Actions → GitHub Pages)

Every push to main runs .github/workflows/deploy-pages.yml, which runs the tests, stamps the service worker cache version (v<date>-<sha>, shown in the app's footer), packages only the web app files, and publishes them to GitHub Pages. If any test fails, nothing is deployed. Pull requests run the tests without deploying.

• Requires Settings → Pages → Build and deployment → Source = GitHub Actions. With any other source the site will not update.
• Deploy status is visible under the Actions tab ("Deploy to GitHub Pages"); it can also be run manually from there.
• Nothing is committed back to main by the deploy.

🧪 Tests

Run them locally with Node 20.6 or later (no install step; no dependencies):

npm test

They live in tests/ and use Node's built-in test runner:

• assist.test.js — Count Assist line counting, the choir/bystander rule, opposing streams, child height filter, tap-to-tag.
• data.test.js — record identity (date + service), cloud backup merging, HTML escaping.
• lectionary.test.js — lectionary dates are valid, every Sunday has a theme, the Friday → Sunday → Tuesday rule, and the "lectionary not added yet" check.
• integrity.test.js — every file the service worker precaches exists and every module is precached (a mistake here blocks all app updates), every button handler is wired up, English/Malayalam strings match, and the manifest icons exist.

🎨 Project layout

• index.html — page markup only.
• styles.css — all styling (precached by sw.js).
• src/ — app modules; src/main.js wires them up.
• sw.js — service worker (offline cache, updates).
• vendor/ — bundled third-party libraries (jsPDF, TensorFlow.js, COCO-SSD).