Building LifeOS: A Case Study in Product Discovery, AI & User-Centric Design
For the last 3-4 months, I’ve been building something that started with a very simple idea:
“What if I could manage different parts of my life from one place?”
It started small. Then I got another idea. Then another.
A better way to track expenses.
A simpler way to log food.
A place to store everything I was learning.
A way to plan my day.
A place to track goals.
A reminder for birthdays.
Instead of creating a separate app every time, I kept adding the idea to the same system.
Today, that experiment has grown into my personal LifeOS.
And the interesting part isn't just what the application does.
It is how I built it.
From a Blank Screen to My Personal LifeOS
When I started, there was no grand product roadmap.
No 50-page PRD.
No development team.
Just a blank screen and a problem I wanted to solve.
I used Google AI Studio, web technologies, and prompt-assisted development to turn ideas into working features. I would think through a problem, describe what I wanted, test the result, find something that didn't work, and iterate.
Then I'd get another idea. And build again.
Over time, this became my own product development loop:
Problem → Idea → Prompt → Prototype → Test → Feedback → Iterate
That loop has been running for almost three years.
And somewhere along the way, I realized that I wasn't simply building a collection of tools.
I was practicing product management on myself.
The Product: Param's LifeOS
Today, the home screen brings together different parts of my life:
💰 Wealth: finances, goals & transactions
❤️ Health: fitness, nutrition & wellness
📅 Routine: daily schedule & time blocks
📝 Notes: learning and knowledge management
✈️ Safar: experiences, reflections & travel
🎯 Life Goals: ambitions and milestones
🧘 Manifest: affirmations and visualization
🎂 Birthday Reminder: remembering the people who matter
The idea isn't to make everything complicated. It is to make the things I repeatedly do easier to manage from one place.
01 Wealth: Understanding Where My Money Goes
Money was one of the first problems I wanted to solve.
I didn't just want to know how much money I had.
I wanted to understand:
Where is my money going?
My finances are spread across different accounts, wallets, credit cards and investment platforms.
So I built a central Wealth module.
The Dashboard
The dashboard gives me a quick view of:
Current account balances
Monthly spending
Spending categories
Income and expenses
Overall financial activity
Instead of opening multiple places, I can get the bigger picture from one screen.
Accounts
I can configure different financial sources:
Bank accounts
Wallets
Credit cards
Other accounts
This creates a single structure for my financial data.
Transactions
This is where I spent a lot of time thinking about reducing friction.
I can manually add a transaction with:
Debit or credit
Title
Category
Date
Remarks
Account
But manually entering hundreds of transactions isn't fun.
So I added bulk import through Excel.
I can prepare the data in a spreadsheet and import it instead of entering every transaction individually.
And Then I Added AI
This was one of the moments where the application became more interesting.
Instead of opening a form, I can simply write something like:
“I spent ₹300 on lunch from XYZ Bank.”
The AI assistant interprets the information and helps log the transaction.
The goal was simple:
Don't make me learn the system. Let the system understand me.
Goals & Investments
I also added goal tracking for things like:
Education
Car
Mobile phone
Other personal goals
And there's an investment section for SIPs and stocks.
For example, an SIP transaction can be associated with the account it comes from and the investment account it goes into.
This gives me a clearer view of both cash flow and investment activity.
And because the transaction data can be downloaded, it can later be used for deeper analysis.
02 Health: Turning Daily Habits Into Data
The Health module started with two questions:
What am I eating? and What am I doing physically?
So I divided it into three areas:
🍎 Food & Water
I can log food under:
Breakfast
Lunch
Evening snacks
Dinner
For each food entry, I can track things like:
Calories
Protein
Carbohydrates
Fiber
But again, I wanted to avoid unnecessary manual work.
So I added an AI-based food logging flow.
I can write:
“I had 100g Poha and 130ml tea.”
The system can estimate the nutritional information and log it.
If I already know the exact nutritional values, I can also enter them manually.
The dashboard then converts these logs into a daily progress view.
💧 Water Tracking
Water tracking follows the same principle.
Instead of typing everything, I can quickly add predefined amounts such as:
50ml → 100ml → 200ml
I can also set a daily target and track progress throughout the day.
💪🏻 Workout
The workout section has two approaches.
The first is simple:
Log what I already did.
The second is where AI becomes useful.
I can give it a context such as:
“I have 20 minutes, I want a lightweight workout, and I'm at home.”
The AI can generate a workout based on those constraints.
And if I don't know how to perform an exercise, the application can provide visual guidance and instructions.
So instead of simply recording activity, the system can help me plan the activity as well.
That's an important product distinction:
Tracking what happened vs. helping decide what to do next.
03 Routine: My Day, Block by Block
Before this application existed, I already maintained my daily routine separately in an Excel sheet.
So instead of replacing something that already worked, I embedded that workflow into the application.
I can plan my day on an hourly basis and log what I actually did.
This gives me two perspectives:
Plan → What I intended to do
Actual → What I really did
For me, that difference is useful.
Because productivity isn't just about creating a perfect schedule.
It's about understanding where reality differs from the plan.
The application doesn't force me to change my routine. It helps me see it.
04 Notes: One Home for Everything I Learn
This module came from a very familiar problem.
I was learning something in class.
I wrote one thing in a notebook.
Another thing went into WhatsApp.
Another went into my phone.
Another ended up in a random document.
Eventually, I couldn't remember where I had written what.
So I built Notes.
The idea is simple:
If I learn something, I should be able to store it in one place and find it later.
The application has a dedicated editor that helps me organize my notes and structure them using Markdown.
It has gradually become my personal learning repository.
05 Safar: Not Just Travel, But Reflection
This might be my most personal module.
Safar isn't simply a travel planner.
It's more like a personal reflection journal.
I maintain month-wise sections covering things like:
What I enjoyed
What I learned
Things that didn't go well
Books I read
Movies I watched
Series I'm following
Other things happening in my life
I also maintain a separate work-related sheet. The interesting part is that this isn't a rigid application feature.
It's my personal workflow.
So I designed the system to allow embedded spreadsheets, rather than forcing everyone into the same structure.
That's an important lesson for me as a product thinker:
Not every user needs the same workflow. Sometimes flexibility is the feature.
06 Life Goals: Turning “Someday” Into Something Visible
We all have things we say:
“I want to do this someday.”
The problem is that someday can stay someday forever.
So I created a dedicated Life Goals section.
I can create goals as cards and track things I want to accomplish over the coming years.
It gives me a visual reminder of:
Where I am → What I want → What I'm working toward
It isn't meant to be complicated.
Sometimes seeing a goal is enough to bring it back into focus.
07 Manifest: From Thoughts to Visuals
The Manifest section came from my interest in visualization and affirmations.
I can create custom affirmations and organize them into different categories.
But I wanted to take it one step further.
So I added an AI-powered visualization dashboard.
I can describe what I want to visualize, and the AI can generate a structured visual dashboard around that idea.
For me, this turns a vague thought into something I can actually see.
And that's the larger idea behind the module:
Think → Visualize → Revisit
08 Birthday Reminder: Because I'm Terrible at Remembering Birthdays
Let's be honest.
I'm not particularly good at remembering birthdays.
So instead of trusting my memory, I built a system.
I can add people's birthdays and see upcoming birthdays from the application.
It's a small feature.
But it solves a very real personal problem.
And this is something I've learned repeatedly while building this application:
A good product doesn't always solve a big problem. It solves a problem that matters to its user.
This module is still new, so I have more ideas for improving reminders and notifications.
That's also the nature of this entire project.
It is never really finished.
The Technology Behind My LifeOS
Behind the simple interface, Param’s LifeOS brings together several technologies and workflows:
Firebase for Google authentication
Database and data storage for managing personal information
AI assistants for tasks such as transaction and food logging
Prompt-assisted web development using Google AI Studio and Gemini
Excel/Google Sheet integrations for routine and personal tracking
Data import and export for easier analysis and management
Modular architecture, where each section solves a specific problem
What makes this interesting for me is how quickly an idea can move from thought → prompt → working feature. I can describe what I want, build a first version, test it in my own workflow, and improve it based on what I actually need.
That has also changed how I think about product development. I didn't start with a massive roadmap. I started with real problems from my own life and kept adding solutions around them.
Today, these individual solutions have come together into one personal LifeOS covering money, health, time, learning, experiences, goals, and relationships.
What's Next?
The application is still evolving, and I have plenty of ideas to improve it further.
My next goal is to explore how I can make Param's Hub production-ready—with stronger reliability, better integrations, improved notifications, and a smoother experience.
I may also explore monetizing it someday if I find a clear use case beyond my own needs. I'm not sure what that model would look like yet, but it's definitely something I want to think about.
For now, I'm still building, experimenting, and learning.
And if you have an interesting idea that could make this LifeOS better, drop it in the comments. I might just add it to the next version.
