Faizan OS Week 1: From Zero to 13 Modules

I started Faizan OS because I was tired of juggling five different apps to run my own life. This is the first entry in a weekly log of what actually happened while building it, week by week, bugs included.

Table of Contents

• The Starting Baseline
• Website and Quick Capture
• The First Notification Bug
• Tags Engine and Cleanup
• What's Next

The Starting Baseline

The first two days were a bulk import. Thirteen modules landed at once, all of them ports of a prior version of the app I had running: Personal Finances, Home Finances, Income, Investments, Split and Owe, Liabilities, Net Worth, Habits, Odessys, Check-in, Watch Queue, Trips, and Reminders, plus Brain Dump for freeform notes.

These weren't built from scratch. Each one kept the exact same data format as the old version, reading and writing the same underlying documents, so the old app and the new one could run side by side with zero migration work. That decision saved a lot of headaches later.

Alongside the import came the first bit of real polish: Watch Queue got platform and genre metadata, and Brain Dump got optimistic UI so notes felt instant instead of waiting on a network round trip.

Website and Quick Capture

Day three brought two new pieces. The first was a module for publishing blog posts to my own website, complete with image uploads. The second was the start of what I call Quick Capture: a text box where I can type something freeform and have it get routed to the right part of the app automatically.

Quick Capture started small on purpose. Phase one only handled routing to Brain Dump. Everything else came later, one category at a time.

That same day I also added local due-date notifications, a simple version that ran entirely on-device with no backend involved.

The First Notification Bug

Day four is where things got more ambitious, and more painful. I replaced the local notifications with real background push, using Firebase Cloud Messaging and a Cloudflare Cron Worker running behind the scenes.

It did not work correctly the first time. Cloudflare Workers run on UTC by default, with no concept of my local timezone. Every due-date comparison was happening against raw UTC time, which meant reminders were showing up roughly five hours late. On top of that, the push messages weren't marked high-priority, so delivery itself was inconsistent.

Both got fixed within the week, but it was a good early reminder that "it works on my machine" and "it works across timezones and background delivery constraints" are two very different problems.

Tags Engine and Cleanup

Day five introduced a lightweight tags system. It started wired into Personal Finances only, then expanded outward so items across the app could carry the same tag and show up together in search.

The last two days of the week were quieter: fixing how Topic Ideas got imported, cleaning up mobile layout issues, and improving search autocomplete. Not glamorous, but the kind of work that makes everything built earlier in the week actually pleasant to use.

What's Next

By the end of week one, the baseline was in place: thirteen modules, a way to publish content, a way to capture stray thoughts, and the beginnings of cross-module organization through tags. Week two is where things start to get more interesting, with new modules and the first real correctness bugs around data and privacy.