Caloriv Native — Precision Fitness Engineering
A production-grade React Native + Expo mobile application for precision fitness tracking, integrated with an Azure Cloud backend and an offline-first native Indian food database.
Overview
Caloriv Native is the mobile-first evolution of the Caloriv ecosystem. Built for Extreme Consistency, it addresses the "Latency Gap" in nutrition tracking—the delay between a meal and its logging that leads to data decay.
The application utilizes an Offline-First SQLite Architecture on the device, synchronizing with an Azure Cloud Backend (Serverless) when network stability is detected.
Technical Valuation: Replacement Cost: ₹48.0 Lakhs | Complexity Score: 180 FP. Engineered for high-stakes body transformations.
Engineering Moat: Native Indian Nutrition Database
Standard fitness apps rely on US-centric databases (USDA). I engineered a Native Indian Food Database (100+ entries) with precise macro-breakdowns for regional staples.
Precision Tracking Architecture
- Step Tracking: Uses device motion sensors via Expo Sensors for zero-latency activity monitoring.
- BMR/TDEE Engine: Real-time metabolic estimation based on the Mifflin-St Jeor equation.
- Offline Persistence: Uses
expo-sqliteandAsyncStoragefor a zero-latency logging experience.
Backend Architecture: The Azure Pipeline
The system is backed by a high-performance Azure Cloud Infrastructure:
| Layer | Technology | Decision Rationale | | :--- | :--- | :--- | | Mobile | React Native + Expo | Cross-platform reach with native-level performance and Reanimated 3. | | Logic | Azure Functions (FastAPI) | Serverless scaling for high-concurrency ingestion and report generation. | | Storage | Azure CosmosDB | Globally distributed NoSQL for sub-100ms user data retrieval. | | CI/CD | EAS (Expo Application Services) | Automated Android build pipeline with over-the-air (OTA) updates. |
Quantitative Audit (FP Analysis)
| Function Category | Count | Adjusted FP | | :--- | :--- | :--- | | External Inputs (EI) | Meal Logs, Step Data, Biometrics | 24 | | External Outputs (EO) | Deficit Reports, Goal Progress Charts | 18 | | External Inquiries (EQ) | Food Search (Native Database) | 15 | | Internal Logical Files (ILF) | SQLite Local DB, User Biometrics | 60 | | External Interfaces (EIF) | Azure Auth, Cloud Sync Pipeline | 35 | | Total (Complexity Adjusted) | Native Android Integration Multiplier | 180 FP |
Outcome & Impact
- Zero-Latency Logging: 100% locally persistent database ensures no "Network Wait" during meal entries.
- Privacy Focus: Health data remains on-device until explicitly synced to the Azure Cloud vault.
- Deployment: Full Android build pipeline automated via custom power-shell/JS scripts discovered during the workstation audit.