Over the next 180 days, I’m building a mobile application called Offline Life Archive.
And I’m documenting every single day of the journey.
Not just the code.
But also:
- product thinking
- architecture decisions
- mistakes
- design iterations
- AI-assisted development workflow
The goal is simple:
Build a real production-ready mobile app while sharing the entire process publicly.
Why I Started This Project
Today most of our personal data lives in cloud ecosystems.
Photos → cloud storage
Notes → SaaS apps
Memories → social media
Links → scattered everywhere
But very few tools allow us to own our digital memories locally.
Most apps are:
- cloud-first
- subscription-heavy
- data-collecting
- ecosystem locked
I wanted to explore a different idea.
A privacy-first personal archive.
The Idea: Offline Life Archive
Offline Life Archive is a mobile app designed to store personal memories fully offline.
The philosophy is simple:
Your digital life should belong to you.
The app focuses on:
- local storage
- strong encryption
- calm minimal design
- zero tracking
- no cloud dependency
Everything stays on the user's device.
No accounts.
No servers.
No analytics.
Just a personal memory vault.
What the App Will Do
The MVP is intentionally small and focused.
Users will be able to:
- create memory entries
- attach optional images
- organize memories using tags
- browse a chronological timeline
- search memories
- export encrypted archives
That's it.
No social features.
No collaboration.
No productivity dashboards.
This app is personal space.
Why a 180 Day Challenge?
Many developers start side projects.
Few finish them.
Most projects fail because of:
- feature overload
- architecture chaos
- lack of discipline
- constant pivots
This challenge forces me to:
- move steadily
- document decisions
- stay within boundaries
- build with long-term thinking
The focus is not speed.
The focus is clarity and discipline.
Technology Stack
The app is being built using:
Mobile
- React Native
Database
- Realm (encrypted)
Architecture
- layered modular architecture
AI tools used during development
- Stitch (UI generation)
- GitHub Copilot (coding assistance)
But AI is used as a junior assistant, not the architect.
Architecture decisions remain human-driven.
Development Philosophy
This project follows one core principle:
Build small. Design big.
Before writing large amounts of code, I’m focusing heavily on:
- architecture
- security strategy
- modular structure
- long-term maintainability
The goal is not just to build an app.
It’s to build a system that can grow without chaos.
What You Will See In This Series
Each day I’ll share what I worked on.
Sometimes it will be code.
Sometimes it will be architecture.
Sometimes it will be design thinking.
You’ll see things like:
- encryption strategy
- repository pattern
- service layer architecture
- AI assisted UI design
- React Native implementation
- performance decisions
- product scope discipline
This series is meant for developers who care about building thoughtful software.
Where Full Documentation Lives
Dev.to posts will contain summaries of each day.
The complete documentation, prompts, and detailed breakdown are available here:
👉 https://subraatakumar.com/180days/
What's Next
In Day 1, we start with something most developers skip:
Architecture before code.
We’ll define the layered structure that will guide the entire project.
Because good architecture early can save months of refactoring later.
If you're interested in:
- React Native architecture
- privacy-first products
- building in public
- disciplined development
Follow along.
Let’s build something meaningful.
Day 1 coming next. 🚀
Top comments (0)