<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Supabase on App Coding</title>
    <link>https://appcoding.com/tags/supabase/</link>
    <description>Recent content in Supabase on App Coding</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 03 Dec 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://appcoding.com/tags/supabase/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Mobile Backend Dilemma: Firebase, Supabase, or Build Your Own</title>
      <link>https://appcoding.com/2025/12/03/the-mobile-backend-dilemma-firebase-supabase-or-build-your-own/</link>
      <pubDate>Wed, 03 Dec 2025 00:00:00 +0000</pubDate>
      <guid>https://appcoding.com/2025/12/03/the-mobile-backend-dilemma-firebase-supabase-or-build-your-own/</guid>
      <description>&lt;p&gt;Every mobile app that does anything interesting eventually needs a backend. Authentication, data storage, push notifications, file uploads, real-time updates — the list of backend requirements grows quickly once an app moves beyond a local-only experience. The decision of how to provide that backend is one of the most consequential architectural choices a mobile development team makes, and it is one that becomes substantially harder to reverse after significant user data has accumulated.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
