<?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: Muhammad Moiz</title>
    <description>The latest articles on DEV Community by Muhammad Moiz (@muhammadmoiz269).</description>
    <link>https://dev.to/muhammadmoiz269</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.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F721685%2F71340318-ba53-49c8-82de-bd13bef0eb67.jpg</url>
      <title>DEV Community: Muhammad Moiz</title>
      <link>https://dev.to/muhammadmoiz269</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/muhammadmoiz269"/>
    <language>en</language>
    <item>
      <title>How to Build an MVP Without Wasting 6 Months</title>
      <dc:creator>Muhammad Moiz</dc:creator>
      <pubDate>Fri, 13 Nov 2026 05:09:00 +0000</pubDate>
      <link>https://dev.to/muhammadmoiz269/how-to-build-an-mvp-without-wasting-6-months-nm6</link>
      <guid>https://dev.to/muhammadmoiz269/how-to-build-an-mvp-without-wasting-6-months-nm6</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://muhammadmoiz.dev/blog/how-to-build-an-mvp" rel="noopener noreferrer"&gt;muhammadmoiz.dev&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;To build an MVP without wasting six months, start from one painful problem and one type of customer, write down the single job your product must do, cut every feature that doesn't serve that job, and put a working version in front of real users within weeks rather than quarters. Anything you can do by hand behind the scenes, do by hand at first. The goal of a minimum viable product is learning what customers will actually use and pay for, not shipping a smaller copy of your dream app.&lt;/p&gt;

&lt;p&gt;This guide walks through how to create an MVP step by step, how to decide what to cut, and the mistakes that turn a six-week project into a six-month one.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is an MVP, really?
&lt;/h2&gt;

&lt;p&gt;Eric Ries, who popularised the term in The Lean Startup, describes the MVP as the version of a product that lets a team learn the most about its customers for the least effort. The term itself is older: it is generally credited to Frank Robinson in 2001, with Steve Blank and Ries spreading it later.&lt;/p&gt;

&lt;p&gt;Two parts of that definition matter more than people expect:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;"Learn" is the output.&lt;/strong&gt; An MVP is a tool for answering a question, such as "Will restaurant owners pay monthly for this?" or "Will people upload their files to us instead of emailing them?" If you can't name the question, you aren't building an MVP yet.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;"Least effort" is relative.&lt;/strong&gt; Ries himself stresses that there is no formula for how small an MVP should be. For some ideas it's a landing page and a payment link. For others, like anything that handles money or health data, the minimum still has to be secure and reliable.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A useful test: if your first version answers your riskiest question, it is viable. If it also answers ten questions nobody asked, it isn't minimal.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why do most MVPs take 6 months instead of 6 weeks?
&lt;/h2&gt;

&lt;p&gt;Slow MVPs rarely come from slow coding. They come from decisions made before the first line of code. The usual causes:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Building for every future customer.&lt;/strong&gt; Multiple user roles, team accounts, an admin dashboard with analytics, and five integrations, all before one person has signed up.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Perfecting things users haven't asked for.&lt;/strong&gt; Custom design systems, animations, and settings pages for preferences nobody has.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Automating work that happens ten times a month.&lt;/strong&gt; Writing an invoicing engine when you could send ten invoices by hand.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Scope that changes every week.&lt;/strong&gt; Without a written, frozen scope, every conversation adds a feature.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Waiting for a big launch.&lt;/strong&gt; Holding the product back until it feels "ready", then launching to silence.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Ries gives a good example of the cost of guessing: his team at IMVU once spent weeks on a feature nobody wanted, when a simple ad test could have shown the lack of demand far sooner. The fix for all five causes above is the same. Decide what you need to learn, and build only that.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to build an MVP: a step-by-step plan
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Step 1: Write the problem and the customer in one sentence
&lt;/h3&gt;

&lt;p&gt;"Independent wedding card sellers lose orders because customers can't see designs and prices online" is a usable problem. "A platform for events" is not. Pick one customer type you can actually reach this month.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 2: Name your riskiest assumption
&lt;/h3&gt;

&lt;p&gt;Usually it is one of three: people don't have this problem, they won't switch from what they do now, or they won't pay. Your MVP exists to test that one assumption first.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 3: Define the one core flow
&lt;/h3&gt;

&lt;p&gt;Map the shortest path from "user arrives" to "user gets value". For a booking product, that's: see availability, pick a slot, confirm. Everything outside that path goes on a "later" list.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 4: Replace software with people wherever you can
&lt;/h3&gt;

&lt;p&gt;Paul Graham's essay "Do Things That Don't Scale" is full of examples: Airbnb's founders recruited hosts door to door in New York, and Stripe's founders quietly set up merchant accounts for early users by hand. You can do the same. Approve signups manually, send reports by email, handle payments with a payment link, and take orders over chat.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 5: Timebox the build
&lt;/h3&gt;

&lt;p&gt;Pick a fixed window, for example four to eight weeks, and cut scope to fit the window rather than stretching the window to fit the scope. Write the scope down and treat changes as trade-offs: something comes in, something goes out.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 6: Launch small, then talk to every user
&lt;/h3&gt;

&lt;p&gt;Graham's point about launches is blunt: big launches rarely matter, and what counts is a small core of users who genuinely like the product. Ship to 10 to 50 people you found yourself, watch how they use it, and talk to them weekly.&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%2Fimages.unsplash.com%2Fphoto-1503551723145-6c040742065b-v2%3Fw%3D1200%26q%3D80" 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%2Fimages.unsplash.com%2Fphoto-1503551723145-6c040742065b-v2%3Fw%3D1200%26q%3D80" alt="Colourful sticky notes pinned to a board during a product planning session" width="1200" height="800"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Photo: Patrick Perkins on Unsplash&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  How to cut scope: what goes in, what waits
&lt;/h2&gt;

&lt;p&gt;This is the part founders find hardest, so here's a practical way to sort features. Ask of each one: "If this were missing, would a user in our core flow fail to get value?" If the answer is no, it waits.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Feature&lt;/th&gt;
&lt;th&gt;In the MVP?&lt;/th&gt;
&lt;th&gt;What to do instead&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Sign up and log in&lt;/td&gt;
&lt;td&gt;Usually yes&lt;/td&gt;
&lt;td&gt;Use a managed auth provider instead of building your own&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;The core flow (book, order, upload, track)&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;td&gt;This is the product&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Payments&lt;/td&gt;
&lt;td&gt;Only if testing willingness to pay&lt;/td&gt;
&lt;td&gt;A hosted checkout or payment link&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Admin dashboard&lt;/td&gt;
&lt;td&gt;Minimal&lt;/td&gt;
&lt;td&gt;A simple internal page, or the database console&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Team accounts and roles&lt;/td&gt;
&lt;td&gt;Rarely&lt;/td&gt;
&lt;td&gt;Add when a paying customer asks&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Native iOS and Android apps&lt;/td&gt;
&lt;td&gt;Rarely&lt;/td&gt;
&lt;td&gt;A responsive web app or PWA first&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Analytics and reporting&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;Basic event tracking plus talking to users&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Notifications&lt;/td&gt;
&lt;td&gt;Maybe one&lt;/td&gt;
&lt;td&gt;One email or push for the moment that matters&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Integrations&lt;/td&gt;
&lt;td&gt;Rarely&lt;/td&gt;
&lt;td&gt;Manual export or a single webhook&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;A real example: when I co-founded and built Shahi Bulawa, a wedding card and e-invitation store, we went from zero to launch in about a month. Instead of building a full cart and checkout, each product leads customers to WhatsApp to request a quote or a free mockup. The Next.js catalogue, an admin panel and SEO-friendly pages were in scope; a complex ordering system was not. The store got around 15 orders a month from the first month. You can read the full &lt;a href="https://muhammadmoiz.dev/work/shahibulawa" rel="noopener noreferrer"&gt;Shahi Bulawa case study&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Choosing a tech stack for your MVP
&lt;/h2&gt;

&lt;p&gt;The best MVP stack is the one your developer can ship fastest and that won't need a full rewrite if the idea works. For most web MVPs, that means:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;A mainstream framework&lt;/strong&gt; such as Next.js or React, so hiring help later is easy.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A managed backend&lt;/strong&gt; such as Firebase or Supabase for auth, database and storage, so nobody spends weeks on infrastructure.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Hosted payments&lt;/strong&gt; rather than custom billing logic.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Simple hosting&lt;/strong&gt; with automatic deploys.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;AI app builders like Lovable, Bolt and Replit can get a prototype on screen in days, and for testing demand they are often a great value starting point. The catch is what happens when real users and real data arrive. We've covered the &lt;a href="https://muhammadmoiz.dev/blog/vibe-coding-security" rel="noopener noreferrer"&gt;common security holes in AI-built apps&lt;/a&gt; separately; if you go this route, plan for a review before you take payments or store personal data.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Minimal is not the same as insecure:&lt;/strong&gt; Cutting features is fine. Cutting security is not. Even a two-week MVP needs proper access rules on the database, secrets kept off the client, and validated input on every form. A data leak in month one can end a product before it starts.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  A realistic MVP timeline
&lt;/h2&gt;

&lt;p&gt;Every project differs, but a focused web MVP often follows a shape like this:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Week 1: Scope.&lt;/strong&gt; Problem statement, riskiest assumption, core flow, written feature list, and a "later" list.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Weeks 2 to 5: Build.&lt;/strong&gt; Core flow first, then auth, then the minimum admin tools. A working preview every week.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Week 6: Private launch.&lt;/strong&gt; Ten to fifty hand-picked users, manual onboarding, direct feedback.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Weeks 7 onward: Iterate.&lt;/strong&gt; Fix what blocks users, add only what several users ask for, and decide whether the core assumption held.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If you want a sense of budget for each stage, see our breakdown of &lt;a href="https://muhammadmoiz.dev/blog/web-app-development-cost" rel="noopener noreferrer"&gt;web app development cost in 2026&lt;/a&gt; and the fixed options on the &lt;a href="https://muhammadmoiz.dev/pricing" rel="noopener noreferrer"&gt;pricing page&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  What this means for founders and business owners
&lt;/h2&gt;

&lt;p&gt;Building an MVP is a business decision before it is a technical one. Before you hire anyone or open an AI builder, you should be able to answer:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;What single question will this MVP answer?&lt;/li&gt;
&lt;li&gt;Who are the first 20 users, by name or by channel?&lt;/li&gt;
&lt;li&gt;What is the one flow they must complete?&lt;/li&gt;
&lt;li&gt;What will we do by hand for now?&lt;/li&gt;
&lt;li&gt;What result would make us stop, change direction, or keep going?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you can answer those, a capable developer can usually get a first version live in weeks. If you can't, no amount of code will save the six months.&lt;/p&gt;

&lt;p&gt;If you'd like help scoping and shipping your first version, take a look at how I approach &lt;a href="https://muhammadmoiz.dev/services/product-development" rel="noopener noreferrer"&gt;product development from idea to launch&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://leanstartup.co/what-is-an-mvp/" rel="noopener noreferrer"&gt;What is an MVP? (Lean Startup Co., quoting Eric Ries)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://paulgraham.com/ds.html" rel="noopener noreferrer"&gt;Do Things That Don't Scale, Paul Graham (July 2013)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://en.wikipedia.org/wiki/Minimum_viable_product" rel="noopener noreferrer"&gt;Minimum viable product (Wikipedia)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://muhammadmoiz.dev/work/shahibulawa" rel="noopener noreferrer"&gt;Shahi Bulawa case study&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Cover photo: Kvalifik on Unsplash&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;I'm Muhammad Moiz, a full-stack developer who builds web apps, SaaS and POS systems, and takes AI-built apps (Lovable, Bolt, Replit) to production. &lt;a href="https://muhammadmoiz.dev/contact" rel="noopener noreferrer"&gt;Get in touch&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>startup</category>
      <category>mvp</category>
      <category>webdev</category>
      <category>saas</category>
    </item>
    <item>
      <title>Paddle vs Stripe vs Lemon Squeezy for SaaS (I Shipped Paddle)</title>
      <dc:creator>Muhammad Moiz</dc:creator>
      <pubDate>Thu, 12 Nov 2026 05:09:37 +0000</pubDate>
      <link>https://dev.to/muhammadmoiz269/paddle-vs-stripe-vs-lemon-squeezy-for-saas-i-shipped-paddle-2o96</link>
      <guid>https://dev.to/muhammadmoiz269/paddle-vs-stripe-vs-lemon-squeezy-for-saas-i-shipped-paddle-2o96</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://muhammadmoiz.dev/blog/paddle-vs-stripe" rel="noopener noreferrer"&gt;muhammadmoiz.dev&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;For most early-stage SaaS products selling worldwide, the Paddle vs Stripe question comes down to one thing: who is legally responsible for sales tax and VAT on every sale. Paddle (and Lemon Squeezy) act as your merchant of record and handle that for a higher fee, while plain Stripe costs less per transaction but leaves tax registration, filing and compliance with you. I run Paddle in production on Timegram, my time-tracking SaaS, so this comparison mixes current pricing (checked in November 2026) with what the choice feels like after launch.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is a merchant of record, in plain English?
&lt;/h2&gt;

&lt;p&gt;A merchant of record (MoR) is the company that legally sells your product to the customer. When Paddle is your MoR, the buyer is technically purchasing from Paddle, and Paddle then pays you. That has a few practical effects:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The MoR calculates, collects and remits sales tax, VAT and GST in the countries where your customers live.&lt;/li&gt;
&lt;li&gt;It carries the liability for the payment, including refunds and chargebacks.&lt;/li&gt;
&lt;li&gt;Its name, not yours, appears on the customer's card statement.&lt;/li&gt;
&lt;li&gt;You still own the product, the customer relationship, support and your terms of use.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;With plain Stripe, &lt;strong&gt;you&lt;/strong&gt; are the merchant of record. Stripe processes the card, but if a customer in Germany or Australia buys your subscription, working out whether you owe VAT there, registering, and filing returns is your job. Stripe Tax can calculate and collect the tax, but it only does so in places where you have registered.&lt;/p&gt;

&lt;p&gt;For a solo founder or a small team, that difference matters more than any percentage point. Tax compliance across dozens of countries is real admin work, and it usually lands on the founder's desk at the worst possible time.&lt;/p&gt;

&lt;h2&gt;
  
  
  Paddle vs Stripe vs Lemon Squeezy: fees compared
&lt;/h2&gt;

&lt;p&gt;Here is what each official pricing page listed when I checked in November 2026 (US pricing for Stripe):&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;Paddle&lt;/th&gt;
&lt;th&gt;Stripe (you are the merchant)&lt;/th&gt;
&lt;th&gt;Stripe Managed Payments&lt;/th&gt;
&lt;th&gt;Lemon Squeezy&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Base fee&lt;/td&gt;
&lt;td&gt;5% + 50¢ per checkout transaction&lt;/td&gt;
&lt;td&gt;2.9% + 30¢ per domestic card&lt;/td&gt;
&lt;td&gt;3.5% on top of standard Stripe payment fees&lt;/td&gt;
&lt;td&gt;5% + 50¢&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Merchant of record&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;Yes (Stripe)&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Sales tax / VAT handled&lt;/td&gt;
&lt;td&gt;Included&lt;/td&gt;
&lt;td&gt;Stripe Tax: 0.5% (no-code) or 50¢ per transaction (API), only where you are registered&lt;/td&gt;
&lt;td&gt;Included, 80+ countries&lt;/td&gt;
&lt;td&gt;Included&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Subscription billing&lt;/td&gt;
&lt;td&gt;Included&lt;/td&gt;
&lt;td&gt;Stripe Billing: 0.7% of billing volume (pay as you go)&lt;/td&gt;
&lt;td&gt;Requires Stripe Billing&lt;/td&gt;
&lt;td&gt;Included&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;International cards&lt;/td&gt;
&lt;td&gt;Not listed as extra&lt;/td&gt;
&lt;td&gt;+1.5%&lt;/td&gt;
&lt;td&gt;Standard Stripe fees apply&lt;/td&gt;
&lt;td&gt;"Small additional fees" outside the US, amount not stated&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Currency conversion&lt;/td&gt;
&lt;td&gt;Not listed as extra&lt;/td&gt;
&lt;td&gt;+1%&lt;/td&gt;
&lt;td&gt;Standard Stripe fees apply&lt;/td&gt;
&lt;td&gt;Not quantified&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Disputes&lt;/td&gt;
&lt;td&gt;Handled by Paddle&lt;/td&gt;
&lt;td&gt;$15 per dispute&lt;/td&gt;
&lt;td&gt;Handled by Stripe&lt;/td&gt;
&lt;td&gt;Handled by Lemon Squeezy&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;A few things the table doesn't show. Paddle says products priced under $10 need custom pricing. Stripe's dispute fee has more parts than one number: a $15 fee when a dispute arrives, another $15 if you counter it manually (refunded if you win). And the Lemon Squeezy page carries a link to a 2026 update about Stripe Managed Payments, which I cover below.&lt;/p&gt;

&lt;h3&gt;
  
  
  A worked example: one $50 monthly subscription
&lt;/h3&gt;

&lt;p&gt;Take a single $50 payment from a US customer on a domestic card:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Paddle:&lt;/strong&gt; 5% + 50¢ = &lt;strong&gt;$3.00&lt;/strong&gt;, with tax handling, billing and disputes included.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Stripe, self-managed:&lt;/strong&gt; 2.9% + 30¢ = $1.75, plus 0.7% Stripe Billing = $0.35, plus 50¢ Stripe Tax via the API if you are registered in that state = &lt;strong&gt;about $2.60&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Same Stripe sale with an international card that needs conversion:&lt;/strong&gt; add 1.5% + 1% = $1.25, bringing it to &lt;strong&gt;about $3.85&lt;/strong&gt;.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;So plain Stripe is the lowest-cost option for domestic sales, and the gap narrows or flips once you add international cards, currency conversion, and the cost of an accountant filing tax returns in other countries. That last cost never appears on a pricing page, but it is very real.&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%2Fimages.unsplash.com%2Fphoto-1551288049-bebda4e38f71%3Fw%3D1200%26q%3D80" 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%2Fimages.unsplash.com%2Fphoto-1551288049-bebda4e38f71%3Fw%3D1200%26q%3D80" alt="Analytics graphs on a laptop screen showing revenue and performance metrics" width="1200" height="800"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Photo: Luke Chesser on Unsplash&lt;/em&gt;&lt;/p&gt;
&lt;h2&gt;
  
  
  Is Lemon Squeezy still a good choice in 2026?
&lt;/h2&gt;

&lt;p&gt;Lemon Squeezy was acquired by Stripe in 2024. In a January 28, 2026 update on its blog, the team said Lemon Squeezy is being folded into Stripe Managed Payments, which they present as its next version, and that the aim is to give existing users an easy way to migrate. The same post admits support had been slower and product updates fewer over the previous year.&lt;/p&gt;

&lt;p&gt;Lemon Squeezy still works, and its pricing page still lists 5% + 50¢. But if you are starting a new SaaS today, I would not build on a platform whose own team describes it as being merged into something else. If you like the Lemon Squeezy model, look at Stripe Managed Payments directly.&lt;/p&gt;
&lt;h3&gt;
  
  
  What Stripe Managed Payments actually is
&lt;/h3&gt;

&lt;p&gt;Managed Payments is Stripe acting as your merchant of record. According to Stripe's docs, it handles sales tax, VAT and GST in more than 80 countries, plus fraud prevention, disputes and transaction-level customer support. Before you choose it, check the limits:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;It only works with &lt;strong&gt;Stripe Checkout and Payment Links&lt;/strong&gt;, not embedded Elements forms.&lt;/li&gt;
&lt;li&gt;Subscriptions must be created through Checkout or Payment Links and use Stripe Billing.&lt;/li&gt;
&lt;li&gt;It doesn't support &lt;strong&gt;Stripe Connect&lt;/strong&gt;, so marketplaces and platforms are out.&lt;/li&gt;
&lt;li&gt;It is for &lt;strong&gt;fully automated digital products&lt;/strong&gt;: software, SaaS, courses, digital media. Consulting, development, design services and physical goods are excluded.&lt;/li&gt;
&lt;li&gt;Your business must be based in a supported country. The list includes the US, Canada, the UK, most of the EU, Switzerland, Norway, Australia, Hong Kong, Japan and Singapore.&lt;/li&gt;
&lt;li&gt;Stripe runs an eligibility review, and you need to keep a low dispute rate to stay on it.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The fee is 3.5% per transaction on top of the normal Stripe payment fees. On the $50 example above, that is $1.75 + $1.75 = $3.50 before any Billing charges, which puts it in the same range as Paddle.&lt;/p&gt;
&lt;h2&gt;
  
  
  Paddle vs Stripe: which should you pick?
&lt;/h2&gt;

&lt;p&gt;There's no single winner. Here is the decision framework I'd use with a client:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Choose Paddle (or another MoR) if:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;You sell a SaaS or software product to customers in many countries from day one.&lt;/li&gt;
&lt;li&gt;You are a small team and don't want to register for VAT or sales tax in multiple places.&lt;/li&gt;
&lt;li&gt;You are fine with a Paddle-branded checkout and Paddle's name on the card statement.&lt;/li&gt;
&lt;li&gt;Your prices are above $10, so the 50¢ fixed fee doesn't eat your margin.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Choose plain Stripe if:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Most of your customers are in one country where you are already registered for tax.&lt;/li&gt;
&lt;li&gt;You need full control of the checkout UI (Stripe Elements) or a marketplace model (Stripe Connect).&lt;/li&gt;
&lt;li&gt;You sell services, physical goods or anything an MoR won't accept.&lt;/li&gt;
&lt;li&gt;You have an accountant or a finance person who can handle tax filings.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Consider Stripe Managed Payments if:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;You want MoR coverage but prefer Stripe's API, dashboard and ecosystem.&lt;/li&gt;
&lt;li&gt;Your business is in a supported country and your product is purely digital.&lt;/li&gt;
&lt;li&gt;A hosted Checkout page is acceptable for your product.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;
  
  
  What I learned shipping Paddle in production
&lt;/h2&gt;

&lt;p&gt;Timegram uses Paddle for payments in production. The appeal of the MoR model for a SaaS like that is simple: Paddle is the seller of record, so the tax side of international sales sits with Paddle rather than with the product team.&lt;/p&gt;

&lt;p&gt;The main engineering lesson applies to any provider: keep billing logic behind your own interface. Your app should ask "is this account on an active paid plan?" and never care which provider answered. That way, switching from Lemon Squeezy to Managed Payments, or from Stripe to Paddle, touches one module instead of the whole codebase.&lt;/p&gt;

&lt;p&gt;Here is a simplified sketch of that pattern in TypeScript:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight typescript"&gt;&lt;code&gt;&lt;span class="c1"&gt;// billing/types.ts: your app only depends on this shape&lt;/span&gt;
&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="kd"&gt;type&lt;/span&gt; &lt;span class="nc"&gt;PlanStatus&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s2"&gt;"trialing"&lt;/span&gt; &lt;span class="o"&gt;|&lt;/span&gt; &lt;span class="s2"&gt;"active"&lt;/span&gt; &lt;span class="o"&gt;|&lt;/span&gt; &lt;span class="s2"&gt;"past_due"&lt;/span&gt; &lt;span class="o"&gt;|&lt;/span&gt; &lt;span class="s2"&gt;"canceled"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="kd"&gt;interface&lt;/span&gt; &lt;span class="nc"&gt;Subscription&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="n"&gt;accountId&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;string&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="n"&gt;plan&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"starter"&lt;/span&gt; &lt;span class="o"&gt;|&lt;/span&gt; &lt;span class="s2"&gt;"pro"&lt;/span&gt; &lt;span class="o"&gt;|&lt;/span&gt; &lt;span class="s2"&gt;"team"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="n"&gt;status&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nc"&gt;PlanStatus&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="n"&gt;renewsAt&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nb"&gt;Date&lt;/span&gt; &lt;span class="o"&gt;|&lt;/span&gt; &lt;span class="kc"&gt;null&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="kd"&gt;interface&lt;/span&gt; &lt;span class="nc"&gt;BillingProvider&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nf"&gt;createCheckoutUrl&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;accountId&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;string&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;plan&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nc"&gt;Subscription&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"plan"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nb"&gt;Promise&lt;/span&gt;&lt;span class="o"&gt;&amp;lt;&lt;/span&gt;&lt;span class="kt"&gt;string&lt;/span&gt;&lt;span class="o"&gt;&amp;gt;&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="c1"&gt;// Turn a verified provider webhook into your own Subscription record&lt;/span&gt;
  &lt;span class="nf"&gt;parseWebhook&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;rawBody&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;string&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;signature&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;string&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nb"&gt;Promise&lt;/span&gt;&lt;span class="o"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;Subscription&lt;/span&gt; &lt;span class="o"&gt;|&lt;/span&gt; &lt;span class="kc"&gt;null&lt;/span&gt;&lt;span class="o"&gt;&amp;gt;&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="c1"&gt;// Feature checks read your database, never the provider's API&lt;/span&gt;
&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;hasPaidAccess&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;sub&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nc"&gt;Subscription&lt;/span&gt; &lt;span class="o"&gt;|&lt;/span&gt; &lt;span class="kc"&gt;undefined&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kt"&gt;boolean&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;sub&lt;/span&gt;&lt;span class="o"&gt;?&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;status&lt;/span&gt; &lt;span class="o"&gt;===&lt;/span&gt; &lt;span class="s2"&gt;"active"&lt;/span&gt; &lt;span class="o"&gt;||&lt;/span&gt; &lt;span class="n"&gt;sub&lt;/span&gt;&lt;span class="o"&gt;?&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;status&lt;/span&gt; &lt;span class="o"&gt;===&lt;/span&gt; &lt;span class="s2"&gt;"trialing"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Each provider (Paddle, Stripe, Lemon Squeezy) gets its own small adapter that implements &lt;code&gt;BillingProvider&lt;/code&gt;. Webhooks update a subscriptions table in your database, and the rest of the app reads from there. It also means a provider outage doesn't lock paying users out of your product.&lt;/p&gt;

&lt;h2&gt;
  
  
  Checklist before you integrate any payment provider
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Write down where your customers are. One country or worldwide changes the answer.&lt;/li&gt;
&lt;li&gt;Check that your product type is accepted. MoRs reject services and some content categories.&lt;/li&gt;
&lt;li&gt;Calculate fees on your real price point, including international cards and conversion.&lt;/li&gt;
&lt;li&gt;Decide whether a hosted checkout is acceptable or you need a fully custom one.&lt;/li&gt;
&lt;li&gt;Plan webhook handling: signature verification, retries and idempotency.&lt;/li&gt;
&lt;li&gt;Store subscription state in your own database, as in the pattern above.&lt;/li&gt;
&lt;li&gt;Test upgrades, downgrades, failed payments and cancellations in sandbox mode before launch.&lt;/li&gt;
&lt;li&gt;Read the provider's payout schedule so cash flow doesn't surprise you.&lt;/li&gt;
&lt;/ol&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Don't over-optimise fees on day one:&lt;/strong&gt; Before you have revenue, the difference between 2.6% and 5% matters far less than launching quickly and staying tax compliant. You can switch providers later if billing sits behind your own interface.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  What this means for your SaaS
&lt;/h2&gt;

&lt;p&gt;If you are a founder choosing between Paddle vs Stripe for a new product, the honest answer is that an MoR (Paddle or Stripe Managed Payments) is usually the right default for a small team selling software internationally. Plain Stripe becomes the better value once you have the volume, the finance help and the need for a fully custom checkout or a marketplace.&lt;/p&gt;

&lt;p&gt;The part people underestimate is the integration itself: webhooks, plan changes, trials, failed payments and keeping your database in sync. If you are planning a SaaS and want billing done right from the first version, that is part of what I cover in &lt;a href="https://muhammadmoiz.dev/services/product-development" rel="noopener noreferrer"&gt;product development&lt;/a&gt;. You can also see my &lt;a href="https://muhammadmoiz.dev/blog/supabase-vs-firebase" rel="noopener noreferrer"&gt;Supabase vs Firebase comparison&lt;/a&gt; for the backend side of the same decision, or check &lt;a href="https://muhammadmoiz.dev/pricing" rel="noopener noreferrer"&gt;pricing&lt;/a&gt; for how I scope projects.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.paddle.com/pricing" rel="noopener noreferrer"&gt;Paddle pricing&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.paddle.com/blog/what-is-merchant-of-record" rel="noopener noreferrer"&gt;Paddle: What is a merchant of record?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://stripe.com/pricing" rel="noopener noreferrer"&gt;Stripe pricing&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.stripe.com/payments/managed-payments" rel="noopener noreferrer"&gt;Stripe docs: Managed Payments&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://docs.stripe.com/payments/managed-payments/eligibility" rel="noopener noreferrer"&gt;Stripe docs: Managed Payments eligibility&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.lemonsqueezy.com/pricing" rel="noopener noreferrer"&gt;Lemon Squeezy pricing&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.lemonsqueezy.com/blog/2026-update" rel="noopener noreferrer"&gt;Lemon Squeezy: 2026 update&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Cover photo: rupixen on Unsplash&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;I'm Muhammad Moiz, a full-stack developer who builds web apps, SaaS and POS systems, and takes AI-built apps (Lovable, Bolt, Replit) to production. &lt;a href="https://muhammadmoiz.dev/contact" rel="noopener noreferrer"&gt;Get in touch&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>saas</category>
      <category>stripe</category>
      <category>startup</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Progressive Web Apps vs Native App: When a PWA Is Enough</title>
      <dc:creator>Muhammad Moiz</dc:creator>
      <pubDate>Wed, 11 Nov 2026 05:07:13 +0000</pubDate>
      <link>https://dev.to/muhammadmoiz269/progressive-web-apps-vs-native-app-when-a-pwa-is-enough-329d</link>
      <guid>https://dev.to/muhammadmoiz269/progressive-web-apps-vs-native-app-when-a-pwa-is-enough-329d</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://muhammadmoiz.dev/blog/progressive-web-apps-vs-native-app" rel="noopener noreferrer"&gt;muhammadmoiz.dev&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;If you are weighing progressive web apps vs native app development, the short answer is this: a PWA is enough when your users mostly work in the foreground, on screens you control, and you need one codebase with fast updates. Go native (or React Native) when you depend on background work, deep hardware access, or iOS features that Safari still does not expose. Below is how to tell which side of that line your product sits on, based on current browser support data and on building an offline-first restaurant POS that runs in the browser.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is a PWA, in plain terms?
&lt;/h2&gt;

&lt;p&gt;A progressive web app is a website that can behave like an installed app. Technically it is still a web page running inside a browser engine, but it adds two things:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;A web app manifest&lt;/strong&gt;: a small JSON file with the app's name, icons, start URL and display mode. This is what lets a browser offer "Install" or "Add to Home Screen".&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A service worker&lt;/strong&gt; (optional but common): a script that sits between your app and the network. It can serve cached files when the device is offline and, on some browsers, run tasks in the background.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Once installed, a PWA gets its own icon and opens in its own window without the browser address bar. To the user it feels like an app. Under the hood, the browser is still doing the work, and that is the root of every limitation discussed below.&lt;/p&gt;

&lt;p&gt;A native app, by contrast, is built for the operating system directly (Swift/Kotlin, or a cross-platform toolkit like React Native or Flutter that compiles to native components) and is distributed through the App Store or Google Play.&lt;/p&gt;

&lt;h2&gt;
  
  
  Progressive web apps vs native app: the quick comparison
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;PWA&lt;/th&gt;
&lt;th&gt;Native app&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Codebase&lt;/td&gt;
&lt;td&gt;One web codebase for desktop, Android, iOS&lt;/td&gt;
&lt;td&gt;Separate builds per platform (or a cross-platform framework)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Distribution&lt;/td&gt;
&lt;td&gt;A URL, plus optional store listings&lt;/td&gt;
&lt;td&gt;App Store and Google Play review&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Updates&lt;/td&gt;
&lt;td&gt;Deploy to your server, users get it on next load&lt;/td&gt;
&lt;td&gt;Store review, then users must update&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Found by search engines&lt;/td&gt;
&lt;td&gt;Yes, pages can be indexed&lt;/td&gt;
&lt;td&gt;Store search only (unless you also have a website)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Offline use&lt;/td&gt;
&lt;td&gt;Yes, with a service worker and local storage&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Background sync on iOS&lt;/td&gt;
&lt;td&gt;Not supported in Safari&lt;/td&gt;
&lt;td&gt;Supported via OS APIs&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Push notifications on iOS&lt;/td&gt;
&lt;td&gt;iOS 16.4+, only when added to Home Screen&lt;/td&gt;
&lt;td&gt;Supported&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Bluetooth / USB hardware&lt;/td&gt;
&lt;td&gt;Chromium browsers only, not Safari&lt;/td&gt;
&lt;td&gt;Supported&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Custom install button on iOS&lt;/td&gt;
&lt;td&gt;Not supported&lt;/td&gt;
&lt;td&gt;Not applicable (store install)&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The rows that matter most are the bottom four. Everything above them is where PWAs usually win.&lt;/p&gt;

&lt;h2&gt;
  
  
  What PWAs can't do on iOS (as of November 2026)
&lt;/h2&gt;

&lt;p&gt;Most "PWA vs native" decisions are really "how much do we care about iPhone users?" decisions. Android with Chrome supports far more of the web platform than iOS does. I checked MDN's browser compatibility data in November 2026, and these are the gaps that most often push a project toward native:&lt;/p&gt;

&lt;h3&gt;
  
  
  Push notifications need a Home Screen install
&lt;/h3&gt;

&lt;p&gt;Safari on iOS added the Push API in version 16.4, but MDN notes it only works for web apps saved to the Home Screen. A user who just visits your site in Safari cannot get push messages. That means your onboarding has to talk people through "Share, then Add to Home Screen" before notifications even become possible.&lt;/p&gt;

&lt;h3&gt;
  
  
  No custom install prompt
&lt;/h3&gt;

&lt;p&gt;On Chrome and Edge, your app can listen for the &lt;code&gt;beforeinstallprompt&lt;/code&gt; event and show its own "Install app" button at a sensible moment. Safari does not support that event, and MDN states plainly that this technique does not work on iOS. Installing is entirely manual for iPhone users. Since iOS 16.4, they can at least do it from the Share menu in Safari, Chrome, Edge, Firefox and Orion, not only Safari.&lt;/p&gt;

&lt;h3&gt;
  
  
  No background sync or background fetch
&lt;/h3&gt;

&lt;p&gt;The Background Synchronization API lets a service worker retry a failed request once the connection returns, even after the user has closed the tab. Periodic Background Sync and Background Fetch go further. According to MDN's compatibility data, Safari supports none of these. On iOS, your app can only sync while it is open.&lt;/p&gt;

&lt;h3&gt;
  
  
  No Bluetooth, USB or serial hardware access
&lt;/h3&gt;

&lt;p&gt;Web Bluetooth, WebUSB and Web Serial exist in Chromium browsers but not in Safari. If your product needs to talk to a card reader, label printer, scale or other peripheral from an iPhone or iPad, a PWA alone cannot do it.&lt;/p&gt;

&lt;h3&gt;
  
  
  Smaller gaps
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Badging&lt;/strong&gt; (the number on the app icon) works on iOS 16.4+ for Home Screen web apps.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Screen Wake Lock&lt;/strong&gt; (keeping the screen on) arrived in Safari 16.4, but MDN notes it did not work in Home Screen web apps until iOS 18.4.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Vibration&lt;/strong&gt; is not supported in Safari at all.&lt;/li&gt;
&lt;/ul&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Check the EU caveat:&lt;/strong&gt; Historically every iOS browser had to use WebKit, so Chrome on iPhone had Safari's limits. MDN notes that since iOS 17.4 Apple allows other browser engines in the EU, so behaviour there can differ. Test on the devices and regions your customers actually use.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Offline storage: how much data can a PWA keep?
&lt;/h2&gt;

&lt;p&gt;Offline-first apps live or die on local storage, so this deserves its own section. Small key-value data can go in &lt;code&gt;localStorage&lt;/code&gt;, which is capped at about 5 MiB per origin. Anything serious (orders, products, customers) belongs in IndexedDB, usually through a library rather than the raw API.&lt;/p&gt;

&lt;p&gt;MDN's storage guide gives the current quota rules:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Chrome and Edge&lt;/strong&gt;: an origin can use up to 60% of total disk size.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Safari (macOS 14 and iOS 17 onward)&lt;/strong&gt;: around 60% of total disk for browser apps and Home Screen web apps, and around 15% when the site runs inside another app's embedded web view.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Firefox&lt;/strong&gt;: in best-effort mode, the smaller of 10% of the disk or a 10 GiB group limit.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The bigger risk is not quota, it is &lt;strong&gt;eviction&lt;/strong&gt;. By default, browser data is "best-effort", meaning the browser may delete it under storage pressure. Safari goes further: with cross-site tracking prevention on, it removes script-created data for origins the user has not interacted with in the last seven days of browser use. When eviction happens, the whole origin's data goes at once.&lt;/p&gt;

&lt;p&gt;Two practical defences:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight typescript"&gt;&lt;code&gt;&lt;span class="c1"&gt;// Ask the browser to treat this origin's data as persistent.&lt;/span&gt;
&lt;span class="c1"&gt;// Chrome and Safari decide silently based on how the user engages with the site;&lt;/span&gt;
&lt;span class="c1"&gt;// Firefox shows a permission prompt.&lt;/span&gt;
&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="k"&gt;async&lt;/span&gt; &lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;requestDurableStorage&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nb"&gt;Promise&lt;/span&gt;&lt;span class="o"&gt;&amp;lt;&lt;/span&gt;&lt;span class="kt"&gt;boolean&lt;/span&gt;&lt;span class="o"&gt;&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="n"&gt;navigator&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;storage&lt;/span&gt;&lt;span class="o"&gt;?&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;persist&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="kc"&gt;false&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;alreadyPersisted&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="n"&gt;navigator&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;storage&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;persisted&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;alreadyPersisted&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="kc"&gt;true&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;navigator&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;storage&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;persist&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="c1"&gt;// Show the user (or your support team) how close the app is to its limit.&lt;/span&gt;
&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="k"&gt;async&lt;/span&gt; &lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;storageReport&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nb"&gt;Promise&lt;/span&gt;&lt;span class="o"&gt;&amp;lt;&lt;/span&gt;&lt;span class="kt"&gt;string&lt;/span&gt;&lt;span class="o"&gt;&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="n"&gt;navigator&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;storage&lt;/span&gt;&lt;span class="o"&gt;?&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;estimate&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="s2"&gt;"Storage estimate not available"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;usage&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;quota&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="n"&gt;navigator&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;storage&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;estimate&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;pct&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;quota&lt;/span&gt; &lt;span class="o"&gt;?&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;usage&lt;/span&gt; &lt;span class="o"&gt;/&lt;/span&gt; &lt;span class="n"&gt;quota&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="mi"&gt;100&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;toFixed&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"?"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="sb"&gt;`Using ${(usage / 1_048_576).toFixed(1)} MB of local storage (${pct}% of quota)`&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;And the rule that matters more than any API call: &lt;strong&gt;local data must never be the only copy of anything important&lt;/strong&gt;. Sync it to a server as soon as a connection is available, and design the app so a wiped device can rebuild itself from the server.&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%2Fimages.unsplash.com%2Fphoto-1556742393-d75f468bfcb0%3Fw%3D1200%26q%3D80" 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%2Fimages.unsplash.com%2Fphoto-1556742393-d75f468bfcb0%3Fw%3D1200%26q%3D80" alt="A barista in an apron using a tablet at a wooden café counter" width="1200" height="800"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Photo: Nathan Dumlao on Unsplash&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Lessons from an offline-first POS that runs in the browser
&lt;/h2&gt;

&lt;p&gt;I spent about two years as a senior frontend engineer on &lt;a href="https://muhammadmoiz.dev/work/oscar-pos" rel="noopener noreferrer"&gt;Oscar&lt;/a&gt;, a point of sale system for restaurants and retail in Pakistan. It is a React web app, not a store app, and it had to keep taking orders, printing receipts and sending tickets to the kitchen even with the internet down. A few things that experience taught me about when the web is enough:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The browser handled offline data well.&lt;/strong&gt; Oscar keeps its data in a local WatermelonDB database on browser storage, so the POS works the same with or without a connection, and nobody has to install anything. Changes sync to a Django backend when the connection returns, and the server stays the source of truth for reporting. I wrote more about that architecture in &lt;a href="https://muhammadmoiz.dev/blog/offline-first-pos-react" rel="noopener noreferrer"&gt;Offline-First POS: Lessons From Building Oscar in React&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Real-time features need an offline plan of their own.&lt;/strong&gt; Orders reached the kitchen display system over WebSockets. Every feature like that needs a decision, made at design time, about what happens when the socket drops.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Hardware was the hard part.&lt;/strong&gt; Restaurants need receipt, kitchen and bar printers. Oscar connects to local printers through QZ Tray, a printer bridge, and I built the routing so each ticket lands on the right printer: receipts at the counter, tickets in the kitchen, drinks at the bar. That pattern (a web app plus a local helper for hardware) is a useful middle ground, but it is one more component to set up and support.&lt;/p&gt;

&lt;p&gt;The broader lesson: Oscar ran on counters and devices the business controlled, in the foreground, all shift long. That is the ideal case for a web app. A consumer app that must wake up in the background on a stranger's iPhone is the opposite case.&lt;/p&gt;

&lt;h2&gt;
  
  
  When a PWA is enough: a checklist
&lt;/h2&gt;

&lt;p&gt;Answer these honestly. If most of your answers land on the left, a PWA (or a plain responsive web app) is probably the right first build.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt; &lt;strong&gt;Do users work with the app open?&lt;/strong&gt; Dashboards, POS screens, booking tools, internal tools and B2B SaaS are used in the foreground. A PWA fits. Apps that must react while closed (trackers, messengers with guaranteed delivery) lean native.&lt;/li&gt;
&lt;li&gt; &lt;strong&gt;Who owns the devices?&lt;/strong&gt; If you control the hardware (counter tablets, staff laptops, Android devices), you can standardise on Chrome and get the full PWA feature set. If the audience is mostly iPhone consumers, plan around the iOS gaps above.&lt;/li&gt;
&lt;li&gt; &lt;strong&gt;Do you need peripherals?&lt;/strong&gt; Printers, scanners, card readers and Bluetooth devices push you toward native, a cross-platform app, or a local bridge like the Oscar setup.&lt;/li&gt;
&lt;li&gt; &lt;strong&gt;How important are push notifications?&lt;/strong&gt; If they are core to retention and your users are on iPhone, the "add to Home Screen first" step will cost you opt-ins.&lt;/li&gt;
&lt;li&gt; &lt;strong&gt;Does discovery come from Google or from the app stores?&lt;/strong&gt; PWAs are web pages, so they can rank in search and be shared as a link. Store presence matters more for some consumer categories. You can also wrap a PWA for some stores (MDN points to tools like PWABuilder), but check each store's rules first.&lt;/li&gt;
&lt;li&gt; &lt;strong&gt;How often will you ship?&lt;/strong&gt; Web deploys reach everyone on the next load. Store apps add review time and update lag.&lt;/li&gt;
&lt;li&gt; &lt;strong&gt;What is the budget?&lt;/strong&gt; One web codebase is usually less work than two native apps. React Native narrows that gap if you need native features.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  What this means for founders and app owners
&lt;/h2&gt;

&lt;p&gt;For most early-stage products, start on the web. A well-built responsive web app with a manifest and a service worker covers desktop, Android and most iPhone use, can be found on Google, and costs less to build and maintain than separate native apps. If you hit a real platform wall (background work, hardware, iOS push at scale), you can add a React Native app later and reuse your backend, API and much of your business logic.&lt;/p&gt;

&lt;p&gt;The mistake to avoid is choosing a PWA and then discovering the iOS gaps after launch. Write down the device features your product depends on, check each one against current browser support, and prototype the riskiest one first.&lt;/p&gt;

&lt;p&gt;If you are planning an offline-first app or a POS and want a second opinion on web vs native, take a look at my &lt;a href="https://muhammadmoiz.dev/services/product-development" rel="noopener noreferrer"&gt;product development service&lt;/a&gt; or the &lt;a href="https://muhammadmoiz.dev/services/react-development" rel="noopener noreferrer"&gt;React development service&lt;/a&gt;, or see how the &lt;a href="https://muhammadmoiz.dev/work/oscar-pos" rel="noopener noreferrer"&gt;Oscar POS case study&lt;/a&gt; handled it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps" rel="noopener noreferrer"&gt;MDN: Progressive web apps&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps/Guides/What_is_a_progressive_web_app" rel="noopener noreferrer"&gt;MDN: What is a progressive web app?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps/Guides/Making_PWAs_installable" rel="noopener noreferrer"&gt;MDN: Making PWAs installable&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps/Guides/Offline_and_background_operation" rel="noopener noreferrer"&gt;MDN: Offline and background operation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://developer.mozilla.org/en-US/docs/Web/API/Storage_API/Storage_quotas_and_eviction_criteria" rel="noopener noreferrer"&gt;MDN: Storage quotas and eviction criteria&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/mdn/browser-compat-data" rel="noopener noreferrer"&gt;MDN browser-compat-data (PushManager, SyncManager, BackgroundFetchManager, BeforeInstallPromptEvent, Bluetooth, USB, Serial, Navigator)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Cover photo: Thom Bradley on Unsplash&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;I'm Muhammad Moiz, a full-stack developer who builds web apps, SaaS and POS systems, and takes AI-built apps (Lovable, Bolt, Replit) to production. &lt;a href="https://muhammadmoiz.dev/contact" rel="noopener noreferrer"&gt;Get in touch&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>pwa</category>
      <category>webdev</category>
      <category>mobile</category>
      <category>offlinefirst</category>
    </item>
    <item>
      <title>Lovable SEO: Why Your Lovable Site Isn't on Google (and the Fix)</title>
      <dc:creator>Muhammad Moiz</dc:creator>
      <pubDate>Thu, 05 Nov 2026 05:09:38 +0000</pubDate>
      <link>https://dev.to/muhammadmoiz269/lovable-seo-why-your-lovable-site-isnt-on-google-and-the-fix-4iin</link>
      <guid>https://dev.to/muhammadmoiz269/lovable-seo-why-your-lovable-site-isnt-on-google-and-the-fix-4iin</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://muhammadmoiz.dev/blog/lovable-seo" rel="noopener noreferrer"&gt;muhammadmoiz.dev&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Lovable SEO problems usually come down to one thing: a Lovable project is a client-side rendered React app, so the HTML a search engine first receives is an almost empty shell, and all your text, titles and links only appear after JavaScript runs. Google can render JavaScript, but it does so in a slower, separate step, and other crawlers may not do it at all. The reliable fix is to serve real HTML for every page you want ranked, which for most growing products means pre-rendering or moving the public pages to a framework like Next.js.&lt;/p&gt;

&lt;p&gt;This post explains why it happens, how to check your own site in five minutes, and which fix fits which situation.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why isn't my Lovable site showing up on Google?
&lt;/h2&gt;

&lt;p&gt;Lovable generates React projects built with Vite. You can see this in Lovable's own &lt;code&gt;lovable-tagger&lt;/code&gt; package on npm, which is published from Lovable's repository and describes itself as a set of Vite plugins. A default Vite and React setup is a single-page application (SPA): the server sends one small HTML file, the browser downloads a JavaScript bundle, and React draws the page.&lt;/p&gt;

&lt;p&gt;For a human visitor that works fine. For a search engine, the first response looks roughly like this:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight html"&gt;&lt;code&gt;&lt;span class="cp"&gt;&amp;lt;!doctype html&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;html&lt;/span&gt; &lt;span class="na"&gt;lang=&lt;/span&gt;&lt;span class="s"&gt;"en"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;
  &lt;span class="nt"&gt;&amp;lt;head&amp;gt;&lt;/span&gt;
    &lt;span class="nt"&gt;&amp;lt;title&amp;gt;&lt;/span&gt;My App&lt;span class="nt"&gt;&amp;lt;/title&amp;gt;&lt;/span&gt;
    &lt;span class="nt"&gt;&amp;lt;script &lt;/span&gt;&lt;span class="na"&gt;type=&lt;/span&gt;&lt;span class="s"&gt;"module"&lt;/span&gt; &lt;span class="na"&gt;src=&lt;/span&gt;&lt;span class="s"&gt;"/assets/index-a1b2c3.js"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&amp;lt;/script&amp;gt;&lt;/span&gt;
  &lt;span class="nt"&gt;&amp;lt;/head&amp;gt;&lt;/span&gt;
  &lt;span class="nt"&gt;&amp;lt;body&amp;gt;&lt;/span&gt;
    &lt;span class="nt"&gt;&amp;lt;div&lt;/span&gt; &lt;span class="na"&gt;id=&lt;/span&gt;&lt;span class="s"&gt;"root"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&amp;lt;/div&amp;gt;&lt;/span&gt;
  &lt;span class="nt"&gt;&amp;lt;/body&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;/html&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;There is no headline, no product copy, no internal links and no page-specific title in that file. Everything a ranking system cares about is locked inside the JavaScript.&lt;/p&gt;

&lt;p&gt;The Next.js team's SEO course puts it plainly: with client-side rendering, the first load usually serves a single HTML file "with little to no content" until the JavaScript is fetched and run. Their guidance is that CSR is not recommended when you care about search, and is better suited to dashboards and account pages that don't need to be indexed.&lt;/p&gt;

&lt;h2&gt;
  
  
  Can Google crawl JavaScript sites at all?
&lt;/h2&gt;

&lt;p&gt;Yes, but with caveats that matter for a new site. The same Next.js course describes how pages with client-side content can be pushed into a separate render queue. Rendering costs a search engine more resources than reading plain HTML, so only a smaller share of pages on the web gets rendered, and a URL can sit in the crawl queue anywhere from seconds to a few days before it's processed.&lt;/p&gt;

&lt;p&gt;In practice that means:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Slower discovery.&lt;/strong&gt; Links that only exist after rendering are found later, so deep pages take longer to get crawled.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Uneven indexing.&lt;/strong&gt; Some routes get rendered and indexed, others stay as an empty shell in the index or don't appear at all.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Other engines are weaker.&lt;/strong&gt; The course also notes that some search engines may not have Google's rendering capacity.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Link previews break.&lt;/strong&gt; When someone shares your page on Slack, WhatsApp or LinkedIn, the preview bot reads the HTML head. In an SPA every route shares the same &lt;code&gt;index.html&lt;/code&gt;, so every shared link shows the same generic title and image.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;None of this means a Lovable site can never rank. It means you are starting with a handicap, and for a site whose whole job is to win organic traffic, that handicap is usually the main reason it isn't on page one.&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%2Fimages.unsplash.com%2Fphoto-1542744095-291d1f67b221%3Fw%3D1200%26q%3D80" 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%2Fimages.unsplash.com%2Fphoto-1542744095-291d1f67b221%3Fw%3D1200%26q%3D80" alt="Person working on a laptop reviewing website content" width="1200" height="800"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Photo: Campaign Creators on Unsplash&lt;/em&gt;&lt;/p&gt;
&lt;h2&gt;
  
  
  How to check if your site has a rendering problem
&lt;/h2&gt;

&lt;p&gt;You don't need special tools for a first diagnosis. Run these checks on your homepage and one or two important inner pages.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;View the raw source.&lt;/strong&gt; Open the page, then use your browser's "View page source" (not the inspector). If you can't find your main headline in the source, search engines don't see it on the first pass either.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Fetch it from the terminal.&lt;/strong&gt; This shows exactly what a non-rendering crawler receives:
&lt;/li&gt;
&lt;/ol&gt;
&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl &lt;span class="nt"&gt;-s&lt;/span&gt; https://your-site.com/pricing | &lt;span class="nb"&gt;grep&lt;/span&gt; &lt;span class="nt"&gt;-i&lt;/span&gt; &lt;span class="s2"&gt;"&amp;lt;h1"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;


&lt;p&gt;No output means your &lt;code&gt;h1&lt;/code&gt; only exists after JavaScript runs.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Compare page titles.&lt;/strong&gt; Fetch two different routes and compare the &lt;code&gt;title&lt;/code&gt; tags. If they are identical, every page is competing with the same generic title in search results.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Check for a sitemap and robots file.&lt;/strong&gt; Visit &lt;code&gt;/sitemap.xml&lt;/code&gt; and &lt;code&gt;/robots.txt&lt;/code&gt;. Make sure the sitemap exists and lists every public page, not just the homepage.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Use Google Search Console.&lt;/strong&gt; It tells you which of your pages Google has actually indexed. If you haven't verified your domain there yet, do that first.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If checks 1 to 3 come back empty, the problem is architectural. Better keywords or more blog posts won't fix it on their own.&lt;/p&gt;
&lt;h2&gt;
  
  
  Lovable SEO fixes, from quick wins to the real fix
&lt;/h2&gt;

&lt;p&gt;There are three realistic paths. Which one fits depends on how much of your growth depends on search.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Option&lt;/th&gt;
&lt;th&gt;What it changes&lt;/th&gt;
&lt;th&gt;Effort&lt;/th&gt;
&lt;th&gt;Good for&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Tidy the SPA&lt;/td&gt;
&lt;td&gt;Per-route titles via a head manager, sitemap, robots.txt, clean URLs&lt;/td&gt;
&lt;td&gt;Low&lt;/td&gt;
&lt;td&gt;Apps where search is a minor channel&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Pre-render public routes&lt;/td&gt;
&lt;td&gt;Generates static HTML for marketing pages at build time&lt;/td&gt;
&lt;td&gt;Medium&lt;/td&gt;
&lt;td&gt;Mostly static landing pages with few routes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Move public pages to Next.js&lt;/td&gt;
&lt;td&gt;Server-rendered or static HTML for every public page, built-in metadata, sitemap and robots support&lt;/td&gt;
&lt;td&gt;Medium to high&lt;/td&gt;
&lt;td&gt;Products where organic search is a main acquisition channel&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;
&lt;h3&gt;
  
  
  Option 1: tidy up the SPA
&lt;/h3&gt;

&lt;p&gt;Add a unique title and meta description per route, generate a sitemap that lists every public URL, make sure &lt;code&gt;robots.txt&lt;/code&gt; doesn't block your assets, and use real paths (&lt;code&gt;/pricing&lt;/code&gt;) instead of hash URLs (&lt;code&gt;/#/pricing&lt;/code&gt;). This helps Google once it renders the page, but the empty first response is still there.&lt;/p&gt;
&lt;h3&gt;
  
  
  Option 2: pre-render the public pages
&lt;/h3&gt;

&lt;p&gt;Vite projects can be set up to output static HTML for selected routes at build time. For a site with a handful of mostly static marketing pages, this gets real content into the first response without changing frameworks. It gets awkward once you have many dynamic pages, such as blog posts, listings or product pages pulled from a database.&lt;/p&gt;
&lt;h3&gt;
  
  
  Option 3: move the public pages to Next.js
&lt;/h3&gt;

&lt;p&gt;This is the fix I recommend most often when search is a primary channel. The Next.js SEO course calls static site generation probably the best rendering strategy for SEO, with server-side rendering as the other strong choice, because the content and metadata are in the HTML before any JavaScript runs.&lt;/p&gt;

&lt;p&gt;You also get metadata tooling built in. In the App Router, a page can export a &lt;code&gt;generateMetadata&lt;/code&gt; function that runs on the server, so each blog post or product page gets its own title and description in the initial HTML:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight tsx"&gt;&lt;code&gt;&lt;span class="c1"&gt;// app/guides/[slug]/page.tsx&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="kd"&gt;type&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;Metadata&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;next&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;getGuide&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;@/lib/guides&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;

&lt;span class="kd"&gt;type&lt;/span&gt; &lt;span class="nx"&gt;Props&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;params&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nb"&gt;Promise&lt;/span&gt;&lt;span class="o"&gt;&amp;lt;&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;slug&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kr"&gt;string&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="o"&gt;&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="k"&gt;async&lt;/span&gt; &lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;generateMetadata&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt; &lt;span class="nx"&gt;params&lt;/span&gt; &lt;span class="p"&gt;}:&lt;/span&gt; &lt;span class="nx"&gt;Props&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt; &lt;span class="nb"&gt;Promise&lt;/span&gt;&lt;span class="o"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nx"&gt;Metadata&lt;/span&gt;&lt;span class="o"&gt;&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;slug&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nx"&gt;params&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;guide&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nf"&gt;getGuide&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;slug&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
  &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="na"&gt;title&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;`&lt;/span&gt;&lt;span class="p"&gt;${&lt;/span&gt;&lt;span class="nx"&gt;guide&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;title&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="s2"&gt; | Acme`&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="na"&gt;description&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;guide&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;summary&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="na"&gt;openGraph&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;images&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="nx"&gt;guide&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;coverUrl&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="p"&gt;},&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="k"&gt;default&lt;/span&gt; &lt;span class="k"&gt;async&lt;/span&gt; &lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;GuidePage&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt; &lt;span class="nx"&gt;params&lt;/span&gt; &lt;span class="p"&gt;}:&lt;/span&gt; &lt;span class="nx"&gt;Props&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;slug&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nx"&gt;params&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;guide&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nf"&gt;getGuide&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;slug&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
  &lt;span class="k"&gt;return &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
    &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nt"&gt;article&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
      &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nt"&gt;h1&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="nx"&gt;guide&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;title&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;&lt;span class="p"&gt;&amp;lt;/&lt;/span&gt;&lt;span class="nt"&gt;h1&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
      &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nt"&gt;p&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="nx"&gt;guide&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;summary&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;&lt;span class="p"&gt;&amp;lt;/&lt;/span&gt;&lt;span class="nt"&gt;p&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
    &lt;span class="p"&gt;&amp;lt;/&lt;/span&gt;&lt;span class="nt"&gt;article&lt;/span&gt;&lt;span class="p"&gt;&amp;gt;&lt;/span&gt;
  &lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Sitemaps and robots files are handled by special files in the &lt;code&gt;app&lt;/code&gt; folder, so they stay in sync with your real routes:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight typescript"&gt;&lt;code&gt;&lt;span class="c1"&gt;// app/sitemap.ts&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="kd"&gt;type&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;MetadataRoute&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;next&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;listGuideSlugs&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;@/lib/guides&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;

&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="k"&gt;default&lt;/span&gt; &lt;span class="k"&gt;async&lt;/span&gt; &lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;sitemap&lt;/span&gt;&lt;span class="p"&gt;():&lt;/span&gt; &lt;span class="nb"&gt;Promise&lt;/span&gt;&lt;span class="o"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nx"&gt;MetadataRoute&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;Sitemap&lt;/span&gt;&lt;span class="o"&gt;&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;slugs&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nf"&gt;listGuideSlugs&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt;
  &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;
    &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;url&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;https://acme.com&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="na"&gt;lastModified&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="k"&gt;new&lt;/span&gt; &lt;span class="nc"&gt;Date&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt; &lt;span class="p"&gt;},&lt;/span&gt;
    &lt;span class="p"&gt;...&lt;/span&gt;&lt;span class="nx"&gt;slugs&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;map&lt;/span&gt;&lt;span class="p"&gt;((&lt;/span&gt;&lt;span class="nx"&gt;slug&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;({&lt;/span&gt; &lt;span class="na"&gt;url&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;`https://acme.com/guides/&lt;/span&gt;&lt;span class="p"&gt;${&lt;/span&gt;&lt;span class="nx"&gt;slug&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="s2"&gt;`&lt;/span&gt; &lt;span class="p"&gt;})),&lt;/span&gt;
  &lt;span class="p"&gt;]&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;A common pattern is a partial migration: the logged-in app stays as it is (it doesn't need to be indexed), and only the marketing site, blog and public listing pages move to Next.js. That keeps the cost and risk down.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Don't migrate blindly:&lt;/strong&gt; Before rewriting anything, list the pages that actually need to rank. If it's five static pages, pre-rendering may be enough. If it's hundreds of database-driven pages, a server-rendered framework will save you a lot of pain.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Does React itself hurt SEO?
&lt;/h2&gt;

&lt;p&gt;Not exactly. React is a UI library and can render on the server just fine. The issue is the default setup. The React docs point out that common build tools like Vite start you off with a client-only SPA, which is easier to begin with but can have slower initial loads, and that adding server rendering or static generation yourself takes extra work. That is why the React team recommends starting new apps with a framework. Lovable chose the simpler SPA setup, which is a reasonable choice for prototypes and internal tools, and a weak one for content that needs to rank.&lt;/p&gt;

&lt;h2&gt;
  
  
  What this means for founders with a Lovable site
&lt;/h2&gt;

&lt;p&gt;If your product is a logged-in tool and people find you through ads, referrals or sales, Lovable SEO limitations may not matter much. Fix titles and the sitemap and move on.&lt;/p&gt;

&lt;p&gt;If your plan depends on people finding you on Google, the rendering model is the first thing to fix, before you invest in content or link building. A quick checklist:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Confirm with &lt;code&gt;curl&lt;/code&gt; or View Source whether your key pages have real content in the HTML.&lt;/li&gt;
&lt;li&gt;List the pages that need to rank and how many of them are database-driven.&lt;/li&gt;
&lt;li&gt;Decide between pre-rendering and a move to Next.js for those pages.&lt;/li&gt;
&lt;li&gt;Keep the logged-in app separate if it works; migrate the public pages first.&lt;/li&gt;
&lt;li&gt;Set up Search Console, submit the sitemap and watch indexing over the next few weeks.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you're weighing a switch away from Lovable more broadly, my comparison of &lt;a href="https://muhammadmoiz.dev/blog/lovable-alternatives" rel="noopener noreferrer"&gt;Lovable alternatives&lt;/a&gt; covers when custom code makes sense. And if you want the public side of your app rebuilt so Google can actually read it, that's exactly what my &lt;a href="https://muhammadmoiz.dev/services/nextjs-development" rel="noopener noreferrer"&gt;Next.js development service&lt;/a&gt; covers, usually as part of getting an &lt;a href="https://muhammadmoiz.dev/services/ai-app-production-ready" rel="noopener noreferrer"&gt;AI-built app ready for production&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://nextjs.org/learn/seo/rendering-strategies" rel="noopener noreferrer"&gt;Next.js Learn: SEO, Rendering Strategies&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://nextjs.org/learn/seo/webcrawlers" rel="noopener noreferrer"&gt;Next.js Learn: SEO, Webcrawlers&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://nextjs.org/learn/seo/metadata" rel="noopener noreferrer"&gt;Next.js Learn: SEO, Metadata&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://nextjs.org/docs/app/getting-started/metadata-and-og-images" rel="noopener noreferrer"&gt;Next.js Docs: Metadata and OG images&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://react.dev/learn/build-a-react-app-from-scratch" rel="noopener noreferrer"&gt;React Docs: Build a React app from scratch&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.npmjs.com/package/lovable-tagger" rel="noopener noreferrer"&gt;lovable-tagger on npm&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Cover photo: Agence Olloweb on Unsplash&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;I'm Muhammad Moiz, a full-stack developer who builds web apps, SaaS and POS systems, and takes AI-built apps (Lovable, Bolt, Replit) to production. &lt;a href="https://muhammadmoiz.dev/contact" rel="noopener noreferrer"&gt;Get in touch&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>seo</category>
      <category>nextjs</category>
      <category>react</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Lovable Alternatives: 7 Options Compared (and When to Switch to Custom Code)</title>
      <dc:creator>Muhammad Moiz</dc:creator>
      <pubDate>Wed, 04 Nov 2026 05:09:51 +0000</pubDate>
      <link>https://dev.to/muhammadmoiz269/lovable-alternatives-7-options-compared-and-when-to-switch-to-custom-code-5b4p</link>
      <guid>https://dev.to/muhammadmoiz269/lovable-alternatives-7-options-compared-and-when-to-switch-to-custom-code-5b4p</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://muhammadmoiz.dev/blog/lovable-alternatives" rel="noopener noreferrer"&gt;muhammadmoiz.dev&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;The best Lovable alternatives in late 2026 are Bolt, Replit, v0, Base44, Cursor and Claude Code, plus the option most comparison lists skip: moving to custom code with a developer. Which one fits depends less on the AI model underneath and more on three questions: can you get your code out, who owns the backend, and how far from production you are.&lt;/p&gt;

&lt;p&gt;I take over and fix apps built with these tools, so this comparison focuses on what matters after the demo works. Pricing below was checked on each vendor's own pricing page in November 2026, except where I say otherwise.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why do people look for Lovable alternatives?
&lt;/h2&gt;

&lt;p&gt;Lovable is good at getting a polished React frontend on screen fast. The reasons founders start shopping around are usually the same few:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Credit burn.&lt;/strong&gt; Lovable runs on credits. Its pricing page describes a free daily grant of 5 build credits (capped at 30 a month) plus 20 Cloud credits a month, with paid plans adding more. Long debugging loops eat credits quickly, and that is often when people start comparing.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Backend lock-in worries.&lt;/strong&gt; Lovable's frontend code syncs to GitHub, but the database, secrets and backend services live in Lovable Cloud or Supabase. Third-party export guides point out that your data and your environment secrets do not come with a code export, so leaving takes more than one click.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Hitting a complexity ceiling.&lt;/strong&gt; Payments, roles and permissions, background jobs and integrations with other systems are where prompt-based editing starts to go in circles.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Search visibility.&lt;/strong&gt; A client-rendered single-page app is harder for search engines to read than server-rendered pages.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If one of these is your reason, it should drive your choice. Switching tools to fix a problem the new tool also has is a common and expensive mistake.&lt;/p&gt;

&lt;h2&gt;
  
  
  The 7 Lovable alternatives at a glance
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Option&lt;/th&gt;
&lt;th&gt;Best for&lt;/th&gt;
&lt;th&gt;Backend&lt;/th&gt;
&lt;th&gt;Getting your code out&lt;/th&gt;
&lt;th&gt;Entry paid price (Nov 2026)&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Bolt&lt;/td&gt;
&lt;td&gt;Fast browser-based prototypes and simple sites&lt;/td&gt;
&lt;td&gt;Bolt Cloud (hosting, databases, auth)&lt;/td&gt;
&lt;td&gt;Open-source core; check export per plan&lt;/td&gt;
&lt;td&gt;Pro $25/month&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Replit&lt;/td&gt;
&lt;td&gt;Full-stack apps with hosting in one place&lt;/td&gt;
&lt;td&gt;Built-in auth, database, hosting, monitoring&lt;/td&gt;
&lt;td&gt;Code lives in a real workspace&lt;/td&gt;
&lt;td&gt;Core $20/month ($18 yearly)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;v0&lt;/td&gt;
&lt;td&gt;Frontend and UI on the Vercel stack&lt;/td&gt;
&lt;td&gt;Bring your own&lt;/td&gt;
&lt;td&gt;Code-first, frontend focused&lt;/td&gt;
&lt;td&gt;Check v0.app/pricing&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Base44&lt;/td&gt;
&lt;td&gt;Internal tools and simple business apps&lt;/td&gt;
&lt;td&gt;Base44's managed backend&lt;/td&gt;
&lt;td&gt;Reported to need a higher plan&lt;/td&gt;
&lt;td&gt;Check base44.com/pricing&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Cursor&lt;/td&gt;
&lt;td&gt;Developers editing a real codebase&lt;/td&gt;
&lt;td&gt;Whatever you choose&lt;/td&gt;
&lt;td&gt;You already own it&lt;/td&gt;
&lt;td&gt;Plans from $8 to $200/month&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Claude Code&lt;/td&gt;
&lt;td&gt;Agentic coding on your own repo&lt;/td&gt;
&lt;td&gt;Whatever you choose&lt;/td&gt;
&lt;td&gt;You already own it&lt;/td&gt;
&lt;td&gt;Needs a Claude plan or API account&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Custom code with a developer&lt;/td&gt;
&lt;td&gt;Apps with paying users, payments, compliance&lt;/td&gt;
&lt;td&gt;Designed for your app&lt;/td&gt;
&lt;td&gt;You own everything from day one&lt;/td&gt;
&lt;td&gt;Project based&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The first four are app builders: you describe what you want and they produce and host an app. The next two are AI coding tools: they work on a codebase you or a developer control. The last is a different decision altogether.&lt;/p&gt;

&lt;h2&gt;
  
  
  App builders: Bolt, Replit, v0 and Base44
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Bolt
&lt;/h3&gt;

&lt;p&gt;Bolt is the closest match to Lovable in how it feels. You chat, it builds, and it runs the app in the browser. Its backend story is Bolt Cloud, which the homepage describes as covering hosting, databases and user authentication.&lt;/p&gt;

&lt;p&gt;On pricing, Bolt's free tier gives 1M tokens a month with a 300K daily cap and Bolt branding on sites. Pro is $25 a month for 10M tokens with rollover, a custom domain and no branding. Teams is $30 per member per month. Bolt bills by tokens rather than credits, which some people find easier to predict, but large projects still use a lot of them because the model has to read more code each time. The original bolt.new codebase is public on GitHub under the MIT license, which is a good sign for transparency, even though the hosted product has moved well past it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pick Bolt if&lt;/strong&gt; you want the Lovable experience with a different pricing model, and your app is still at the prototype stage.&lt;/p&gt;

&lt;h3&gt;
  
  
  Replit
&lt;/h3&gt;

&lt;p&gt;Replit is a full development environment with an AI agent on top. Its homepage lists authentication, a database, hosting and monitoring as built-in services, which makes it the strongest "everything in one place" option on this list.&lt;/p&gt;

&lt;p&gt;The Core plan is $20 a month ($18 billed yearly) and Pro is $100 a month ($90 yearly), with higher usage tiers above that. Because Replit gives you an actual workspace with files and a terminal, it is easier for a developer to step in later than with tools that hide the code. I compared it with Lovable in more detail in &lt;a href="https://muhammadmoiz.dev/blog/lovable-vs-replit" rel="noopener noreferrer"&gt;Lovable vs Replit vs Bolt vs Cursor&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pick Replit if&lt;/strong&gt; you want the agent to handle backend logic too, and you like the idea of hosting staying in one place.&lt;/p&gt;

&lt;h3&gt;
  
  
  v0
&lt;/h3&gt;

&lt;p&gt;v0 is Vercel's AI builder. It is strongest on interface work: pages, components and layouts that look production-grade. It fits teams already planning to host on Vercel. For anything beyond the UI, you connect your own database and auth.&lt;/p&gt;

&lt;p&gt;I could not reach v0's pricing page from my research environment this month, and third-party guides disagree about which plans still exist after changes earlier in 2026, so check v0.app/pricing directly rather than trusting a number from a blog (including this one).&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pick v0 if&lt;/strong&gt; your main pain with Lovable is design quality, and you have, or will hire, someone to build the backend.&lt;/p&gt;

&lt;h3&gt;
  
  
  Base44
&lt;/h3&gt;

&lt;p&gt;Base44 targets non-technical builders making internal tools, dashboards and simple customer-facing apps, with a managed backend included. It is easy to start with, but the trade-off is portability. Third-party pricing guides report that code export and GitHub sync are limited to its higher paid tiers, and that the backend stays tied to Base44's own SDK. I could not confirm this on Base44's official site this month, so verify it before you build anything you might want to move.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pick Base44 if&lt;/strong&gt; the app is internal, low-risk, and you are fine with it living on the platform long term.&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%2Fimages.unsplash.com%2Fphoto-1534665482403-a909d0d97c67%3Fw%3D1200%26q%3D80" 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%2Fimages.unsplash.com%2Fphoto-1534665482403-a909d0d97c67%3Fw%3D1200%26q%3D80" alt="A developer working on code on a laptop at a desk" width="1200" height="800"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Photo: Danial Igdery on Unsplash&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  AI coding tools: Cursor and Claude Code
&lt;/h2&gt;

&lt;p&gt;These two are not app builders. They are what you move to when you want AI help but also want a normal codebase in a normal Git repository.&lt;/p&gt;

&lt;h3&gt;
  
  
  Cursor
&lt;/h3&gt;

&lt;p&gt;Cursor is an AI-first code editor. You open your project, and the AI can read the whole codebase, suggest changes across files and run agent tasks. Cursor's pricing page in November 2026 lists a free tier and paid plans at $8, $30, $100 and $200 a month, with third-party model usage billed separately. Its plan lineup has changed several times this year, so treat any older comparison with caution.&lt;/p&gt;

&lt;h3&gt;
  
  
  Claude Code
&lt;/h3&gt;

&lt;p&gt;Claude Code is Anthropic's agentic coding tool. According to its documentation it runs in the terminal, in VS Code and JetBrains, as a desktop app and in the browser. It reads a codebase, edits files, runs commands, and works directly with Git to create branches, commits and pull requests. It needs a Claude subscription or an Anthropic Console account.&lt;/p&gt;

&lt;h3&gt;
  
  
  Who should use these?
&lt;/h3&gt;

&lt;p&gt;Both tools make an experienced developer much faster. Neither turns a non-developer into one. If you export a Lovable app into Cursor or Claude Code without knowing how to review a database migration or an access policy, you have swapped one set of blind spots for another. A sensible pattern is: the founder keeps using a builder for experiments, and a developer uses an AI coding tool on the production repo.&lt;/p&gt;

&lt;h2&gt;
  
  
  When should you switch to custom code?
&lt;/h2&gt;

&lt;p&gt;This is the decision that matters most, and it is rarely about which AI tool is "better". Switching makes sense when your app has crossed from prototype into product. Signs you are there:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Real users and real data.&lt;/strong&gt; Once strangers sign up and store personal or business data, security stops being optional. Missing row level security is one of the most common holes in AI-built apps; see &lt;a href="https://muhammadmoiz.dev/blog/supabase-rls" rel="noopener noreferrer"&gt;Supabase RLS explained&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Money moves through the app.&lt;/strong&gt; Subscriptions, refunds, webhooks and tax are easy to demo and hard to get right.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Fixes keep breaking other things.&lt;/strong&gt; If each prompt fixes one bug and creates two, the codebase has outgrown prompt-based editing.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;You need to rank on Google.&lt;/strong&gt; A Lovable or Bolt frontend is typically a client-rendered SPA. Moving key pages to server rendering is a structural change, not a prompt.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Investors, clients or compliance ask questions.&lt;/strong&gt; Due diligence wants to know who understands the code.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Custom code does not mean starting over. In many AI-built apps, the UI and the data model are worth keeping. The work is usually hardening: locking down database access, moving secrets server-side, adding proper error handling and logging, setting up a real deployment pipeline, and fixing the parts that only worked in the happy path.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Before you switch tools:&lt;/strong&gt; Connect your current project to GitHub and export your database first. Whatever you decide next, owning a copy of your code and data keeps every option open.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  A quick checklist for choosing your next step
&lt;/h2&gt;

&lt;p&gt;Use this before you pay for another tool:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Can I get the full source code out today, on my current plan?&lt;/li&gt;
&lt;li&gt;Where does my data live, and can I export it in a standard format?&lt;/li&gt;
&lt;li&gt;Who holds my API keys and secrets, and can I rotate them?&lt;/li&gt;
&lt;li&gt;Is authentication and database access enforced on the server, not just hidden in the UI?&lt;/li&gt;
&lt;li&gt;Do I have more than a handful of real users or any payments flowing?&lt;/li&gt;
&lt;li&gt;Do I need these pages to show up on Google?&lt;/li&gt;
&lt;li&gt;Is someone on the team able to read and review the generated code?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you answer "no" or "not sure" to the first four, fix that before switching anything. If you answer "yes" to the middle two and "no" to the last one, a builder alone is no longer enough.&lt;/p&gt;

&lt;h2&gt;
  
  
  What this means for founders
&lt;/h2&gt;

&lt;p&gt;For a prototype or an idea you are testing, any of the builders above is great value compared with paying for custom development, and the right one is mostly a matter of taste and pricing model. For an app with users and revenue, the tool matters far less than having someone accountable for the code.&lt;/p&gt;

&lt;p&gt;If you are at that point, my &lt;a href="https://muhammadmoiz.dev/services/ai-app-production-ready" rel="noopener noreferrer"&gt;AI app to production service&lt;/a&gt; takes apps built with Lovable, Bolt or Replit and makes them secure, maintainable and ready to scale, without throwing away the work you have already done. If you are not sure how bad things are yet, a &lt;a href="https://muhammadmoiz.dev/services/production-audit" rel="noopener noreferrer"&gt;production audit&lt;/a&gt; is a lower-commitment first step.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://lovable.dev/pricing" rel="noopener noreferrer"&gt;Lovable pricing&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://bolt.new/pricing" rel="noopener noreferrer"&gt;Bolt pricing&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://bolt.new/" rel="noopener noreferrer"&gt;Bolt homepage&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/stackblitz/bolt.new" rel="noopener noreferrer"&gt;bolt.new on GitHub (stackblitz)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://replit.com/pricing" rel="noopener noreferrer"&gt;Replit pricing&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://replit.com/" rel="noopener noreferrer"&gt;Replit homepage&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://cursor.com/pricing" rel="noopener noreferrer"&gt;Cursor pricing&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://code.claude.com/docs/en/overview" rel="noopener noreferrer"&gt;Claude Code overview (Anthropic docs)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://v2.softr.io/blog/base44-pricing" rel="noopener noreferrer"&gt;Base44 pricing guide (Softr)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.zite.com/blog/base44-pricing" rel="noopener noreferrer"&gt;Base44 pricing guide (Zite)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://usagepricing.com/blueprint/v0" rel="noopener noreferrer"&gt;v0 pricing blueprint (usagepricing.com)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://vp0.com/blogs/can-i-export-code-from-lovable" rel="noopener noreferrer"&gt;Can I export code from Lovable? (vp0)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Cover photo: Christopher Gower on Unsplash&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;I'm Muhammad Moiz, a full-stack developer who builds web apps, SaaS and POS systems, and takes AI-built apps (Lovable, Bolt, Replit) to production. &lt;a href="https://muhammadmoiz.dev/contact" rel="noopener noreferrer"&gt;Get in touch&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>webdev</category>
      <category>startup</category>
      <category>lovable</category>
    </item>
    <item>
      <title>Web App Development Cost in 2026: Real Numbers for MVPs</title>
      <dc:creator>Muhammad Moiz</dc:creator>
      <pubDate>Tue, 03 Nov 2026 05:09:02 +0000</pubDate>
      <link>https://dev.to/muhammadmoiz269/web-app-development-cost-in-2026-real-numbers-for-mvps-ijp</link>
      <guid>https://dev.to/muhammadmoiz269/web-app-development-cost-in-2026-real-numbers-for-mvps-ijp</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://muhammadmoiz.dev/blog/web-app-development-cost" rel="noopener noreferrer"&gt;muhammadmoiz.dev&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Web app development cost depends on three things: how much you build, who builds it, and what it costs to run once it is live. There is no honest single number, but you can get a reliable estimate by pricing the hours your scope needs at your builder's rate, then adding a small monthly bill for hosting, database and store fees. This guide shows you how to do that, with real platform prices checked in November 2026.&lt;/p&gt;

&lt;h2&gt;
  
  
  What actually drives web app development cost?
&lt;/h2&gt;

&lt;p&gt;Most quotes look different because they are pricing different things. When you compare two numbers, check that they cover the same work. These are the factors that move a quote the most:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Number of screens and user flows.&lt;/strong&gt; A sign-up, a dashboard and a settings page is a very different job from twenty screens with multi-step forms.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;User roles and permissions.&lt;/strong&gt; Every extra role (admin, staff, customer, manager) adds rules, tests and edge cases. Getting permissions wrong is also one of the most common security problems, as covered in &lt;a href="https://muhammadmoiz.dev/blog/supabase-rls" rel="noopener noreferrer"&gt;Supabase RLS explained&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Integrations.&lt;/strong&gt; Payments, email, maps, calendars, accounting tools and third-party APIs each add setup, error handling and testing time.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Business rules.&lt;/strong&gt; Pricing logic, approvals, scheduling and inventory are where "simple" apps quietly become complex.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Security and compliance.&lt;/strong&gt; Handling payments, personal data or regulated information means more review and more testing.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The state of existing code.&lt;/strong&gt; Extending a clean codebase is faster than untangling one, which matters a lot if you are starting from an AI-built prototype.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Timeline.&lt;/strong&gt; A tight deadline does not usually lower the total, but it can mean more hours per week.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Design, testing, deployment and project management are part of the cost too. A quote that only counts "coding" is not the full picture.&lt;/p&gt;

&lt;h2&gt;
  
  
  How much does it cost to build an MVP?
&lt;/h2&gt;

&lt;p&gt;The easiest way to estimate an MVP is a simple formula:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Estimated cost = hours for your scope x hourly rate + monthly running costs&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The hourly rate varies hugely by country and by type of team. Agencies in high-cost markets charge much more per hour than an independent senior developer working remotely, and you are often paying for account managers and overhead on top of the engineering.&lt;/p&gt;

&lt;p&gt;To make the formula concrete, here is an illustration using the published rate on my &lt;a href="https://muhammadmoiz.dev/pricing" rel="noopener noreferrer"&gt;pricing page&lt;/a&gt;: $20 per hour for ad-hoc work. The hour counts below are rough examples to show how scope changes the total, not a quote.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Scope (example)&lt;/th&gt;
&lt;th&gt;What it includes&lt;/th&gt;
&lt;th&gt;Example hours&lt;/th&gt;
&lt;th&gt;At $20/hour&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Landing page plus waitlist&lt;/td&gt;
&lt;td&gt;One or two pages, a form, analytics&lt;/td&gt;
&lt;td&gt;20 to 40&lt;/td&gt;
&lt;td&gt;$400 to $800&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Small MVP&lt;/td&gt;
&lt;td&gt;Auth, one core workflow, a dashboard, basic admin&lt;/td&gt;
&lt;td&gt;150 to 300&lt;/td&gt;
&lt;td&gt;$3,000 to $6,000&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;SaaS MVP with billing&lt;/td&gt;
&lt;td&gt;The above plus subscriptions, teams, emails, settings&lt;/td&gt;
&lt;td&gt;300 to 500&lt;/td&gt;
&lt;td&gt;$6,000 to $10,000&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Larger product&lt;/td&gt;
&lt;td&gt;Several roles, integrations, reporting, mobile-ready UI&lt;/td&gt;
&lt;td&gt;600+&lt;/td&gt;
&lt;td&gt;$12,000+&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Two things to notice. First, hours matter far more than the rate. Cutting one complex feature from version one often saves more than negotiating the rate down. Second, the same table at a higher agency rate multiplies every row, so always ask how many hours a quote assumes.&lt;/p&gt;

&lt;p&gt;For ongoing work after launch, a retainer is often simpler. My retainer is $1,000 a month for about 60 hours (15 hours per week), which covers new features, fixes and priority support.&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%2Fimages.unsplash.com%2Fphoto-1498050108023-c5249f4df085%3Fw%3D1200%26q%3D80" 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%2Fimages.unsplash.com%2Fphoto-1498050108023-c5249f4df085%3Fw%3D1200%26q%3D80" alt="A laptop showing lines of code on a desk with notebooks and a phone" width="1200" height="799"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Photo: Christopher Gower on Unsplash&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What does it cost to run a web app each month?
&lt;/h2&gt;

&lt;p&gt;Running costs are the part founders forget. The good news is that for most early-stage products they are small. Here are the published prices from the main platforms, as of November 2026:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Service&lt;/th&gt;
&lt;th&gt;Free option&lt;/th&gt;
&lt;th&gt;First paid plan&lt;/th&gt;
&lt;th&gt;Notes&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Vercel (hosting for Next.js and React)&lt;/td&gt;
&lt;td&gt;Hobby, $0&lt;/td&gt;
&lt;td&gt;Pro, $20/month&lt;/td&gt;
&lt;td&gt;Pro includes a $20 usage credit, then pay as you go. Extra developer seats are $20/month each.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Supabase (database, auth, storage)&lt;/td&gt;
&lt;td&gt;Free, $0&lt;/td&gt;
&lt;td&gt;Pro, from $25/month&lt;/td&gt;
&lt;td&gt;Free projects pause after a week of inactivity and are limited to 500 MB of database. Pro gives 8 GB disk and 100,000 monthly active users.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Supabase Team&lt;/td&gt;
&lt;td&gt;n/a&lt;/td&gt;
&lt;td&gt;From $599/month&lt;/td&gt;
&lt;td&gt;Longer backup and log retention, mainly for larger teams.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Apple Developer Program&lt;/td&gt;
&lt;td&gt;n/a&lt;/td&gt;
&lt;td&gt;$99/year&lt;/td&gt;
&lt;td&gt;Only needed if you ship an iOS app to the App Store.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;So a typical early web app on Vercel Pro and Supabase Pro starts at around $45 a month before usage grows. Add a domain, an email sending service and any paid APIs you rely on. If you are deciding between backends, my &lt;a href="https://muhammadmoiz.dev/blog/supabase-vs-firebase" rel="noopener noreferrer"&gt;Supabase vs Firebase comparison&lt;/a&gt; covers how their pricing models differ.&lt;/p&gt;

&lt;p&gt;A few cost traps to watch for:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Free tiers that pause.&lt;/strong&gt; A free database that sleeps after a week is fine for testing but not for a live product with paying users.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Usage-based billing.&lt;/strong&gt; Serverless functions, bandwidth and database reads are cheap per unit and expensive at scale. Set spending alerts on day one.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Per-seat pricing.&lt;/strong&gt; Some tools charge for each team member, which adds up as you hire.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Payment fees.&lt;/strong&gt; Payment providers take a percentage of each transaction, so factor that into your margins rather than your build budget.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  How much does it cost to make an app with AI builders?
&lt;/h2&gt;

&lt;p&gt;Tools like Lovable, Bolt and Replit have changed the early stage. A founder can now build a working prototype for the price of a monthly subscription, which is a great way to test an idea before spending on development. I compared the main options in &lt;a href="https://muhammadmoiz.dev/blog/lovable-vs-replit" rel="noopener noreferrer"&gt;Lovable vs Replit vs Bolt vs Cursor&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;The catch is what happens next. AI-built apps often reach a point where they need a developer: security rules that were never set up, payments that only half work, or code that becomes hard to change. That does not make the prototype a waste. It means your real budget is "prototype cost plus the work to make it production-ready", and that second number depends heavily on how clean the generated code is. I wrote about the most common problems in &lt;a href="https://muhammadmoiz.dev/blog/vibe-coding-security" rel="noopener noreferrer"&gt;vibe coding security&lt;/a&gt;.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Get the code reviewed before you get a quote:&lt;/strong&gt; If you already have a prototype, a fixed-price review tells you exactly what needs fixing, so any quote you get afterwards is based on facts rather than guesses. My &lt;a href="https://muhammadmoiz.dev/services/production-audit" rel="noopener noreferrer"&gt;production audit&lt;/a&gt; is $300 and comes with a prioritised fix list.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  How to get an accurate quote (and keep it accurate)
&lt;/h2&gt;

&lt;p&gt;Vague requests get vague quotes. Use this checklist before you talk to any developer or agency:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Write down the one job your app must do.&lt;/strong&gt; If you cannot describe the core workflow in two sentences, the scope is not ready yet.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;List every user role&lt;/strong&gt; and what each one can see and do.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;List integrations&lt;/strong&gt; by name: which payment provider, which email service, which maps or calendar API.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Mark each feature as "launch" or "later".&lt;/strong&gt; Be ruthless. Most MVPs launch with far less than the first wish list.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Share what exists already:&lt;/strong&gt; designs, a prototype, an AI-built app, or a competitor you like.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Ask for a fixed quote with milestones,&lt;/strong&gt; so you pay as work is delivered rather than all up front.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Agree how scope changes are handled.&lt;/strong&gt; Every change should be priced and agreed in writing before work starts.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Confirm who owns the code.&lt;/strong&gt; You should, in your own repository, once the work is paid for.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;On my projects, every quote is fixed after a free call and a look at the code, paid per milestone, and any change is agreed in writing before I start on it. Whoever you hire, ask for the same.&lt;/p&gt;

&lt;h2&gt;
  
  
  What this means for founders and business owners
&lt;/h2&gt;

&lt;p&gt;If you are budgeting for a new product, plan in two parts. The first is the build: scope multiplied by rate, with the scope cut down to what you need to learn whether customers will pay. The second is running costs, which for a young web app usually sit in the tens of dollars a month rather than hundreds, as long as you watch usage-based billing.&lt;/p&gt;

&lt;p&gt;The biggest savings come from decisions, not discounts. Launching with one strong workflow instead of five half-finished ones will cut your web app development cost more than any rate negotiation. And if you already have a prototype from an AI builder, find out what state it is in before you decide whether to fix it or rebuild.&lt;/p&gt;

&lt;p&gt;If you want a number for your own project, the &lt;a href="https://muhammadmoiz.dev/pricing" rel="noopener noreferrer"&gt;pricing page&lt;/a&gt; explains how I quote, or you can book a free call.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://muhammadmoiz.dev/pricing" rel="noopener noreferrer"&gt;Muhammad Moiz pricing page&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://vercel.com/pricing" rel="noopener noreferrer"&gt;Vercel pricing&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://supabase.com/pricing" rel="noopener noreferrer"&gt;Supabase pricing&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://developer.apple.com/support/enrollment/" rel="noopener noreferrer"&gt;Apple Developer Program enrollment&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Cover photo: Jakub Żerdzicki on Unsplash&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;I'm Muhammad Moiz, a full-stack developer who builds web apps, SaaS and POS systems, and takes AI-built apps (Lovable, Bolt, Replit) to production. &lt;a href="https://muhammadmoiz.dev/contact" rel="noopener noreferrer"&gt;Get in touch&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>startup</category>
      <category>saas</category>
      <category>mvp</category>
    </item>
    <item>
      <title>Supabase vs Firebase for Startups: An Honest Comparison</title>
      <dc:creator>Muhammad Moiz</dc:creator>
      <pubDate>Fri, 30 Oct 2026 06:23:45 +0000</pubDate>
      <link>https://dev.to/muhammadmoiz269/supabase-vs-firebase-for-startups-an-honest-comparison-93h</link>
      <guid>https://dev.to/muhammadmoiz269/supabase-vs-firebase-for-startups-an-honest-comparison-93h</guid>
      <description>&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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fapa4hbeovgs1x30b0vo0.jpg" 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.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fapa4hbeovgs1x30b0vo0.jpg" alt=" " width="800" height="533"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Supabase vs Firebase comes down to one question: do you want a relational Postgres database with SQL, or a document database that syncs to clients with almost no setup? For most SaaS products with users, teams, billing and reports, Supabase is the safer long-term default. Firebase still wins for real-time, mobile-first apps where you want Google to run everything and your data is shaped like documents.&lt;/p&gt;

&lt;p&gt;I've shipped production work on Firebase (&lt;a href="https://muhammadmoiz.dev/work/timegram" rel="noopener noreferrer"&gt;Timegram&lt;/a&gt;, a time-tracking SaaS I built, runs on it) and I regularly work on Supabase apps, many of them generated by AI builders like Lovable. Below is how the two compare on the things that actually hurt later: data model, security, pricing, lock-in and hiring.&lt;/p&gt;

&lt;h2&gt;
  
  
  What is the difference between Supabase and Firebase?
&lt;/h2&gt;

&lt;p&gt;Both are "backend as a service" platforms. You get a database, authentication, file storage, server functions and real-time updates without running your own servers. The difference is what sits in the middle.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Supabase&lt;/strong&gt; is built on Postgres. Its docs describe each project as a full Postgres database rather than an abstraction over one, and Auth, Storage, Realtime and Edge Functions all hang off that database. You write SQL, use foreign keys and joins, and can add Postgres extensions such as pgvector for AI embeddings, PostGIS for maps and pg_cron for scheduled jobs.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Firebase&lt;/strong&gt; is built around Cloud Firestore, a NoSQL document database from Google. Data lives in collections of documents, clients read and write directly through the SDK, and access is controlled by Firebase Security Rules. It plugs into the rest of Google Cloud (Cloud Functions, Cloud Storage, Analytics, Crashlytics, Cloud Messaging).&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Neither is "better" in general. They suit different shapes of data and different teams.&lt;/p&gt;

&lt;h2&gt;
  
  
  Supabase vs Firebase at a glance
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;Supabase&lt;/th&gt;
&lt;th&gt;Firebase&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Database&lt;/td&gt;
&lt;td&gt;Postgres (relational, SQL)&lt;/td&gt;
&lt;td&gt;Firestore (NoSQL documents)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Queries&lt;/td&gt;
&lt;td&gt;Joins, aggregates, views, full SQL&lt;/td&gt;
&lt;td&gt;Simple queries per collection; joins done in app code&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Access control&lt;/td&gt;
&lt;td&gt;Postgres Row Level Security policies&lt;/td&gt;
&lt;td&gt;Firebase Security Rules&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Pricing model&lt;/td&gt;
&lt;td&gt;Plan fee plus usage (storage, egress, MAU)&lt;/td&gt;
&lt;td&gt;Pay per document read, write and delete&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Free tier&lt;/td&gt;
&lt;td&gt;2 active projects, paused after a week of inactivity&lt;/td&gt;
&lt;td&gt;Daily free quota on reads, writes and storage&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Self-hosting&lt;/td&gt;
&lt;td&gt;Possible (open source)&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Best fit&lt;/td&gt;
&lt;td&gt;SaaS, dashboards, B2B, reporting, AI features&lt;/td&gt;
&lt;td&gt;Mobile apps, chat, live collaboration, quick prototypes&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  Supabase vs Firebase pricing: what will you actually pay?
&lt;/h2&gt;

&lt;p&gt;I checked both pricing pages in October 2026. Prices change, so confirm before you budget.&lt;/p&gt;

&lt;h3&gt;
  
  
  Supabase pricing
&lt;/h3&gt;

&lt;p&gt;Supabase uses plans with included usage:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Free:&lt;/strong&gt; $0. 500 MB database, 50,000 monthly active users, 5 GB egress, 1 GB file storage, 500,000 Edge Function invocations. You get two active projects, and free projects are paused after one week of inactivity.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Pro:&lt;/strong&gt; from $25 a month. 8 GB database per project, 100,000 MAU, 250 GB egress, 100 GB file storage, 2 million Edge Function invocations, plus $10 of compute credits. Projects are never paused.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Overages on Pro:&lt;/strong&gt; $0.125 per GB of database, $0.00325 per extra MAU, $0.09 per GB of egress, $0.0213 per GB of file storage.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Team:&lt;/strong&gt; from $599 a month. &lt;strong&gt;Enterprise:&lt;/strong&gt; custom.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A useful detail: the Pro plan has a spend cap switched on by default, so you won't get a surprise bill unless you turn the cap off.&lt;/p&gt;

&lt;h3&gt;
  
  
  Firebase (Firestore) pricing
&lt;/h3&gt;

&lt;p&gt;Firestore charges per operation, not per plan. Google's Firestore pricing page lists a daily free quota of 1 GiB of stored data, 50,000 document reads, 20,000 writes and 20,000 deletes, plus 10 GiB of outbound transfer a month. Above that, in the Iowa (us-central1) location, you pay $0.03 per 100,000 reads, $0.09 per 100,000 writes and $0.01 per 100,000 deletes. Other regions are priced differently.&lt;/p&gt;

&lt;p&gt;For sign-in, Google Cloud's Identity Platform pricing page lists email, phone, anonymous and social sign-ins as free up to 50,000 MAU, then $0.0055 per MAU up to 100,000. SAML and OpenID Connect (enterprise single sign-on) are free for only 50 MAU, then $0.015 per MAU. SMS for phone login is billed separately.&lt;/p&gt;

&lt;h3&gt;
  
  
  Which one is more affordable?
&lt;/h3&gt;

&lt;p&gt;It depends on how your app reads data, not just how many users you have.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Firestore bills every document a query returns. A dashboard that loads 200 documents for every page view costs 200 reads each time. Listeners that re-run on every change add up fast. Badly structured Firestore apps are where surprise bills come from.&lt;/li&gt;
&lt;li&gt;Supabase bills mostly for storage, egress and compute. A heavy SQL query costs CPU time, not per row returned, so read-heavy dashboards and reports are usually more predictable on a fixed plan.&lt;/li&gt;
&lt;li&gt;For a small app with light traffic, both can stay free or close to it for a long time. Just remember the Supabase free plan pauses idle projects, which is fine for prototypes but not for a live product.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Is Supabase or Firebase better for a SaaS startup?
&lt;/h2&gt;

&lt;p&gt;Ask what your data looks like six months from now.&lt;/p&gt;

&lt;p&gt;A typical SaaS has organisations, users, roles, projects, invoices, subscriptions and audit logs, all linked to each other. That is relational data. In Postgres you model it with tables and foreign keys, and a report like "hours logged per client per month, grouped by team" is one SQL query. In Firestore you either duplicate data across documents so each screen can read it in one go, or you fetch several collections and join them in your code. Both work, but duplication means keeping copies in sync, and that is where bugs creep in.&lt;/p&gt;

&lt;p&gt;Here is the same question asked both ways. In Supabase:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight sql"&gt;&lt;code&gt;&lt;span class="k"&gt;select&lt;/span&gt; &lt;span class="k"&gt;c&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;name&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="k"&gt;sum&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;t&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;minutes&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;/&lt;/span&gt; &lt;span class="mi"&gt;60&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt; &lt;span class="k"&gt;as&lt;/span&gt; &lt;span class="n"&gt;hours&lt;/span&gt;
&lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="n"&gt;time_entries&lt;/span&gt; &lt;span class="n"&gt;t&lt;/span&gt;
&lt;span class="k"&gt;join&lt;/span&gt; &lt;span class="n"&gt;projects&lt;/span&gt; &lt;span class="n"&gt;p&lt;/span&gt; &lt;span class="k"&gt;on&lt;/span&gt; &lt;span class="n"&gt;p&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;id&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;t&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;project_id&lt;/span&gt;
&lt;span class="k"&gt;join&lt;/span&gt; &lt;span class="n"&gt;clients&lt;/span&gt; &lt;span class="k"&gt;c&lt;/span&gt; &lt;span class="k"&gt;on&lt;/span&gt; &lt;span class="k"&gt;c&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;id&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;p&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;client_id&lt;/span&gt;
&lt;span class="k"&gt;where&lt;/span&gt; &lt;span class="n"&gt;t&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;org_id&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s1"&gt;'org_123'&lt;/span&gt;
  &lt;span class="k"&gt;and&lt;/span&gt; &lt;span class="n"&gt;t&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;started_at&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;=&lt;/span&gt; &lt;span class="n"&gt;date_trunc&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s1"&gt;'month'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;now&lt;/span&gt;&lt;span class="p"&gt;())&lt;/span&gt;
&lt;span class="k"&gt;group&lt;/span&gt; &lt;span class="k"&gt;by&lt;/span&gt; &lt;span class="k"&gt;c&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;name&lt;/span&gt;
&lt;span class="k"&gt;order&lt;/span&gt; &lt;span class="k"&gt;by&lt;/span&gt; &lt;span class="n"&gt;hours&lt;/span&gt; &lt;span class="k"&gt;desc&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;In Firestore you would usually keep a running total on each client document and update it every time an entry is written, often from a Cloud Function:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="c1"&gt;// Illustrative: keep a per-client monthly total in sync on every new entry&lt;/span&gt;
&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;onEntryCreated&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;onDocumentCreated&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
  &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;orgs/{orgId}/entries/{entryId}&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="k"&gt;async &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;event&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;entry&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;event&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;data&lt;/span&gt;&lt;span class="p"&gt;?.&lt;/span&gt;&lt;span class="nf"&gt;data&lt;/span&gt;&lt;span class="p"&gt;();&lt;/span&gt;
    &lt;span class="k"&gt;if &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="nx"&gt;entry&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;return&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;month&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;entry&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;startedAt&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;toDate&lt;/span&gt;&lt;span class="p"&gt;().&lt;/span&gt;&lt;span class="nf"&gt;toISOString&lt;/span&gt;&lt;span class="p"&gt;().&lt;/span&gt;&lt;span class="nf"&gt;slice&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;7&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
    &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;ref&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;db&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;doc&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;`orgs/&lt;/span&gt;&lt;span class="p"&gt;${&lt;/span&gt;&lt;span class="nx"&gt;event&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;params&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;orgId&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="s2"&gt;/clientTotals/&lt;/span&gt;&lt;span class="p"&gt;${&lt;/span&gt;&lt;span class="nx"&gt;entry&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;clientId&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="s2"&gt;_&lt;/span&gt;&lt;span class="p"&gt;${&lt;/span&gt;&lt;span class="nx"&gt;month&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="s2"&gt;`&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
    &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nx"&gt;ref&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;set&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt; &lt;span class="na"&gt;minutes&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;FieldValue&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;increment&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;entry&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;minutes&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;},&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;merge&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kc"&gt;true&lt;/span&gt; &lt;span class="p"&gt;});&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;);&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The Firestore version is fast and cheap to read, but you now have to handle edits, deletes and back-filling old data yourself. Every new report means another pre-computed total.&lt;/p&gt;

&lt;p&gt;My rule of thumb:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Pick Supabase&lt;/strong&gt; if your product is a B2B SaaS, has reporting or admin screens, needs complex permissions, or will add AI search with embeddings.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Pick Firebase&lt;/strong&gt; if you're building a mobile-first or chat-style app, need offline sync on phones out of the box, already use Google Cloud, or your data really is a set of independent documents (user profiles, messages, feeds).&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you're still scoping your first version, this decision belongs in the planning stage of an &lt;a href="https://muhammadmoiz.dev/services/mvp-development" rel="noopener noreferrer"&gt;MVP build&lt;/a&gt;, not halfway through development.&lt;/p&gt;

&lt;h2&gt;
  
  
  Supabase vs Firebase security: where do apps go wrong?
&lt;/h2&gt;

&lt;p&gt;Both platforms let the browser or mobile app talk to the database directly. That's what makes them fast to build with, and it's also why security has to be done right on day one.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Supabase&lt;/strong&gt; relies on Postgres Row Level Security (RLS). If a table is exposed and RLS is off, or the policies are too loose, anyone with your public anon key can read the data. This is the most common problem I find in apps built with Lovable and other AI tools. I wrote a full guide on it: &lt;a href="https://muhammadmoiz.dev/blog/supabase-rls" rel="noopener noreferrer"&gt;Supabase RLS explained&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Firebase&lt;/strong&gt; relies on Security Rules. The classic mistake is shipping with test-mode rules that allow all reads and writes, or rules that check a user is signed in but not that they own the document.&lt;/li&gt;
&lt;/ul&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Check this before launch&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Whichever you pick, test your access rules with a second, non-admin account. Try to read and change another user's data. If you can, so can anyone else.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Lock-in and switching later
&lt;/h2&gt;

&lt;p&gt;Supabase is open source and the data sits in standard Postgres, so you can export it with normal Postgres tools or move to any Postgres host. That's a real advantage if investors or enterprise clients ask about vendor risk.&lt;/p&gt;

&lt;p&gt;Firebase is a Google product with no self-hosted version. Moving away means rewriting data access code and reshaping documents into tables. Supabase publishes a migration path for this: community scripts that export each Firestore collection to JSON and import it as a Postgres table, flattening fields into text, numeric, boolean or jsonb columns. Nested arrays and objects need custom hooks or your own script to split into related tables, and each collection is migrated separately. It works, but plan time for the data modelling, not just the copy.&lt;/p&gt;

&lt;h2&gt;
  
  
  A quick decision checklist
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Write down your five main entities (users, orders, projects and so on) and how they link. Lots of links points to Supabase.&lt;/li&gt;
&lt;li&gt;List the reports and admin screens you'll need in year one. Cross-collection reports point to Supabase.&lt;/li&gt;
&lt;li&gt;Is it mostly a phone app that must work offline? That points to Firebase.&lt;/li&gt;
&lt;li&gt;Estimate reads per user per day. If a single screen loads hundreds of documents, model the Firestore cost before committing.&lt;/li&gt;
&lt;li&gt;Check if your team or future hires know SQL. Postgres skills are easy to find.&lt;/li&gt;
&lt;li&gt;Decide how much vendor lock-in you can accept.&lt;/li&gt;
&lt;li&gt;Whatever you choose, budget time to write and test RLS policies or Security Rules.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  What this means for founders and app owners
&lt;/h2&gt;

&lt;p&gt;If you're starting fresh, you can't really go wrong with either, as long as the data model fits the tool. The expensive mistakes come from forcing relational data into Firestore, or from launching a Supabase app with RLS switched off.&lt;/p&gt;

&lt;p&gt;If you already have an app built with an AI tool and you're not sure whether the backend is set up safely or will scale, a &lt;a href="https://muhammadmoiz.dev/services/production-audit" rel="noopener noreferrer"&gt;production audit&lt;/a&gt; is the quickest way to find out what needs fixing before real customers arrive. And if you're planning a new product and want help choosing the stack, see how I approach &lt;a href="https://muhammadmoiz.dev/services/mvp-development" rel="noopener noreferrer"&gt;MVP development&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://supabase.com/pricing" rel="noopener noreferrer"&gt;Supabase pricing&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://supabase.com/docs/guides/database/overview" rel="noopener noreferrer"&gt;Supabase docs: Database overview&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://supabase.com/docs/guides/platform/migrating-to-supabase/firestore-data" rel="noopener noreferrer"&gt;Supabase docs: Migrate from Firestore to Supabase&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://cloud.google.com/firestore/pricing" rel="noopener noreferrer"&gt;Google Cloud: Firestore pricing&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://cloud.google.com/identity-platform/pricing" rel="noopener noreferrer"&gt;Google Cloud: Identity Platform pricing&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Cover photo: Christopher Gower on Unsplash&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://muhammadmoiz.dev/blog/supabase-vs-firebase" rel="noopener noreferrer"&gt;muhammadmoiz.dev&lt;/a&gt;. I'm Muhammad Moiz, a senior full-stack engineer building production apps with React, Next.js and Node.js. If you need a hand with your product, &lt;a href="https://muhammadmoiz.dev/contact" rel="noopener noreferrer"&gt;get in touch&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>postgres</category>
      <category>saas</category>
      <category>database</category>
      <category>startup</category>
    </item>
    <item>
      <title>Vibe Coding Security: 8 Holes in Almost Every AI-Built App</title>
      <dc:creator>Muhammad Moiz</dc:creator>
      <pubDate>Fri, 30 Oct 2026 05:10:06 +0000</pubDate>
      <link>https://dev.to/muhammadmoiz269/vibe-coding-security-8-holes-in-almost-every-ai-built-app-2ffj</link>
      <guid>https://dev.to/muhammadmoiz269/vibe-coding-security-8-holes-in-almost-every-ai-built-app-2ffj</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://muhammadmoiz.dev/blog/vibe-coding-security" rel="noopener noreferrer"&gt;muhammadmoiz.dev&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Vibe coding security comes down to one problem: AI app builders are very good at making features work and much less careful about who is allowed to use them. The same handful of holes turn up again and again in AI-built apps, and most of them are about access control, leaked keys and trusting the browser. Below are the 8 that come up most often, how to check for each one in an afternoon, and what to do when you find them.&lt;/p&gt;

&lt;p&gt;This is written for founders who built with Lovable, Bolt, Replit, Cursor or v0, and for developers who just inherited one of those projects.&lt;/p&gt;

&lt;h2&gt;
  
  
  Is Lovable safe? Why AI-built apps share the same weaknesses
&lt;/h2&gt;

&lt;p&gt;The tools themselves are not the problem. The problem is the default architecture they produce. Most AI builders generate a React frontend that talks directly to a backend-as-a-service such as Supabase or Firebase. There is often no server of your own in between. That means the browser is the only place where "rules" live, unless someone deliberately writes them into the database.&lt;/p&gt;

&lt;p&gt;This is not a theory. CVE-2025-48757, published on 30 May 2025, describes insufficient Row Level Security in sites generated by Lovable up to 15 April 2025, which let unauthenticated attackers read or write arbitrary tables. The CVE record gives it a CVSS 3.1 base score of 9.3 (critical). Lovable disputes the entry, and the record notes their position that each customer is responsible for protecting their own app's data.&lt;/p&gt;

&lt;p&gt;That dispute is the key lesson for any founder: whoever's fault it is, your users' data is your responsibility. The AI tool will not be the one emailing your customers about a breach.&lt;/p&gt;

&lt;h2&gt;
  
  
  The 8 vibe coding security holes
&lt;/h2&gt;

&lt;h3&gt;
  
  
  1. Row Level Security is missing or does nothing
&lt;/h3&gt;

&lt;p&gt;With Supabase, your publishable (anon) key ships inside the frontend. That is by design. Supabase's own docs say requests made with it are limited to whatever Row Level Security allows. So RLS is the actual lock on your data.&lt;/p&gt;

&lt;p&gt;The common failures:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;RLS is turned off on one or more tables in the &lt;code&gt;public&lt;/code&gt; schema.&lt;/li&gt;
&lt;li&gt;RLS is on, but a policy like &lt;code&gt;using (true)&lt;/code&gt; lets everyone read everything.&lt;/li&gt;
&lt;li&gt;Policies check that a user is logged in, but not that the row belongs to them.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A safer pattern for a table where each user owns their rows looks like this:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight sql"&gt;&lt;code&gt;&lt;span class="k"&gt;alter&lt;/span&gt; &lt;span class="k"&gt;table&lt;/span&gt; &lt;span class="n"&gt;invoices&lt;/span&gt; &lt;span class="n"&gt;enable&lt;/span&gt; &lt;span class="k"&gt;row&lt;/span&gt; &lt;span class="k"&gt;level&lt;/span&gt; &lt;span class="k"&gt;security&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="k"&gt;create&lt;/span&gt; &lt;span class="n"&gt;policy&lt;/span&gt; &lt;span class="nv"&gt;"owners read their invoices"&lt;/span&gt;
&lt;span class="k"&gt;on&lt;/span&gt; &lt;span class="n"&gt;invoices&lt;/span&gt; &lt;span class="k"&gt;for&lt;/span&gt; &lt;span class="k"&gt;select&lt;/span&gt;
&lt;span class="k"&gt;to&lt;/span&gt; &lt;span class="n"&gt;authenticated&lt;/span&gt;
&lt;span class="k"&gt;using&lt;/span&gt; &lt;span class="p"&gt;((&lt;/span&gt;&lt;span class="k"&gt;select&lt;/span&gt; &lt;span class="n"&gt;auth&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;uid&lt;/span&gt;&lt;span class="p"&gt;())&lt;/span&gt; &lt;span class="k"&gt;is&lt;/span&gt; &lt;span class="k"&gt;not&lt;/span&gt; &lt;span class="k"&gt;null&lt;/span&gt; &lt;span class="k"&gt;and&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="k"&gt;select&lt;/span&gt; &lt;span class="n"&gt;auth&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;uid&lt;/span&gt;&lt;span class="p"&gt;())&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;owner_id&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Supabase recommends the explicit &lt;code&gt;is not null&lt;/code&gt; check because &lt;code&gt;auth.uid()&lt;/code&gt; returns null for anonymous requests, and wrapping it in &lt;code&gt;select&lt;/code&gt; lets Postgres evaluate it once per query instead of once per row. I covered this hole in depth in &lt;a href="https://muhammadmoiz.dev/blog/supabase-rls" rel="noopener noreferrer"&gt;Supabase RLS explained&lt;/a&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Secret keys shipped to the browser
&lt;/h3&gt;

&lt;p&gt;The Supabase secret key (formerly the &lt;code&gt;service_role&lt;/code&gt; key) bypasses every RLS policy. It belongs on a server, in an Edge Function or in a scheduled job, never in frontend code, never in Git. A common way it ends up in client code: an AI assistant "fixes" a permissions error by swapping the publishable key for the secret one.&lt;/p&gt;

&lt;p&gt;The same mistake happens with environment variables. In Next.js, any variable prefixed with &lt;code&gt;NEXT_PUBLIC_&lt;/code&gt; is inlined into the JavaScript bundle at build time, so anyone can read it in their browser's dev tools. Other build tools have similar public prefixes. If a payment provider secret, OpenAI key or database password has a public prefix, treat it as leaked: rotate it, then move the call that needs it to the server.&lt;/p&gt;

&lt;p&gt;Quick check: open your live site, open dev tools, search the loaded JavaScript for &lt;code&gt;sb_secret_&lt;/code&gt;, &lt;code&gt;service_role&lt;/code&gt; and the start of any secret key from your payment or AI provider.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Security rules that only exist in the UI
&lt;/h3&gt;

&lt;p&gt;Hiding the "Delete" button for non-admins is not security. Neither is a redirect on the admin page. Anyone can call your API, your Supabase tables or your server functions directly with a tool like curl.&lt;/p&gt;

&lt;p&gt;The Next.js docs make this point clearly for Server Actions: an exported action can be called with a direct POST request, so the page-level login check does not protect it. Each action needs its own check.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight typescript"&gt;&lt;code&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;use server&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;

&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;getSession&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;@/lib/session&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;db&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;@/lib/db&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;

&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="k"&gt;async&lt;/span&gt; &lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;archiveProject&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;projectId&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kr"&gt;string&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;session&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nf"&gt;getSession&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt;
  &lt;span class="k"&gt;if &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="nx"&gt;session&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;throw&lt;/span&gt; &lt;span class="k"&gt;new&lt;/span&gt; &lt;span class="nc"&gt;Error&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;Not signed in&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;

  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;project&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nx"&gt;db&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;project&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;findFirst&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt;
    &lt;span class="na"&gt;where&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;id&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;projectId&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="na"&gt;ownerId&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;session&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;userId&lt;/span&gt; &lt;span class="p"&gt;},&lt;/span&gt;
  &lt;span class="p"&gt;})&lt;/span&gt;
  &lt;span class="k"&gt;if &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="nx"&gt;project&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;throw&lt;/span&gt; &lt;span class="k"&gt;new&lt;/span&gt; &lt;span class="nc"&gt;Error&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;Not found&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;

  &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nx"&gt;db&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;project&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;update&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt; &lt;span class="na"&gt;where&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;id&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;project&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;id&lt;/span&gt; &lt;span class="p"&gt;},&lt;/span&gt; &lt;span class="na"&gt;data&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;archived&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kc"&gt;true&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="p"&gt;})&lt;/span&gt;
  &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;ok&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kc"&gt;true&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  4. Trusting IDs sent from the client (IDOR)
&lt;/h3&gt;

&lt;p&gt;This is the cousin of hole 3. The user is logged in, but the app takes an ID from the URL or request body and loads that record without asking whether it belongs to them. Change &lt;code&gt;/orders/1041&lt;/code&gt; to &lt;code&gt;/orders/1042&lt;/code&gt; and you see a stranger's order. The OWASP name for this is Insecure Direct Object Reference.&lt;/p&gt;

&lt;p&gt;The fix is always the same: look up the record using both the ID and the current user (as in the example above), or let RLS enforce ownership in the database.&lt;/p&gt;

&lt;h3&gt;
  
  
  5. Admin flags and roles the user can edit
&lt;/h3&gt;

&lt;p&gt;AI-generated schemas often put &lt;code&gt;role&lt;/code&gt; or &lt;code&gt;is_admin&lt;/code&gt; on the same &lt;code&gt;profiles&lt;/code&gt; table that users are allowed to update. If the update policy covers the whole row, any user can promote themselves to admin with one request. Another variant reads a role from local storage or a query string, which the Next.js docs specifically call out as untrusted input.&lt;/p&gt;

&lt;p&gt;Keep roles in a table users cannot write to, or restrict updates to specific columns, and verify the role on the server every time.&lt;/p&gt;

&lt;h3&gt;
  
  
  6. File storage that is more public than you think
&lt;/h3&gt;

&lt;p&gt;Uploaded invoices, ID photos and contracts often end up in a public bucket because that made the images load during development. In Supabase, objects in a public bucket can be read by anyone who has the URL, with no policy needed. Supabase does block uploads until you add policies on &lt;code&gt;storage.objects&lt;/code&gt;, so AI tools sometimes add a very broad policy to make uploads work.&lt;/p&gt;

&lt;p&gt;Use private buckets for anything personal, generate signed URLs when a user needs to view a file, and scope storage policies to a folder per user.&lt;/p&gt;

&lt;h3&gt;
  
  
  7. No rate limits on expensive actions
&lt;/h3&gt;

&lt;p&gt;Supabase Auth applies rate limits to its own sign-in, sign-up and email endpoints. Your custom functions are a different story. A contact form that sends email, an endpoint that calls an AI model, or a function that writes to the database can be hit thousands of times by a script. The result is a surprise bill, a blacklisted email domain or a flooded database. The Next.js data security guide recommends rate limiting exactly these kinds of operations.&lt;/p&gt;

&lt;p&gt;Add per-IP and per-user limits to anything that costs money or sends messages, and set spending caps on your AI provider account.&lt;/p&gt;

&lt;h3&gt;
  
  
  8. Returning far more data than the screen needs
&lt;/h3&gt;

&lt;p&gt;A &lt;code&gt;select *&lt;/code&gt; that sends the full user record to the browser, including email, phone, internal notes or a password reset token, is a leak even if the UI only shows the name. Anything in a network response is visible to the user who received it.&lt;/p&gt;

&lt;p&gt;Select only the columns the page needs. In Next.js, the docs recommend a server-only data layer that returns small, safe objects rather than raw database rows.&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%2Fimages.unsplash.com%2Fphoto-1555066931-4365d14bab8c%3Fw%3D1200%26q%3D80" 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%2Fimages.unsplash.com%2Fphoto-1555066931-4365d14bab8c%3Fw%3D1200%26q%3D80" alt="Laptop screen showing application source code"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Photo: Arnold Francisca on Unsplash&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Vibe coding best practices: a one-afternoon security checklist
&lt;/h2&gt;

&lt;p&gt;You can work through this list yourself before paying anyone. Each line is a yes/no question.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Check&lt;/th&gt;
&lt;th&gt;How to test it&lt;/th&gt;
&lt;th&gt;Red flag&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;RLS on every table&lt;/td&gt;
&lt;td&gt;Check each table's RLS status in the Supabase dashboard&lt;/td&gt;
&lt;td&gt;Any exposed table with RLS off&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Policies scoped to owner&lt;/td&gt;
&lt;td&gt;Read each policy's &lt;code&gt;using&lt;/code&gt; clause&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;true&lt;/code&gt;, or no &lt;code&gt;auth.uid()&lt;/code&gt; reference&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;No secrets in the bundle&lt;/td&gt;
&lt;td&gt;Search the live site's JS in dev tools&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;sb_secret_&lt;/code&gt;, &lt;code&gt;service_role&lt;/code&gt;, any secret key&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Server checks on every action&lt;/td&gt;
&lt;td&gt;Call an endpoint with curl while logged out&lt;/td&gt;
&lt;td&gt;It succeeds&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Ownership checks&lt;/td&gt;
&lt;td&gt;Change an ID in the URL while logged in&lt;/td&gt;
&lt;td&gt;You see another user's data&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Roles protected&lt;/td&gt;
&lt;td&gt;Try updating your own &lt;code&gt;role&lt;/code&gt; column via the API&lt;/td&gt;
&lt;td&gt;It works&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Private storage&lt;/td&gt;
&lt;td&gt;Open a document URL in a private window&lt;/td&gt;
&lt;td&gt;It loads&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Rate limits&lt;/td&gt;
&lt;td&gt;Submit a form 50 times quickly&lt;/td&gt;
&lt;td&gt;Every request succeeds&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Minimal responses&lt;/td&gt;
&lt;td&gt;Inspect network responses on profile pages&lt;/td&gt;
&lt;td&gt;Fields the UI never shows&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;.env files out of Git&lt;/td&gt;
&lt;td&gt;Check your repo history&lt;/td&gt;
&lt;td&gt;A committed &lt;code&gt;.env&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Test with a second account:&lt;/strong&gt; Most of these holes only show up when you are logged in as one user and try to reach another user's data. Create two test accounts and try to read, edit and delete each other's records. If you can, so can anyone.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  What to do when you find a hole
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt; &lt;strong&gt;Rotate anything leaked first.&lt;/strong&gt; A key that was ever in a public bundle or repository is compromised, even if you remove it now.&lt;/li&gt;
&lt;li&gt; &lt;strong&gt;Lock down the database.&lt;/strong&gt; Enable RLS everywhere, then add the narrowest policies that keep the app working. Supabase's docs suggest testing allowed and denied operations for both the anon and authenticated roles.&lt;/li&gt;
&lt;li&gt; &lt;strong&gt;Move privileged calls to the server.&lt;/strong&gt; Payments, emails, AI calls and admin operations belong in server routes or Edge Functions.&lt;/li&gt;
&lt;li&gt; &lt;strong&gt;Check your logs.&lt;/strong&gt; Look for unusual reads or writes before the fix, in case you need to notify users.&lt;/li&gt;
&lt;li&gt; &lt;strong&gt;Stop the AI from undoing it.&lt;/strong&gt; When you prompt for new features, tell the tool explicitly not to change policies or swap keys, and review every diff that touches auth or the database.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  What this means for founders and app owners
&lt;/h2&gt;

&lt;p&gt;An AI builder can get you to a working demo in days, and that is genuinely valuable. But "it works" and "it is safe to put real customer data in" are separate milestones. If you are about to take payments, store personal data, onboard a business client or raise money, a security review is part of shipping, not an extra.&lt;/p&gt;

&lt;p&gt;If the checklist turned up red flags, or you are not sure how to read the results, a &lt;a href="https://muhammadmoiz.dev/services/production-audit" rel="noopener noreferrer"&gt;production audit&lt;/a&gt; gives you a prioritised list of what is exposed and how to fix it. If you would rather hand the whole thing over, I also &lt;a href="https://muhammadmoiz.dev/services/ai-app-production-ready" rel="noopener noreferrer"&gt;take AI-built apps to production&lt;/a&gt;, keeping what works and rebuilding what does not.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2025/48xxx/CVE-2025-48757.json" rel="noopener noreferrer"&gt;CVE-2025-48757 record (CVE Program, cvelistV5 on GitHub)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://supabase.com/docs/guides/api/api-keys" rel="noopener noreferrer"&gt;Supabase docs: Understanding API keys&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://supabase.com/docs/guides/database/postgres/row-level-security" rel="noopener noreferrer"&gt;Supabase docs: Row Level Security&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://supabase.com/docs/guides/storage/security/access-control" rel="noopener noreferrer"&gt;Supabase docs: Storage access control&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://supabase.com/docs/guides/auth/rate-limits" rel="noopener noreferrer"&gt;Supabase docs: Auth rate limits&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://nextjs.org/docs/app/guides/environment-variables" rel="noopener noreferrer"&gt;Next.js docs: Environment variables&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://nextjs.org/docs/app/guides/data-security" rel="noopener noreferrer"&gt;Next.js docs: Data security&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://owasp.org/www-project-top-ten/" rel="noopener noreferrer"&gt;OWASP Top 10&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Cover photo: FlyD on Unsplash&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;I'm Muhammad Moiz, a full-stack developer who builds web apps, SaaS and POS systems, and takes AI-built apps (Lovable, Bolt, Replit) to production. &lt;a href="https://muhammadmoiz.dev/contact" rel="noopener noreferrer"&gt;Get in touch&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>security</category>
      <category>ai</category>
      <category>webdev</category>
      <category>supabase</category>
    </item>
    <item>
      <title>PHP Critical RCE Vulnerabilities CVE-2026-109618 and CVE-2026-109619: How to Patch</title>
      <dc:creator>Muhammad Moiz</dc:creator>
      <pubDate>Fri, 30 Oct 2026 05:10:00 +0000</pubDate>
      <link>https://dev.to/muhammadmoiz269/php-critical-rce-vulnerabilities-cve-2026-109618-and-cve-2026-109619-how-to-patch-i1i</link>
      <guid>https://dev.to/muhammadmoiz269/php-critical-rce-vulnerabilities-cve-2026-109618-and-cve-2026-109619-how-to-patch-i1i</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://muhammadmoiz.dev/blog/php-rce-cve-2026-109618-cve-2026-109619-patch-guide" rel="noopener noreferrer"&gt;muhammadmoiz.dev&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Two critical bugs in PHP itself, CVE-2026-109618 and CVE-2026-109619, can let an attacker run code on a web server without logging in. They were fixed on 21 October 2026 in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35, and every earlier release on those branches is affected. If your website, WordPress install or API runs on PHP, the fix is to upgrade the PHP runtime, not your plugins or framework.&lt;/p&gt;

&lt;h2&gt;
  
  
  What happened
&lt;/h2&gt;

&lt;p&gt;The PHP project published two GitHub security advisories on 21 October 2026, both rated Critical with a CVSS v4 score of 9.2. On the same day it shipped patch releases on all four supported branches. The release notes put it bluntly: "There are no complete mitigations, updating is the only safe choice."&lt;/p&gt;

&lt;p&gt;The score reflects a network attack that needs no account and no user interaction, but does need certain conditions to line up (that is why attack complexity is marked high). In plain terms: it is not trivial to pull off, but an outsider can attempt it against a public server, and the payoff is full control of the PHP worker process.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Branch&lt;/th&gt;
&lt;th&gt;Vulnerable&lt;/th&gt;
&lt;th&gt;Fixed in&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;PHP 8.5&lt;/td&gt;
&lt;td&gt;below 8.5.12&lt;/td&gt;
&lt;td&gt;8.5.12&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;PHP 8.4&lt;/td&gt;
&lt;td&gt;below 8.4.27&lt;/td&gt;
&lt;td&gt;8.4.27&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;PHP 8.3&lt;/td&gt;
&lt;td&gt;below 8.3.36&lt;/td&gt;
&lt;td&gt;8.3.36&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;PHP 8.2&lt;/td&gt;
&lt;td&gt;below 8.2.35&lt;/td&gt;
&lt;td&gt;8.2.35&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Note that the 8.2.35 release notes also remind users that PHP 8.2 reaches end of life on 31 December 2026. Branches older than 8.2 are not listed in the advisories, so treat them as unpatched and unsupported.&lt;/p&gt;

&lt;h2&gt;
  
  
  The two bugs, explained without the jargon
&lt;/h2&gt;

&lt;h3&gt;
  
  
  CVE-2026-109618: memory exhaustion leaves PHP in a broken state
&lt;/h3&gt;

&lt;p&gt;When a PHP request runs out of memory, the engine historically bailed out of whatever it was doing with an abrupt jump. The advisory explains that some code paths make freshly allocated request memory visible before it is fully set up. If any allocation fails at that exact moment, even an unrelated one, the request is left holding half-initialised data, and the shutdown routine later trusts it.&lt;/p&gt;

&lt;p&gt;The scary part is how an attacker forces the out-of-memory condition. The advisory lists several ways, including multipart (file upload style) requests with a huge number of headers per part, many empty file fields that still create metadata, and deeply nested field names. Under Apache with mod_php, the researchers confirmed full remote code execution over HTTP with default memory and input limits, before any of your application code even runs. PHP-FPM is believed to be susceptible based on source analysis, but no complete FPM exploit was demonstrated. FrankenPHP and LSAPI are flagged as likely susceptible but not validated.&lt;/p&gt;

&lt;p&gt;The fix replaces the abrupt jump with a graceful "soft" out-of-memory stop at a safe point, plus a hard process exit if memory keeps climbing past a second threshold.&lt;/p&gt;

&lt;h3&gt;
  
  
  CVE-2026-109619: leftover state from a previous request
&lt;/h3&gt;

&lt;p&gt;Long-running PHP workers handle many requests in a row. This advisory describes global state (error, session, object and extension data) that can survive after the memory behind it is freed. A later request that touches that state before normal start-up reads freed memory, which is a classic use-after-free.&lt;/p&gt;

&lt;p&gt;Two confirmed paths stand out:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;PHP 8.5 with &lt;code&gt;fatal_error_backtraces&lt;/code&gt; enabled.&lt;/strong&gt; The backtrace data is not cleared after a fatal error, and a later diagnostic reads it. This is the basis of the confirmed mod_php exploit.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Session upload progress.&lt;/strong&gt; This feature is on by default and does not need your code to call &lt;code&gt;session_start()&lt;/code&gt;. A fatal error or memory exhaustion during input processing can leave it pointing at freed memory. It was validated against both mod_php and PHP-FPM.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;An attacker needs two requests to land on the same worker: one to plant the stale state and one to trigger it. More workers make that harder, but the advisory is clear that it does not remove the risk.&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%2Fimages.unsplash.com%2Fphoto-1564457461758-8ff96e439e83%3Fw%3D1200%26q%3D80" 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%2Fimages.unsplash.com%2Fphoto-1564457461758-8ff96e439e83%3Fw%3D1200%26q%3D80" alt="Rows of server cabinets in a data center connected by blue network cables"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Photo: Taylor Vick on Unsplash&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Who is affected
&lt;/h2&gt;

&lt;p&gt;If any of these describe your setup, you should act this week:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A WordPress, WooCommerce, Laravel, Symfony, Drupal or custom PHP site on a PHP version below the fixed releases above.&lt;/li&gt;
&lt;li&gt;Apache with mod_php. This is the configuration with confirmed, application-independent exploitation.&lt;/li&gt;
&lt;li&gt;PHP-FPM behind nginx or Apache. Exposure is conditional, but session upload progress was validated on FPM.&lt;/li&gt;
&lt;li&gt;Docker images that pin an older &lt;code&gt;php:8.x&lt;/code&gt; tag and have not been rebuilt since 21 October.&lt;/li&gt;
&lt;li&gt;Shared or managed hosting. Your host controls the PHP binary, so you need to confirm they have rolled out the patched build.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Updating WordPress core, a theme or a plugin does nothing here. The bug lives in the language runtime underneath them.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to patch: a practical checklist
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt; &lt;strong&gt;Find your real PHP version.&lt;/strong&gt; The command-line PHP and the web-server PHP are sometimes different builds, so check both.
&lt;/li&gt;
&lt;/ol&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;# CLI version&lt;/span&gt;
php &lt;span class="nt"&gt;-v&lt;/span&gt;

&lt;span class="c"&gt;# FPM version (binary name varies by distro, e.g. php-fpm8.3)&lt;/span&gt;
php-fpm &lt;span class="nt"&gt;-v&lt;/span&gt;

&lt;span class="c"&gt;# Settings that matter for the mitigations below&lt;/span&gt;
php &lt;span class="nt"&gt;-i&lt;/span&gt; | &lt;span class="nb"&gt;grep&lt;/span&gt; &lt;span class="nt"&gt;-E&lt;/span&gt; &lt;span class="s1"&gt;'memory_limit|session.upload_progress.enabled|fatal_error_backtraces'&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;For the web server, a temporary &lt;code&gt;phpinfo()&lt;/code&gt; page works, but delete it straight after.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt; &lt;strong&gt;Upgrade to the fixed release for your branch.&lt;/strong&gt; Use your distribution's security repository, your host's control panel, or a rebuilt container image. For Docker, bump the base image tag and rebuild rather than relying on a cached layer.
&lt;/li&gt;
&lt;/ol&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;# Example: confirm the image you ship actually contains the fix&lt;/span&gt;
docker run &lt;span class="nt"&gt;--rm&lt;/span&gt; your-app-image php &lt;span class="nt"&gt;-v&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;ol&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Restart every worker.&lt;/strong&gt; A new binary on disk does not help while old FPM children or Apache processes stay in memory. Restart the service, not just reload configuration.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Verify in production.&lt;/strong&gt; Re-run the version check against the live server and record the result.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Plan your branch.&lt;/strong&gt; If you are on 8.2, schedule a move to 8.3 or newer before the end of December. If you are on anything older than 8.2, upgrading is now urgent rather than optional.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Settings tweaks are a stopgap, not a fix:&lt;/strong&gt; The advisories say updating is the only complete mitigation. Use the settings below only to reduce risk for the few days it takes to get a patched build deployed.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  If you cannot upgrade today
&lt;/h2&gt;

&lt;p&gt;Both advisories list temporary measures. In summary:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Turn off session upload progress&lt;/strong&gt; (&lt;code&gt;session.upload_progress.enabled=0&lt;/code&gt;) and restart workers. The advisory suggests leaving it off even after patching if you don't use it, and most sites don't.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;On PHP 8.5, set &lt;code&gt;fatal_error_backtraces=0&lt;/code&gt;&lt;/strong&gt; at the administrative level and restart. This removes the confirmed exploit path for the second bug, but not every possible one.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Tighten request limits at the edge.&lt;/strong&gt; Keep &lt;code&gt;post_max_size&lt;/code&gt; conservative, cap decoded request size at your reverse proxy or WAF, and block multipart requests entirely on endpoints that never accept uploads.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Lower input limits&lt;/strong&gt; such as &lt;code&gt;max_input_nesting_level&lt;/code&gt; and the number of input variables, parts and uploads.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Avoid &lt;code&gt;RLIMIT_AS&lt;/code&gt; and &lt;code&gt;RLIMIT_DATA&lt;/code&gt;&lt;/strong&gt; as a memory cap. The advisory warns these make allocations fail in exactly the way that triggers the first bug.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The first advisory also mentions &lt;code&gt;memory_limit=-1&lt;/code&gt; as a partial configuration mitigation, with the caveat that it is incomplete and that an unbounded memory limit brings its own denial-of-service risk. Treat it with care.&lt;/p&gt;

&lt;h2&gt;
  
  
  What it means for business and app owners
&lt;/h2&gt;

&lt;p&gt;For a non-technical founder, the short version is this: your website's engine had a serious flaw, and the engine has to be replaced, not the bodywork. Ask whoever runs your hosting or code three direct questions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Which PHP version is serving our live site right now?&lt;/li&gt;
&lt;li&gt;When was it updated, and were all workers restarted?&lt;/li&gt;
&lt;li&gt;Are we on a branch that still gets security fixes after this year?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If nobody can answer quickly, that is a sign your stack lacks basic visibility, and a one-off &lt;a href="https://muhammadmoiz.dev/services/production-audit" rel="noopener noreferrer"&gt;production audit&lt;/a&gt; of versions, hosting and patching is usually great value compared with cleaning up after a breach. If you run WordPress and want someone to handle the PHP upgrade and test your plugins against the new version, &lt;a href="https://muhammadmoiz.dev/services/wordpress-development" rel="noopener noreferrer"&gt;WordPress development support&lt;/a&gt; covers exactly that kind of job.&lt;/p&gt;

&lt;p&gt;The broader lesson is that "keep plugins updated" is only half of PHP security. The runtime, the web server and the container image all need an owner and a patch routine, and this month's release is a good prompt to set one up.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://github.com/php/php-src/security/advisories/GHSA-w8hw-w9fx-j79w" rel="noopener noreferrer"&gt;PHP security advisory GHSA-w8hw-w9fx-j79w: RCE via OOM corruption (CVE-2026-109618)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/php/php-src/security/advisories/GHSA-6wmf-4rv5-p3rp" rel="noopener noreferrer"&gt;PHP security advisory GHSA-6wmf-4rv5-p3rp: RCE via stale global state (CVE-2026-109619)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/php/php-src/releases" rel="noopener noreferrer"&gt;php-src releases on GitHub (8.5.12, 8.4.27, 8.3.36, 8.2.35)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/php/php-src/security" rel="noopener noreferrer"&gt;php-src security advisories overview&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Cover photo: FlyD on Unsplash&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;I'm Muhammad Moiz, a full-stack developer who builds web apps, SaaS and POS systems, and takes AI-built apps (Lovable, Bolt, Replit) to production. &lt;a href="https://muhammadmoiz.dev/contact" rel="noopener noreferrer"&gt;Get in touch&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>php</category>
      <category>security</category>
      <category>webdev</category>
      <category>devops</category>
    </item>
    <item>
      <title>Lovable vs Replit vs Bolt vs Cursor: Which to Use, and When You Need a Developer</title>
      <dc:creator>Muhammad Moiz</dc:creator>
      <pubDate>Thu, 29 Oct 2026 05:10:58 +0000</pubDate>
      <link>https://dev.to/muhammadmoiz269/lovable-vs-replit-vs-bolt-vs-cursor-which-to-use-and-when-you-need-a-developer-32j7</link>
      <guid>https://dev.to/muhammadmoiz269/lovable-vs-replit-vs-bolt-vs-cursor-which-to-use-and-when-you-need-a-developer-32j7</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://muhammadmoiz.dev/blog/lovable-vs-replit" rel="noopener noreferrer"&gt;muhammadmoiz.dev&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Lovable vs Replit&lt;/strong&gt; comes down to what you want to own at the end. Lovable is the faster path to a polished web app when you mostly describe screens in chat, Replit suits founders who want an AI agent plus a full coding workspace and hosting in one place, Bolt sits between them, and Cursor is a code editor for people (or developers) who already work in a codebase. All four can get you to a working prototype; none of them replaces the engineering work a real product needs once paying users, private data and growth arrive.&lt;/p&gt;

&lt;p&gt;Below is a practical comparison written for founders, with prices taken from each vendor's pricing page as of October 2026, plus the signals that tell you it's time to bring in a developer.&lt;/p&gt;

&lt;h2&gt;
  
  
  Lovable vs Replit vs Bolt vs Cursor at a glance
&lt;/h2&gt;

&lt;p&gt;These tools are often lumped together, but they solve different problems. Three are "describe it and the AI builds it" app builders. Cursor is a different category: an AI-first editor and agent for working inside real code.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;Lovable&lt;/th&gt;
&lt;th&gt;Replit&lt;/th&gt;
&lt;th&gt;Bolt&lt;/th&gt;
&lt;th&gt;Cursor&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Best for&lt;/td&gt;
&lt;td&gt;Non-technical founders building web apps by chat&lt;/td&gt;
&lt;td&gt;Founders who want an agent plus a full dev environment&lt;/td&gt;
&lt;td&gt;Quick web apps, prototypes and sites&lt;/td&gt;
&lt;td&gt;Developers and technical founders editing real code&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;How you work&lt;/td&gt;
&lt;td&gt;Chat, visual preview&lt;/td&gt;
&lt;td&gt;Chat with Agent, plus code editor&lt;/td&gt;
&lt;td&gt;Chat, preview, start from Figma or GitHub&lt;/td&gt;
&lt;td&gt;IDE, CLI and cloud agents&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Backend&lt;/td&gt;
&lt;td&gt;Lovable Cloud, billed from your credits&lt;/td&gt;
&lt;td&gt;Built-in database and user auth&lt;/td&gt;
&lt;td&gt;Built-in databases on every plan&lt;/td&gt;
&lt;td&gt;Whatever your project uses&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Code ownership&lt;/td&gt;
&lt;td&gt;You own your code; GitHub sync&lt;/td&gt;
&lt;td&gt;Code lives in your Replit workspace&lt;/td&gt;
&lt;td&gt;Can start from your GitHub repo&lt;/td&gt;
&lt;td&gt;Your repo from day one&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Starting paid price (Oct 2026)&lt;/td&gt;
&lt;td&gt;Credit-based Pro and Business plans&lt;/td&gt;
&lt;td&gt;Core: $20/month ($18 billed yearly)&lt;/td&gt;
&lt;td&gt;Pro: $25/month&lt;/td&gt;
&lt;td&gt;Plus: $8/month (Grok models only)&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;A note on Lovable pricing: its pricing page sells Pro and Business on credits rather than seats, and the plan table didn't load when I checked, so I'm not quoting a number. What the page does confirm is that the free plan gives 5 build credits a day (capped at 30 a month) plus 20 Cloud credits a month, and paid plans add a monthly credit balance on top of those daily grants.&lt;/p&gt;

&lt;h2&gt;
  
  
  Lovable vs Bolt: which is better for a first version?
&lt;/h2&gt;

&lt;p&gt;Both are aimed at people who want a working web app without writing code, so this is the comparison most founders actually face.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Lovable&lt;/strong&gt; describes itself as a full-stack engineer you chat with, and it pushes your project to GitHub and deploys in one click. Its newer model puts building, hosting and AI features in your app on one credit balance. Hosting a small app is usually covered by the included grant, but the pricing FAQ is clear that apps with serious traffic or size start drawing on your credits. That's fair, but it means your hosting bill and your "AI typing" bill now share one pot, so watch it as you grow.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Bolt&lt;/strong&gt; is token-based. The free plan includes 1M tokens a month (with a 300K daily limit), and Pro at $25/month includes 10M tokens with rollover, a custom domain and no Bolt branding. Teams is $30 per member per month. Every plan, including free, lists unlimited databases and hosting, and you can start from a blank prompt, a Figma file or a GitHub repo.&lt;/p&gt;

&lt;p&gt;In practice:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Pick &lt;strong&gt;Lovable&lt;/strong&gt; if you want the most guided experience and a clean GitHub handoff later.&lt;/li&gt;
&lt;li&gt;Pick &lt;strong&gt;Bolt&lt;/strong&gt; if you want predictable token budgets, want to start from an existing design or repo, or need a custom domain on the entry paid plan.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Lovable vs Replit: what's the real difference?
&lt;/h2&gt;

&lt;p&gt;Replit is a full cloud development environment that grew an AI agent, rather than an AI builder that later exposed the code. That changes how it feels.&lt;/p&gt;

&lt;p&gt;According to Replit's product page, its Agent builds from a chat description, uses Replit's own database and user authentication, can connect services like Stripe through stored keys, and periodically tests the app in a browser and fixes what it finds. Core costs $20/month (or $18/month billed yearly) and includes $20 of usage toward the more powerful models. Pro is $100/month ($90 billed yearly) with $100 of credits, up to 10 parallel agents and database rollback up to 28 days.&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%2Fimages.unsplash.com%2Fphoto-1504707748692-419802cf939d%3Fw%3D1200%26q%3D80" 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%2Fimages.unsplash.com%2Fphoto-1504707748692-419802cf939d%3Fw%3D1200%26q%3D80" alt="Open MacBook Pro on a grey desk, ready for building an app" width="1200" height="822"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Photo: Ben Kolde on Unsplash&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;So the honest answer to "Lovable vs Replit" is:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Lovable&lt;/strong&gt; is better when the person driving is non-technical and the product is a web app with a typical dashboard, forms and auth.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Replit&lt;/strong&gt; is better when you want to see and touch everything (files, terminal, database) in the same place, or when the app includes background jobs, bots or scripts that don't fit neatly into a web-app template.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Lovable vs Cursor: different tools for different stages
&lt;/h2&gt;

&lt;p&gt;People compare these because both "write code with AI", but they sit at opposite ends of a project.&lt;/p&gt;

&lt;p&gt;Cursor is an editor and agent that works on a real codebase: a desktop IDE, a terminal CLI, cloud agents that work in parallel and review pull requests in GitHub. You choose between models from several labs, including Cursor's own Composer. It also changed hands this year: Cursor's site says it is now part of SpaceX, in a post dated August 14, 2026, and its pricing now bundles Grok models. Plus is $8/month for Grok models only, Premium is $30/month with cloud agents and code reviews, and third-party models on the paid tiers are billed separately by usage.&lt;/p&gt;

&lt;p&gt;That makes the decision simple:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;If you can't read code, Cursor will feel like being handed the keys to a workshop. Start with an app builder.&lt;/li&gt;
&lt;li&gt;If your Lovable or Bolt project is already on GitHub and a developer is now maintaining it, Cursor (or a similar editor) is where that work tends to move.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What about Lovable vs v0?
&lt;/h2&gt;

&lt;p&gt;v0 is Vercel's AI app builder (Vercel's own v0 docs now point to v0.app). I couldn't verify its current plans or features this month, so check its site directly before deciding. The general rule still holds: if your app's success depends on SEO and fast page loads, a framework with server rendering (like Next.js) gives you a better base than a purely client-rendered single-page app.&lt;/p&gt;

&lt;h2&gt;
  
  
  Which one should you use? A quick decision guide
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;You're non-technical and need a clickable product to show investors or early users:&lt;/strong&gt; Lovable or Bolt.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;You want an agent, but also a real environment with a database, terminal and hosting:&lt;/strong&gt; Replit.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;You (or your developer) already have a codebase and want AI to speed up the work:&lt;/strong&gt; Cursor.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;You care about search traffic from day one:&lt;/strong&gt; favour a server-rendered setup such as Next.js, whichever tool generates it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;You're handling payments, health or personal data:&lt;/strong&gt; use any tool to prototype, but plan a security review before launch.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  When the AI tool stops being enough
&lt;/h2&gt;

&lt;p&gt;Every one of these tools is excellent at the first 70% of an app. The trouble shows up in the last 30%, and it usually arrives as one of these:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;The AI starts breaking things it fixed yesterday.&lt;/strong&gt; Each prompt patches one screen and quietly damages another, and credits or tokens burn on going in circles.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Security is "probably fine".&lt;/strong&gt; Database rules are open, API keys sit in the frontend, or every logged-in user can read every other user's rows. On Supabase-backed apps this is usually a Row Level Security problem; I wrote about it in &lt;a href="https://muhammadmoiz.dev/blog/supabase-rls" rel="noopener noreferrer"&gt;Supabase RLS explained&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Payments, roles and edge cases get complicated.&lt;/strong&gt; Subscriptions with upgrades, refunds and team accounts are where generated code gets fragile.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Google can't see your site.&lt;/strong&gt; A client-rendered app often shows search engines an almost empty page.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;You can't hire anyone to maintain it.&lt;/strong&gt; Nobody can explain how the code is structured, so every change is a gamble.&lt;/li&gt;
&lt;/ul&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Keep the AI tool, fix the foundation:&lt;/strong&gt; Hitting these limits doesn't mean starting over. Export the code to GitHub, get it reviewed, fix the risky parts, and keep building on it with a developer (and AI) in the loop.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  What this means for a founder
&lt;/h2&gt;

&lt;p&gt;The tool you start with matters less than the moment you notice it's no longer enough. Use Lovable, Replit or Bolt to learn what users want quickly and spend little doing it. Once the app holds real data or real revenue, treat the generated code like code from any new contractor: review it, secure it and give it a structure someone can maintain.&lt;/p&gt;

&lt;p&gt;If you're at that point, I take AI-built apps from Lovable, Bolt and Replit and &lt;a href="https://muhammadmoiz.dev/services/ai-app-production-ready" rel="noopener noreferrer"&gt;make them production-ready&lt;/a&gt;, or start with a &lt;a href="https://muhammadmoiz.dev/services/production-audit" rel="noopener noreferrer"&gt;production audit&lt;/a&gt; if you just want to know where you stand.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://lovable.dev/pricing" rel="noopener noreferrer"&gt;Lovable pricing and FAQ&lt;/a&gt; (checked October 2026)&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://replit.com/pricing" rel="noopener noreferrer"&gt;Replit pricing&lt;/a&gt; (checked October 2026)&lt;/li&gt;
&lt;li&gt;&lt;a href="https://replit.com/products/agent" rel="noopener noreferrer"&gt;Replit Agent product page&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://bolt.new/pricing" rel="noopener noreferrer"&gt;Bolt pricing&lt;/a&gt; (checked October 2026)&lt;/li&gt;
&lt;li&gt;&lt;a href="https://bolt.new" rel="noopener noreferrer"&gt;Bolt homepage&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://cursor.com/pricing" rel="noopener noreferrer"&gt;Cursor pricing&lt;/a&gt; (checked October 2026)&lt;/li&gt;
&lt;li&gt;&lt;a href="https://cursor.com" rel="noopener noreferrer"&gt;Cursor homepage&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://vercel.com/docs/v0" rel="noopener noreferrer"&gt;Vercel v0 documentation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Cover photo: Mohammad Rahmani on Unsplash&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;I'm Muhammad Moiz, a full-stack developer who builds web apps, SaaS and POS systems, and takes AI-built apps (Lovable, Bolt, Replit) to production. &lt;a href="https://muhammadmoiz.dev/contact" rel="noopener noreferrer"&gt;Get in touch&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>webdev</category>
      <category>startup</category>
      <category>nocode</category>
    </item>
    <item>
      <title>PostgreSQL 19 Release Candidate: What Shipped, What Was Cut, How to Upgrade</title>
      <dc:creator>Muhammad Moiz</dc:creator>
      <pubDate>Thu, 29 Oct 2026 05:10:55 +0000</pubDate>
      <link>https://dev.to/muhammadmoiz269/postgresql-19-release-candidate-what-shipped-what-was-cut-how-to-upgrade-5foi</link>
      <guid>https://dev.to/muhammadmoiz269/postgresql-19-release-candidate-what-shipped-what-was-cut-how-to-upgrade-5foi</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://muhammadmoiz.dev/blog/postgresql-19-release-candidate-upgrade-guide" rel="noopener noreferrer"&gt;muhammadmoiz.dev&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;PostgreSQL 19 is not out yet. The first release candidate shipped on October 15, 2026, and the project now plans general availability for November 19, 2026, later than many teams expected. Several headline features announced in the June beta were pulled before the RC, so if you planned an upgrade around them, this guide covers what actually made the cut, what changes under your feet, and how to get ready.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where the release stands right now
&lt;/h2&gt;

&lt;p&gt;The PostgreSQL 19 timeline this year has been longer than usual. Here are the dates that matter, all from the project's own announcements:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Milestone&lt;/th&gt;
&lt;th&gt;Date&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Beta 1&lt;/td&gt;
&lt;td&gt;June 4, 2026&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Beta 4 (features removed)&lt;/td&gt;
&lt;td&gt;September 24, 2026&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Release Candidate 1&lt;/td&gt;
&lt;td&gt;October 15, 2026&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;RC 2 and minor updates for supported versions&lt;/td&gt;
&lt;td&gt;November 12, 2026 (planned)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;PostgreSQL 14 end of life&lt;/td&gt;
&lt;td&gt;November 12, 2026&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;PostgreSQL 19 general availability&lt;/td&gt;
&lt;td&gt;November 19, 2026 (planned)&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The RC 1 announcement explains that the release team chose to fold a large batch of fixes into version 19 before calling it final, which is why a second release candidate is on the calendar. The GA date can still move if a serious issue turns up.&lt;/p&gt;

&lt;p&gt;Why so many late fixes? According to a DEV Community write-up that collects the public discussion, long-time committer Peter Eisentraut wrote on October 9 that LLM-assisted code review was at least partly responsible for the wave of reverts, because it surfaced defects in already-committed features much faster than before. The same write-up notes that some community members pushed back, saying a large share of AI-reported bugs turned out not to be real. Either way, the practical result for you is the same: a smaller, more conservative release.&lt;/p&gt;

&lt;h2&gt;
  
  
  What was cut from PostgreSQL 19
&lt;/h2&gt;

&lt;p&gt;If you read the Beta 1 announcement and got excited, check this list before you plan anything. The official Beta 4 announcement says these were removed so they can be reconsidered for a later major version:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;SQL/PGQ property graph queries&lt;/strong&gt; (graph-style queries in standard SQL)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Turning data checksums on or off while the cluster is online&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Temporal &lt;code&gt;UPDATE&lt;/code&gt; and &lt;code&gt;DELETE&lt;/code&gt; using &lt;code&gt;FOR PORTION OF&lt;/code&gt;&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code&gt;ALTER TABLE ... MERGE PARTITIONS&lt;/code&gt; and &lt;code&gt;SPLIT PARTITIONS&lt;/code&gt;&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code&gt;pg_get_role_ddl()&lt;/code&gt;, &lt;code&gt;pg_get_tablespace_ddl()&lt;/code&gt; and &lt;code&gt;pg_get_database_ddl()&lt;/code&gt;&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;code&gt;GROUP BY ALL&lt;/code&gt;, which appeared in the Beta 1 highlights, is also missing from the current release notes. So if a blog post or tutorial shows any of these as "new in Postgres 19", treat it as outdated.&lt;/p&gt;

&lt;h2&gt;
  
  
  What did make it in
&lt;/h2&gt;

&lt;p&gt;The good news is that a lot of useful work survived. Based on the RC-era release notes, these are the changes most app developers will notice:&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%2Fimages.unsplash.com%2Fphoto-1762163516269-3c143e04175c%3Fw%3D1200%26q%3D80" 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%2Fimages.unsplash.com%2Fphoto-1762163516269-3c143e04175c%3Fw%3D1200%26q%3D80" alt="Server rack with rows of blinking green status lights" width="1200" height="795"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Photo: Domaintechnik on Unsplash&lt;/em&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  For application code
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;INSERT ... ON CONFLICT DO SELECT ... RETURNING&lt;/code&gt;.&lt;/strong&gt; An upsert can now hand back the row that already existed instead of silently skipping it. That removes a common "insert, and if nothing came back, run a second SELECT" round trip.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Faster foreign key checks.&lt;/strong&gt; The notes list a general performance improvement for foreign key constraint checks.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A &lt;code&gt;WAIT&lt;/code&gt; command for replicas.&lt;/strong&gt; A session on a standby can wait until a given WAL position has been written, flushed or replayed. That gives you read-your-writes behaviour when you send writes to the primary and reads to a replica.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;More &lt;code&gt;jsonpath&lt;/code&gt; string methods&lt;/strong&gt;, including &lt;code&gt;lower()&lt;/code&gt;, &lt;code&gt;upper()&lt;/code&gt;, &lt;code&gt;replace()&lt;/code&gt;, &lt;code&gt;split_part()&lt;/code&gt; and the trim family.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;COPY TO&lt;/code&gt; can output JSON&lt;/strong&gt;, with a &lt;code&gt;FORCE_ARRAY&lt;/code&gt; option to produce a single JSON array.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Smarter &lt;code&gt;NOTIFY&lt;/code&gt;&lt;/strong&gt;, which now wakes only the backends listening on the relevant channel. Apps that use &lt;code&gt;LISTEN&lt;/code&gt;/&lt;code&gt;NOTIFY&lt;/code&gt; for real-time features should see less overhead.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Here is the kind of upsert that gets simpler. This is an illustration, not code from the docs:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight sql"&gt;&lt;code&gt;&lt;span class="c1"&gt;-- Create a tag if it doesn't exist, and always get its row back&lt;/span&gt;
&lt;span class="k"&gt;INSERT&lt;/span&gt; &lt;span class="k"&gt;INTO&lt;/span&gt; &lt;span class="n"&gt;tags&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;name&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="k"&gt;VALUES&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s1"&gt;'billing'&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="k"&gt;ON&lt;/span&gt; &lt;span class="n"&gt;CONFLICT&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;name&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;DO&lt;/span&gt; &lt;span class="k"&gt;SELECT&lt;/span&gt;
&lt;span class="n"&gt;RETURNING&lt;/span&gt; &lt;span class="n"&gt;id&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;name&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  For operations
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;REPACK&lt;/code&gt;&lt;/strong&gt;, a built-in way to rebuild bloated tables, with a &lt;code&gt;CONCURRENTLY&lt;/code&gt; option that avoids blocking reads and writes. It shipped with a narrower scope than first planned, and it received many crash and correctness fixes during the betas, so test it on a copy first.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Parallel autovacuum&lt;/strong&gt; via &lt;code&gt;autovacuum_max_parallel_workers&lt;/code&gt;, plus a new scoring system for deciding which tables to vacuum first.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Automatic I/O worker scaling&lt;/strong&gt; between the new &lt;code&gt;io_min_workers&lt;/code&gt; and &lt;code&gt;io_max_workers&lt;/code&gt; settings.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;pg_plan_advice&lt;/code&gt; and &lt;code&gt;pg_stash_advice&lt;/code&gt;&lt;/strong&gt;, new modules for steering and pinning planner decisions.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Logical replication of sequences&lt;/strong&gt;, which makes replication-based online upgrades less fiddly.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;TLS SNI support&lt;/strong&gt; through a new &lt;code&gt;pg_hosts.conf&lt;/code&gt; file, so one server can present different certificates per hostname.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Breaking changes to check before upgrading
&lt;/h2&gt;

&lt;p&gt;This is the section to read twice. These items come from the migration section and other behaviour changes in the release notes:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;JIT is off by default.&lt;/strong&gt; If you have analytical queries that benefited from JIT compilation, benchmark them and turn it back on explicitly if needed.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;RADIUS authentication is gone.&lt;/strong&gt; The notes describe the UDP-only implementation as unfixably insecure. Move to another method before upgrading.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;MD5 password logins now trigger a warning&lt;/strong&gt; after successful authentication (controlled by &lt;code&gt;md5_password_warnings&lt;/code&gt;). It's a nudge to switch to SCRAM.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;standard_conforming_strings&lt;/code&gt; is always on.&lt;/strong&gt; Dumps taken from older versions with this setting off will not load correctly into 19.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;max_locks_per_transaction&lt;/code&gt; defaults to 128 instead of 64&lt;/strong&gt;, and lock sizing changed. If you tuned this value, the notes say you effectively need to double it to keep the same capacity.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;json_array()&lt;/code&gt; returns an empty array instead of NULL&lt;/strong&gt; when there are no rows. Check any code that tests for NULL here.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Default TOAST compression is now &lt;code&gt;lz4&lt;/code&gt;&lt;/strong&gt; rather than &lt;code&gt;pglz&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;vacuumdb --analyze-only&lt;/code&gt; now includes partitioned tables&lt;/strong&gt; when no targets are given.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;A quick way to spot settings that matter on your current server:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight sql"&gt;&lt;code&gt;&lt;span class="k"&gt;SELECT&lt;/span&gt; &lt;span class="n"&gt;name&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;setting&lt;/span&gt;
&lt;span class="k"&gt;FROM&lt;/span&gt; &lt;span class="n"&gt;pg_settings&lt;/span&gt;
&lt;span class="k"&gt;WHERE&lt;/span&gt; &lt;span class="n"&gt;name&lt;/span&gt; &lt;span class="k"&gt;IN&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;
  &lt;span class="s1"&gt;'jit'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="s1"&gt;'standard_conforming_strings'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="s1"&gt;'max_locks_per_transaction'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="s1"&gt;'password_encryption'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="s1"&gt;'default_toast_compression'&lt;/span&gt;
&lt;span class="p"&gt;);&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;And to find roles still using MD5 password hashes (run as a superuser):&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight sql"&gt;&lt;code&gt;&lt;span class="k"&gt;SELECT&lt;/span&gt; &lt;span class="n"&gt;rolname&lt;/span&gt;
&lt;span class="k"&gt;FROM&lt;/span&gt; &lt;span class="n"&gt;pg_authid&lt;/span&gt;
&lt;span class="k"&gt;WHERE&lt;/span&gt; &lt;span class="n"&gt;rolpassword&lt;/span&gt; &lt;span class="k"&gt;LIKE&lt;/span&gt; &lt;span class="s1"&gt;'md5%'&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  A practical upgrade checklist
&lt;/h2&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Don't run an RC in production:&lt;/strong&gt; A release candidate is for testing. Wait for the final 19.0 release, and for most teams, for the first minor release after it, before moving production data.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Know your current version.&lt;/strong&gt; Run &lt;code&gt;SELECT version();&lt;/code&gt;. If you're on PostgreSQL 14, that matters more than 19: version 14 stops getting fixes on November 12, 2026. Plan to move to 17 or 18 now, or straight to 19 once it's stable.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Check your provider.&lt;/strong&gt; Managed services (RDS, Cloud SQL, Supabase, Neon and others) adopt new majors on their own schedules. Look up when they will offer 19 rather than assuming it will be there on day one.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Spin up the RC in a container&lt;/strong&gt; and restore a recent copy of your database into it. Run your test suite and your slowest real queries.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Work through the breaking-change list above&lt;/strong&gt;, especially MD5, RADIUS and &lt;code&gt;standard_conforming_strings&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Pick an upgrade method.&lt;/strong&gt; The project recommends a major-version approach such as &lt;code&gt;pg_upgrade&lt;/code&gt; (fast, in place) or &lt;code&gt;pg_dump&lt;/code&gt; / &lt;code&gt;pg_restore&lt;/code&gt; (slower, cleaner). Logical replication is another option if you need minimal downtime.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Run &lt;code&gt;pg_upgrade --check&lt;/code&gt; first&lt;/strong&gt; against a copy. It reports incompatibilities without changing anything.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Update drivers and ORMs&lt;/strong&gt; (node-postgres, Prisma, Drizzle, psycopg and so on) in staging, then confirm migrations still run.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Have a rollback plan&lt;/strong&gt;: a verified backup and a tested restore, not just a backup.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  What this means for business and app owners
&lt;/h2&gt;

&lt;p&gt;If you run a SaaS product, an e-commerce store or an internal tool on Postgres, PostgreSQL 19 is not urgent. Nothing in it is a security fix you must rush to apply, and the most eye-catching features were deferred. The more pressing date is November 12: if your database is on version 14, it will stop receiving security patches that day.&lt;/p&gt;

&lt;p&gt;A sensible plan for most teams looks like this: get off 14 this quarter, test 19 in staging once it hits GA, and schedule the production upgrade for early 2027 after the first point release. The features that did ship, like &lt;code&gt;ON CONFLICT DO SELECT&lt;/code&gt;, replica &lt;code&gt;WAIT&lt;/code&gt; and faster foreign key checks, are real quality-of-life wins worth adopting once you're there.&lt;/p&gt;

&lt;p&gt;If your app was built quickly, perhaps with an AI builder, and nobody is sure which Postgres version it runs, which auth method it uses, or whether backups restore, that's worth finding out before any upgrade. A &lt;a href="https://muhammadmoiz.dev/services/production-audit" rel="noopener noreferrer"&gt;production audit&lt;/a&gt; covers exactly those questions, and if you need help planning a database move as part of backend work, &lt;a href="https://muhammadmoiz.dev/contact" rel="noopener noreferrer"&gt;get in touch&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.postgresql.org/about/news/postgresql-19-rc-1-released-3409/" rel="noopener noreferrer"&gt;PostgreSQL 19 RC 1 Released (postgresql.org)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.postgresql.org/about/news/postgresql-19-beta-4-released-3386/" rel="noopener noreferrer"&gt;PostgreSQL 19 Beta 4 Released (postgresql.org)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.postgresql.org/about/news/postgresql-19-beta-1-released-3313/" rel="noopener noreferrer"&gt;PostgreSQL 19 Beta 1 Released (postgresql.org)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.postgresql.org/docs/19/release-19.html" rel="noopener noreferrer"&gt;PostgreSQL 19 release notes (RC documentation)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.postgresql.org/support/versioning/" rel="noopener noreferrer"&gt;PostgreSQL versioning policy&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://dev.to/alanwest/postgresql-19-release-date-moved-to-nov-19-after-ai-review-found-too-many-bugs-48n"&gt;PostgreSQL 19 Release Date Moved to Nov 19 After AI Review Found Too Many Bugs (DEV Community)&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;Cover photo: Taylor Vick on Unsplash&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;I'm Muhammad Moiz, a full-stack developer who builds web apps, SaaS and POS systems, and takes AI-built apps (Lovable, Bolt, Replit) to production. &lt;a href="https://muhammadmoiz.dev/contact" rel="noopener noreferrer"&gt;Get in touch&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>postgres</category>
      <category>database</category>
      <category>webdev</category>
      <category>devops</category>
    </item>
    <item>
      <title>Offline-First POS: Lessons From Building Oscar in React</title>
      <dc:creator>Muhammad Moiz</dc:creator>
      <pubDate>Wed, 28 Oct 2026 07:07:55 +0000</pubDate>
      <link>https://dev.to/muhammadmoiz269/offline-first-pos-lessons-from-building-oscar-in-react-284l</link>
      <guid>https://dev.to/muhammadmoiz269/offline-first-pos-lessons-from-building-oscar-in-react-284l</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published at &lt;a href="https://muhammadmoiz.dev/blog/offline-first-pos-react" rel="noopener noreferrer"&gt;muhammadmoiz.dev&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;A point of sale system has one job that matters more than any feature: it must keep selling. On a busy Friday night a restaurant can't tell a queue of customers to wait until the Wi-Fi comes back.&lt;/p&gt;

&lt;p&gt;When I worked on Oscar, a POS for restaurants and retail businesses in Pakistan, "works offline" wasn't a nice-to-have. It shaped the whole architecture. Here's how an offline-first POS works in the browser, and the lessons I'd pass on to any founder planning one.&lt;/p&gt;

&lt;h2&gt;
  
  
  What "offline-first" actually means
&lt;/h2&gt;

&lt;p&gt;Many apps say they "work offline" when they really mean they show a friendly error. Offline-first flips the usual design:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;The app reads and writes a local database first.&lt;/strong&gt; The screen never waits for the server.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The server is updated in the background&lt;/strong&gt; whenever a connection is available.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The cloud stays the source of truth for reporting,&lt;/strong&gt; so owners still see every branch's sales in one place.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For a cashier, the result is simple: punching an order, taking payment and printing a receipt behave exactly the same with or without internet.&lt;/p&gt;

&lt;h2&gt;
  
  
  The architecture in one picture
&lt;/h2&gt;

&lt;p&gt;The React app reads and writes a local database in the browser, so it works offline. When a connection is available, a sync process sends local changes to the backend, which updates the main database used for reporting.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;React POS app ↔ Local database: Read / write&lt;/li&gt;
&lt;li&gt;Local database ↔ Backend API: Sync when online&lt;/li&gt;
&lt;li&gt;Backend API → Main database&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;On Oscar, the local database was &lt;strong&gt;WatermelonDB&lt;/strong&gt; running on browser storage, so there was no app to install. The backend received the synced changes and mapped them to the main database.&lt;/p&gt;

&lt;h2&gt;
  
  
  Lesson 1: design the data before the screens
&lt;/h2&gt;

&lt;p&gt;With a normal web app you can sketch the UI first and add API calls later. Offline-first doesn't forgive that. Every feature started with &lt;strong&gt;data modelling&lt;/strong&gt;: the tables, the relations between them, and the functions that create, update and query records.&lt;/p&gt;

&lt;p&gt;An order, for example, isn't one row. It has items, modifiers, discounts and payments, and all of them must be created locally, in one go, without asking the server for IDs. Here's a simplified model to show the idea:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight typescript"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;Model&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;@nozbe/watermelondb&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;children&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;field&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;date&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;@nozbe/watermelondb/decorators&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="kd"&gt;class&lt;/span&gt; &lt;span class="nc"&gt;Order&lt;/span&gt; &lt;span class="kd"&gt;extends&lt;/span&gt; &lt;span class="nc"&gt;Model&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="k"&gt;static&lt;/span&gt; &lt;span class="nx"&gt;table&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;orders&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="k"&gt;static&lt;/span&gt; &lt;span class="nx"&gt;associations&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="na"&gt;order_items&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;type&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;has_many&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="na"&gt;foreignKey&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;order_id&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt; &lt;span class="p"&gt;},&lt;/span&gt;
    &lt;span class="na"&gt;payments&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;type&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;has_many&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="na"&gt;foreignKey&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;order_id&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt; &lt;span class="p"&gt;},&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="kd"&gt;as const&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

  &lt;span class="p"&gt;@&lt;/span&gt;&lt;span class="nd"&gt;field&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;type&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="kd"&gt;type&lt;/span&gt;&lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;dine_in&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt; &lt;span class="o"&gt;|&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;takeaway&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt; &lt;span class="o"&gt;|&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;delivery&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="p"&gt;@&lt;/span&gt;&lt;span class="nd"&gt;field&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;status&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="nx"&gt;status&lt;/span&gt;&lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kr"&gt;string&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="p"&gt;@&lt;/span&gt;&lt;span class="nd"&gt;date&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;created_at&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="nx"&gt;createdAt&lt;/span&gt;&lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nb"&gt;Date&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="p"&gt;@&lt;/span&gt;&lt;span class="nd"&gt;children&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;order_items&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="nx"&gt;items&lt;/span&gt;&lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;unknown&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="p"&gt;@&lt;/span&gt;&lt;span class="nd"&gt;children&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;payments&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="nx"&gt;payments&lt;/span&gt;&lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;unknown&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If the data model is right, the screens are easy. If it's wrong, every new feature fights the sync.&lt;/p&gt;

&lt;h2&gt;
  
  
  Lesson 2: sync is a product feature, not a background detail
&lt;/h2&gt;

&lt;p&gt;The hardest bugs in offline apps aren't on the screen. They're in the sync: an order that arrives twice, a discount that disappears, two devices editing the same table. What helps:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Every record is created with its own unique ID on the device,&lt;/strong&gt; so the server never has to invent one and duplicates are easy to detect.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Changes sync as a batch,&lt;/strong&gt; so a half-sent order never shows up in reports.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The backend owns the rules for conflicts.&lt;/strong&gt; When two devices change the same thing, one place decides, the same way every time.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Lesson 3: real-time and offline can live together
&lt;/h2&gt;

&lt;p&gt;Kitchens want orders the moment they're punched. On Oscar, orders reached the &lt;strong&gt;Kitchen Display System over WebSockets&lt;/strong&gt;, and prints went to the right printer (receipt, kitchen or bar) through &lt;strong&gt;QZ Tray&lt;/strong&gt;. Each real-time feature needs its own answer to "what happens offline?", decided at design time, not after the first outage.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;For founders:&lt;/strong&gt; If your product is used at a counter, in a warehouse or on the road, ask early: "What happens when the internet drops?" Adding offline support later usually means rebuilding the data layer.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  Lesson 4: test the bad days, not the good ones
&lt;/h2&gt;

&lt;p&gt;An offline-first app needs testing in the conditions it was built for:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Turn the network off in the middle of an order, then back on.&lt;/li&gt;
&lt;li&gt;Punch orders on two devices while one is offline.&lt;/li&gt;
&lt;li&gt;Close the browser before a sync finishes and reopen it.&lt;/li&gt;
&lt;li&gt;Fill the local database with a busy week of orders and check the app is still fast.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;These tests find the problems that real customers would otherwise find for you.&lt;/p&gt;

&lt;h2&gt;
  
  
  Is offline-first right for your product?
&lt;/h2&gt;

&lt;p&gt;It adds real work, so it's worth it when people &lt;strong&gt;must keep working without a connection&lt;/strong&gt;: POS systems, field-service apps, inventory and delivery tools. For a typical SaaS dashboard used at a desk, a well-built online app with good error handling is usually enough.&lt;/p&gt;

&lt;p&gt;If you're planning a POS or another app that has to keep working when the internet doesn't, you can read how I built Oscar in the &lt;a href="https://muhammadmoiz.dev/work/oscar-pos" rel="noopener noreferrer"&gt;case study&lt;/a&gt;, or &lt;a href="https://muhammadmoiz.dev/contact" rel="noopener noreferrer"&gt;tell me about your project&lt;/a&gt;.&lt;/p&gt;




&lt;p&gt;I'm Muhammad Moiz, a full-stack developer who builds web apps, SaaS and POS systems, and takes AI-built apps (Lovable, Bolt, Replit) to production. &lt;a href="https://muhammadmoiz.dev/contact" rel="noopener noreferrer"&gt;Get in touch&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>react</category>
      <category>pwa</category>
      <category>webdev</category>
      <category>javascript</category>
    </item>
  </channel>
</rss>
