<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>App Deployment on Roger That Dev</title>
    <link>https://www.rogerthat.dev/tags/app-deployment/</link>
    <description>Recent content in App Deployment on Roger That Dev</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 10 Jul 2026 07:04:11 -0800</lastBuildDate>
    <atom:link href="https://www.rogerthat.dev/tags/app-deployment/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Environments in Firebase: From Prototype to Production</title>
      <link>https://www.rogerthat.dev/posts/firebase-environments/</link>
      <pubDate>Fri, 10 Jul 2026 07:04:11 -0800</pubDate>
      <guid>https://www.rogerthat.dev/posts/firebase-environments/</guid>
      <description>&lt;p&gt;These days, anyone can be a builder. With agentic AI assistants and app platforms like Firebase, it’s easy to go from prototype to deployment in no time at all. But if you want your million-dollar app idea to someday scale in a secure way, you’ll eventually need to think about how you’re going to separate your live production environments from your prototyping and development resources.&lt;/p&gt;&#xA;&lt;h3 id=&#34;one-app-and-two-projects-at-least&#34;&gt;One app and two projects (at least)&lt;/h3&gt;&#xA;&lt;p&gt;Every Firebase app should have at least two environments: &lt;strong&gt;one production (prod)&lt;/strong&gt; and &lt;strong&gt;at least one pre-production (pre-prod)&lt;/strong&gt;. Prod is for the live show and pre-prod is for rehearsals, dress rehearsals and dry runs. Pre-prod environments allow you to experiment, explore and make mistakes without impacting what users are seeing or any data that matters. Even if you’re doing local development with the Firestore Emulator Suite, it’s important to have a pre-prod environment deployed on Google Cloud too.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
