SplitSense banner

SplitSense

3 devlogs
3h 16m 3s

SplitSense is a simple app that helps people split expenses fairly and easily.

It is made for situations like trips with friends, sharing rent, or splitting food bills. Instead of calculating everything manually or arguing about who owes whom, …

SplitSense is a simple app that helps people split expenses fairly and easily.

It is made for situations like trips with friends, sharing rent, or splitting food bills. Instead of calculating everything manually or arguing about who owes whom, SplitSense keeps track of expenses and shows a clear summary of how much each person should pay or receive.

The app lets you create groups, add expenses, and automatically calculate balances. It is designed to be easy to use, even for someone who is not very technical. The goal of SplitSense is to save time, avoid confusion, and make money matters between friends stress-free.

Demo Repository

Loading README...

namandogra431

Today’s work focused on building and deploying the web version of SplitSense, taking it from a local idea to a live, production-ready application.

I started by designing a highly polished, responsive frontend using modern HTML, Tailwind CSS, glassmorphism, animations, and premium visual effects. The goal was to make the interface feel app-like, professional, and intuitive, with smooth interactions, animated headings, and a clean user flow for creating groups, adding members, and managing expenses. Special attention was given to responsiveness so the UI works seamlessly across desktop and mobile screens.

On the backend side, we implemented a Flask application (app.py) that handles core functionality: creating groups, storing members, adding expenses, calculating balances, and simplifying settlements. The backend uses clean routing, form handling, and in-memory data structures to power the app logic while keeping the architecture simple and easy to extend later (for example, with a database or authentication).

The final and most important step was deploying the Flask backend to the cloud using Render. This involved preparing the project structure, creating a requirements.txt, configuring Gunicorn as the production server, pushing the code to GitHub, and setting up a Render web service with HTTPS. After deployment, the app became accessible through a public URL, making it usable outside localhost and ready for real users. This completed the full web pipeline: design → backend → live deployment.

Attachment
0
namandogra431

Today i have created the basic expense-splitting logic as ell as created the prototype Flask server, and i also made the basic ui to test the protoype

Attachment
0