<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: jrosalesro</title>
    <description>The latest articles on DEV Community by jrosalesro (@jrosalesro).</description>
    <link>https://dev.to/jrosalesro</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3869185%2Fb00fce10-5580-4d25-bfc3-72f3270e0fd8.png</url>
      <title>DEV Community: jrosalesro</title>
      <link>https://dev.to/jrosalesro</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/jrosalesro"/>
    <language>en</language>
    <item>
      <title>Stop rebuilding Firebase admin panels — here’s a simpler approach</title>
      <dc:creator>jrosalesro</dc:creator>
      <pubDate>Thu, 09 Apr 2026 07:17:59 +0000</pubDate>
      <link>https://dev.to/jrosalesro/stop-rebuilding-firebase-admin-panels-heres-a-simpler-approach-754</link>
      <guid>https://dev.to/jrosalesro/stop-rebuilding-firebase-admin-panels-heres-a-simpler-approach-754</guid>
      <description>&lt;p&gt;Every time I start a new project with Firebase, I run into the same problem.&lt;/p&gt;

&lt;p&gt;At some point, I need to manage data properly — not just read it, but edit, inspect, and organize it in a practical way.&lt;/p&gt;

&lt;p&gt;And every time, I end up doing the same thing:&lt;br&gt;
👉 building a custom admin panel from scratch.&lt;/p&gt;

&lt;h2&gt;
  
  
  🔁 The recurring problem
&lt;/h2&gt;

&lt;p&gt;Firebase is amazing to get started quickly.&lt;/p&gt;

&lt;p&gt;But once your project grows, the Firebase Console starts to feel limited:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Editing data becomes tedious&lt;/li&gt;
&lt;li&gt;Navigating collections is not always efficient&lt;/li&gt;
&lt;li&gt;There’s no real “workflow” for managing data&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;So what happens?&lt;/p&gt;

&lt;p&gt;👉 You build your own internal tool.&lt;br&gt;
👉 Again.&lt;br&gt;
👉 And again.&lt;/p&gt;

&lt;h2&gt;
  
  
  🤔 Why does this happen?
&lt;/h2&gt;

&lt;p&gt;Because there’s a gap between:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Firebase as a backend&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;and&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;having a usable backoffice to manage your data&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;And most of the time, we just accept that building an admin panel is part of the process.&lt;/p&gt;

&lt;h2&gt;
  
  
  💡 A different approach
&lt;/h2&gt;

&lt;p&gt;Instead of rebuilding the same tool every time, I started thinking:&lt;/p&gt;

&lt;p&gt;👉 What if we could reuse something that already exists?&lt;/p&gt;

&lt;p&gt;Something simple, familiar, and flexible enough to act as a backoffice.&lt;/p&gt;

&lt;h2&gt;
  
  
  🧩 Using WordPress as a Firestore admin
&lt;/h2&gt;

&lt;p&gt;This led me to experiment with using WordPress as a lightweight admin layer for Firebase.&lt;/p&gt;

&lt;p&gt;The idea is simple:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Use WordPress as the UI&lt;/li&gt;
&lt;li&gt;Connect it to Firestore&lt;/li&gt;
&lt;li&gt;Manage your data from there&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  ⚙️ What this enables
&lt;/h2&gt;

&lt;p&gt;With this approach, you can:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Browse collections&lt;/li&gt;
&lt;li&gt;Edit documents&lt;/li&gt;
&lt;li&gt;Perform CRUD operations&lt;/li&gt;
&lt;li&gt;Have a simple admin interface without building it from scratch&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fzs32jknnlt57wyqxyexy.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fzs32jknnlt57wyqxyexy.webp" alt=" " width="800" height="595"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  🚀 What I built
&lt;/h2&gt;

&lt;p&gt;To test this idea, I built a small plugin:&lt;br&gt;
&lt;strong&gt;BackOffice Manager for Firebase&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Setup takes just a few minutes — no need to build a custom admin panel from scratch.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;It allows you to connect WordPress with Firestore and manage your data directly from the dashboard.&lt;/p&gt;

&lt;p&gt;It’s still early, but it already solves the main pain point I kept running into.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fu6qihkb79vdazvjhmhqt.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fu6qihkb79vdazvjhmhqt.webp" alt=" " width="800" height="597"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  🤝 Looking for feedback
&lt;/h2&gt;

&lt;p&gt;I’m trying to understand if this is a real problem for others or just something I experienced.&lt;/p&gt;

&lt;p&gt;So I’d love to hear from you:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Do you build custom admin panels for Firebase projects?&lt;/li&gt;
&lt;li&gt;How do you manage your data today?&lt;/li&gt;
&lt;li&gt;Would you use something like this, or prefer full control?&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  🔗 If you’re curious
&lt;/h2&gt;

&lt;p&gt;You can find the plugin in the WordPress plugin repository by searching:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://wordpress.org/plugins/backoffice-manager-for-firebase/" rel="noopener noreferrer"&gt;BackOffice Manager for Firebase&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;If you’re working with Firebase and feel this pain, I’d really appreciate your feedback.&lt;/p&gt;

</description>
      <category>backend</category>
      <category>firebase</category>
      <category>webdev</category>
      <category>wordpress</category>
    </item>
  </channel>
</rss>
