PIP INSTALL WIN

Inspiration

The idea for LifeOS emerged from a personal frustration with fragmented health apps. I found myself using one app for steps, another for nutrition, a third for sleep, and yet another for tasks. None of them talked to each other, and none provided actionable insights.

I wanted a single "operating system" for my life — something that could:

Aggregate all health data in one place
Analyze patterns using AI
Recommend personalized improvements
Track progress over time

The vision was simple: What if your health data could tell you not just what happened, but what to do next?

What It Does

LifeOS is an AI-powered lifestyle management platform that combines:

Module	Features
Health Tracking	Log vitals (heart rate, weight, blood pressure, steps) with timestamps
Fitness	Record workouts, track calories burned, monitor intensity
Nutrition	Log meals with macronutrient breakdown
Sleep	Track sleep duration, quality, and consistency
Tasks	Manage daily tasks with AI-prioritized recommendations
Social	Share achievements and compete with friends
AI Coach	Chat with Google Gemini for personalized health advice

The AI analyzes your data using statistical models. For example, if we define a health score $H$ as:

$$H = \alpha \cdot S + \beta \cdot N + \gamma \cdot F + \delta \cdot T$$

Where:

$S$ = Sleep quality score (0-10)
$N$ = Nutrition adherence (0-1)
$F$ = Fitness frequency (workouts per week / target)
$T$ = Task completion rate
$\alpha, \beta, \gamma, \delta$ = User-configurable weights

The system identifies correlations — e.g., "When you sleep >7 hours, your task completion improves by 23%" — and suggests optimizations.

How We Built It

Tech Stack

Frontend: HTML5 + CSS3 + Jinja2 Templates Backend: Flask (Python) Database: SQLAlchemy ORM + SQLite/PostgreSQL AI Engine: Google Gemini API Auth: Flask-Login with Werkzeug security

Architecture

The project follows the MVC pattern:

Models: SQLAlchemy ORM defines entities (User, HealthMetric, Task, etc.)
Views: Jinja2 templates render responsive HTML
Controllers: Flask blueprints handle routing and business logic

Key Implementation Details

Database Design: Used normalized relational schema with foreign key constraints:

class User(db.Model):
    id = db.Column(db.Integer, primary_key=True)
    health_metrics = db.relationship('HealthMetric', backref='user', lazy='dynamic')