LIFEBYTE

• 

Inspiration

The idea behind Life Byte was strongly influenced by observing popular food platforms like Swiggy and Zomato.

These platforms are excellent at recommending food based on:

Cravings Trending dishes Recent searches

However, they do not consider health at all. A user might be recommended high-calorie or unhealthy food simply because it is popular or frequently searched.

This led to a key realization:

👉 What if recommendations were based not on cravings, but on health?

That’s where Life Byte stands apart.

Life Byte is designed as a “Digital Health Companion” that:

Understands your weight, height, BMI, and lifestyle Considers your health conditions (like diabetes, fitness goals, etc.) Adapts to your environment (weather, location) Recommends: Healthy meals Suitable recipes Nearby restaurants aligned with your health

Instead of saying “You may like this burger”, Life Byte says: 👉 “This is what your body actually needs right now.”

What it does

Life Byte is a smart Digital Health Companion that helps users make healthier decisions in real-life situations.

Unlike apps like Swiggy and Zomato, which recommend food based on cravings and past searches, Life Byte focuses completely on health-first recommendations.

It works by combining:

User health data (weight, height, BMI, lifestyle) Environmental data (weather conditions) Location-based data (nearby restaurants & markets)

Based on this, it:

Suggests healthy meals tailored to the user Recommends recipes suitable for current conditions Finds nearby restaurants that match health goals Provides personalized health modes (fitness, diabetic, etc.)

👉 In simple terms: It tells you what you should eat, not just what you want to eat.

How we built it

Life Byte was developed using a full-stack architecture:

Backend: Built with Python and Flask for handling APIs, logic, and user data Frontend: Vanilla JavaScript, HTML, and CSS for a fast, responsive UI Database: PostgreSQL (Neon.tech) for cloud storage SQLite for local development APIs Used: Open-Meteo → weather data Overpass API → nearby places TheMealDB → recipes Health Logic: BMI and BMR calculations Rule-based recommendation engine Heuristic disease-risk prediction

Challenges we ran into

Deployment Issues: Faced errors deploying on Render due to project structure problems Database Migration: SQLite was not suitable for cloud → migrated to PostgreSQL Recommendation Accuracy: Without ML, building accurate health suggestions using heuristics was challenging API Integration Complexity: Managing multiple APIs and combining their outputs smoothly

Accomplishments that we're proud of

Built a health-first alternative to food recommendation apps Created a context-aware system (health + weather + location) Successfully integrated multiple APIs into one platform Designed personalized Health Modes for different users Deployed a fully working full-stack application Delivered a real-world solution, not just a prototype

What we learned

How to integrate and orchestrate multiple APIs Real-world experience in cloud deployment (Render) Importance of user-centered design Building scalable full-stack applications Designing logic-based recommendation systems without ML

What's next for LIFEBYTE

Add AI/ML-based recommendations 📱 Develop a mobile app version 🥗 Introduce advanced nutrition tracking ⌚ Integrate with wearable health devices 🌍 Improve hyperlocal restaurant recommendations 🧑‍🤝‍🧑 Add community and expert support features

Built With

• css
• flask
• javascript
• openmeta
• overpass-openstreetmap
• python
• thememealdb