Rx Note

Introduction In my journey of building Progressive Web Application (PWA) tools for personal use, my collection has grown to 30 independent GitHub repositories. Manually running npm outdated, npx taze -w , and npm update , followed by TypeScript type checking ( tsc --noEmit ) and Biome formatting ( biome check --write ) individually across each project directory, quickly became tedious and time-consuming. To address this, I evaluated two potential architectural paths: Monorepo Approach: Consolidate all companion applications into a single repository to share configurations and centralize dependency management with a single lockfile. Multi-Repo + Orchestrator CLI Approach (Meta-Repository Pattern): Retain separate repositories while building a custom CLI tool to orchestrate batch tasks from a single interface. I chose the Multi-Repo + Orchestrator pattern as the basis for RxCLI for the following reasons: Independent Repositories: Each project continues to live in its own standalone G...

Introduction Following the sunset notice of Firebase Studio , I was forced to migrate my four active projects to Google Antigravity . Despite my initial reluctance, the migration was completed successfully in every attempt. Impressions A few key distinctions stood out immediately: Framework Flexibility: Unlike Firebase Studio , which defaults primarily to server-side frameworks like Next.js , Google Antigravity provides greater framework flexibility, where it supports building web applications using standard vanilla HTML, CSS and JavaScript, as well as modern build tools like Vite + React . Transparency and Control: Google Antigravity provides a detailed plan of proposed changes and only proceeds with explicit permission. This is a significant improvement over the over-aggressive nature of Firebase Studio, which often implemented changes regardless of instructions. Seamless Integration: While I previously found Google service integration in Firebase Studio to be fragmented, Googl...

Introduction A highly counterintuitive aspect of vibe coding is that the real challenge is rarely its feasibility or actual difficulty; rather, it is the imagined psychological barrier that you are incapable of handling the task. Simply looking at an IDE like Visual Studio Code (VS Code) can make you want to take a U-turn. However, this is merely a perceived barrier rather than a genuine hardship. In fact, you will likely get the hang of it after just a few tries. The Explorer View The first tab of the IDE displays the folder layout of your current project. What you see here is a typical Next.js structure. You will notice hidden or auto-generated directories such as .next, node_modules, and out . These are generated automatically when you run npm install and npm run build , and they are typically excluded from being synced to GitHub repositories via the .gitignore file. Clicking on any file in this view reveals the underlying code and logic. Source Control This is arguably the mos...

Introduction As a pharmacist by profession, I approached Vibe Coding and Progressive Web App (PWA) development as a personal experiment in self-directed learning. Rather than enrolling in formal training or studying dense programming manuals, I chose to dive straight into the "vibe coding" process. Admittedly, without a technical background or a mentor’s guidance, I faced a steep learning curve. I have compiled these hard-earned lessons into this book to share them with you while the insights are still fresh in my mind. Content While the core content was originally presented in the series Vibe Coding Journey From Firebase Studio to Antigravity , this book offers a more refined and updated version of those foundational philosophies. The Vibe Coding Experiment is the culmination of that journey - a distilled collection of wisdom gained over a year of hands-on building, troubleshooting, and creating. My additional experiments in building a more diverse range of PWAs have gi...

Introduction When Google introduced Firebase Studio for "vibe coding", Next.js was established as the primary framework due to its seamless integration of front-end and back-end logic. While this unified design is compelling, it carries a hidden cost: a heavy reliance on server-side post-processing and Cloud Functions to serve even basic assets. For many developers, this architecture introduces unnecessary complexity and overhead for projects that don't require a persistent server. The Migration While exploring alternative configurations, I discovered that Google Antigravity suggests app setups tailored to specific functional needs. The PWAs (Progressive Web Apps) I designed for personal use - an offline-first budget tracker , a QR code suite , and a "Sheet-to-Database" utility - are primarily static applications. They rely almost entirely on local client-side execution ('use client') and do not require Server-Side Rendering (SSR). Antigravity reco...