MOVING PROJECTS OFF FIREBASE STUDIO
We have time before the shutdown. That is exactly why we would rather move things now than wait for it to become urgent.
WHY WE ARE MOVING
Firebase Studio is being sunset, which puts a clear deadline on anything still living there. We would rather move projects while there is room to test, fix and double-check things than do it under pressure later.
WHAT WE ARE MOVING TO
The replacement setup is VS Code, Codex, Git and Cloudflare. VS Code is the working environment, Codex helps with changes and debugging, Git keeps the history, and Cloudflare handles deployment. It is a fairly straightforward stack, which is part of the appeal.
THE FIDDLY PART
The code itself is usually not the scary bit. The fiddly part is working out what the old environment was quietly handling, then making those assumptions explicit. Build settings, deployment behaviour, environment configuration and framework choices all need checking.
TAKING IT PROJECT BY PROJECT
We are not treating this like one giant migration. Each project gets moved, tested and checked on its own terms. Some will be simple. Some will probably remind us of things we forgot were there. That is why starting early is useful.