<?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: Israr Kundi</title>
    <description>The latest articles on DEV Community by Israr Kundi (@israr-kundi).</description>
    <link>https://dev.to/israr-kundi</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%2F4217013%2F8b3b8ba5-7e95-4203-b2f5-11cb4448dcd2.png</url>
      <title>DEV Community: Israr Kundi</title>
      <link>https://dev.to/israr-kundi</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/israr-kundi"/>
    <language>en</language>
    <item>
      <title>Lovable Credits Ran Out? Why Your Live App Stopped Working</title>
      <dc:creator>Israr Kundi</dc:creator>
      <pubDate>Tue, 17 Nov 2026 06:02:26 +0000</pubDate>
      <link>https://dev.to/israr-kundi/lovable-credits-ran-out-why-your-live-app-stopped-working-56n1</link>
      <guid>https://dev.to/israr-kundi/lovable-credits-ran-out-why-your-live-app-stopped-working-56n1</guid>
      <description>&lt;p&gt;Lovable credits ran out is the first thing to check when your Lovable app breaks and you changed nothing. One credit balance pays for building your app and for running it, so when that balance hits zero, parts of your live app stop working — while the pages themselves stay up.&lt;/p&gt;

&lt;h2&gt;
  
  
  The problem: "I changed nothing, and the app broke"
&lt;/h2&gt;

&lt;p&gt;Your homepage still loads. But the AI chat feature returns an error or nothing at all. Login stops working. Data will not load. Nothing was edited, nothing was published, and the app worked yesterday.&lt;/p&gt;

&lt;p&gt;That mix — pages up, features dead — is the signature of an empty credit balance. Lovable's own docs say AI features in deployed apps fail with an error when the credits run out, and Lovable shows no message for the failed calls themselves. Your visitors see a broken product, not an offline one, and you get no clear error pointing at the cause.&lt;/p&gt;

&lt;h2&gt;
  
  
  The cause: one balance pays for building and running
&lt;/h2&gt;

&lt;p&gt;Since June 2026, Lovable has run on a single credit balance. Building in the editor, the built-in backend (Lovable Cloud), AI features inside your published app, and managed connectors all draw from the same pool. Before that, build credits and the Cloud and AI balances were separate pots.&lt;/p&gt;

&lt;p&gt;Each month starts with small grants — 20 credits for Cloud usage and 4 for AI usage — and then your general credits pay for the rest, closest to expiry first. The part that catches people out is that visitors spend your credits too. Every AI call and every database read in the live app draws from the same balance you build with. A busy week can drain it even if you barely touched the editor.&lt;/p&gt;

&lt;p&gt;When the balance hits zero, Lovable's docs list what stops:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Building stops, and work in progress pauses.&lt;/li&gt;
&lt;li&gt;AI features in your deployed app stop working.&lt;/li&gt;
&lt;li&gt;The built-in backend pauses: database, storage, and authentication. Your data stays safe, but you cannot access or export it until the services run again.&lt;/li&gt;
&lt;li&gt;Your published pages keep serving, and chat keeps working while the daily chat allowance lasts.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Lovable does warn you first. Workspace admins and owners get an email when credits are likely to run out before the monthly refill, showing the expected run-out date and the refill date, plus banners on the Plans &amp;amp; credit usage page and the Database, Users, and Storage views. But the email goes only to admins and owners, and it is easy to miss one email among many.&lt;/p&gt;

&lt;h2&gt;
  
  
  The minimum fix: Lovable credits ran out
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Check the balance first. Go to Workspace settings, then Plans &amp;amp; credit usage. Look for the out-of-credits banner and the expected run-out and refill dates. If the balance is zero, you have found the cause.&lt;/li&gt;
&lt;li&gt;Add credits. On Pro and Business, a workspace admin or owner can buy top-up credits. On the Free plan, daily build credits refill each day, or upgrade to a paid plan.&lt;/li&gt;
&lt;li&gt;Resume what paused. Select Resume on any paused build work, and Wake up on the paused backend. AI features in your app start working again within a few seconds once credits are available.&lt;/li&gt;
&lt;li&gt;Test the live app yourself. Try the AI feature and the login before you tell users it is fixed. The pages loading does not prove the features work.&lt;/li&gt;
&lt;li&gt;Stop it happening again. On paid plans, set usage limits that warn you or block further spend when a threshold is reached. Turn on auto top-up if the app serves real users. Check the usage dashboard once a week — it breaks spend down by project, and by building versus running the app.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;What NOT to do: do not rebuild or republish the app. The code is not broken, and republishing spends more credits. Do not keep asking the chat to fix it either — each message spends credits from the same empty balance. And do not take "the site loads" as proof the app works. Static pages stay up at zero credits; the features behind them do not.&lt;/p&gt;

&lt;h2&gt;
  
  
  When to get help instead of fixing it yourself
&lt;/h2&gt;

&lt;p&gt;Get help when the balance looks fine and the app still fails — then the cause is somewhere else, and guessing costs more credits. Get help too when credits drain faster than you can explain, or when the app serves paying customers and this has happened more than once. A developer can trace which project and which feature is eating the balance, add error messages so users see something useful instead of a silent failure, or move the backend and AI calls somewhere they are billed on their own.&lt;/p&gt;

&lt;p&gt;If this is your app, contact me through &lt;a href="https://israr-kundi.web.app" rel="noopener noreferrer"&gt;https://israr-kundi.web.app&lt;/a&gt;&lt;/p&gt;

</description>
      <category>lovable</category>
      <category>ai</category>
      <category>webdev</category>
      <category>debugging</category>
    </item>
    <item>
      <title>Why Apple Rejects Apps in 2026 — and How to Fix It</title>
      <dc:creator>Israr Kundi</dc:creator>
      <pubDate>Mon, 16 Nov 2026 04:58:05 +0000</pubDate>
      <link>https://dev.to/israr-kundi/why-apple-rejects-apps-in-2026-and-how-to-fix-it-3951</link>
      <guid>https://dev.to/israr-kundi/why-apple-rejects-apps-in-2026-and-how-to-fix-it-3951</guid>
      <description>&lt;p&gt;Why Apple rejects apps in 2026 is a question with a plain answer: Apple turned down 2,093,244 of the 9,100,620 app submissions it reviewed in 2025, about 23%, according to its App Store Transparency Report, published in May 2026. Before you submit, check three things: the app must work end to end, the privacy forms must match what the app does, and the app must do more than show a website in a frame.&lt;/p&gt;

&lt;h2&gt;
  
  
  The problem: "My app was rejected, and I don't know why"
&lt;/h2&gt;

&lt;p&gt;The rejection names a guideline number and a short reason. One developer who posted on the Apple Developer Forums in March 2026 got this line: "The usefulness of the app is limited by the minimal functionality it currently provides."&lt;/p&gt;

&lt;p&gt;That is Guideline 4.2, Minimum Functionality. The rule does not mention how the app was built. It rejects apps that add nothing to what a browser already does. Rejection is common, and it is not the end: in the same report, 387,087 submissions were approved after an earlier rejection. The fix is to read the exact reason, change the app, and tell the reviewer what changed.&lt;/p&gt;

&lt;h2&gt;
  
  
  The cause: three things to check
&lt;/h2&gt;

&lt;p&gt;One submission can break more than one rule, so the section numbers below add up to more than the 2,093,244 rejected submissions.&lt;/p&gt;

&lt;p&gt;First, Guideline 2.1, App Completeness. Over 40% of unresolved review issues relate to 2.1. The app crashes, a screen still has placeholder text, or the reviewer cannot sign in because no demo account was given. Performance, the section that holds 2.1, recorded 1,354,418 rejections in 2025 — more than any other section.&lt;/p&gt;

&lt;p&gt;Second, Guideline 4.2. The rule says an app "should include features, content, and UI that elevate it beyond a repackaged website." A web view with your site's own menu and footer adds nothing to what Safari already does. Apple's own App Review page puts it plainly: "Websites served in an iOS app, web content that is not formatted for iOS, and limited web interactions do not make a quality app." Two nearby rules cover similar ground: 4.2.2 rejects apps that are mostly marketing material, adverts, or a collection of links, and 4.2.6 rejects apps made with a template or app generation service unless the provider of the content submits them. Design recorded 415,532 rejections in 2025.&lt;/p&gt;

&lt;p&gt;Third, privacy and age rules that moved in 2026. Apple revised its App Review Guidelines three times in 2026 — 6 February, 8 June, and 16 October. If your app sends personal data to a third-party AI service, Guideline 5.1.2(i) asks you to say so clearly and get the user's permission first. The social-media question was added to the age-rating questionnaire on 9 July 2026 and became mandatory from September 2026. In March 2026, Apple also blocked updates to the vibe-coding tools Replit and Vibecode, because apps may not download or run new code after review (Guideline 2.5.2).&lt;/p&gt;

&lt;h2&gt;
  
  
  The minimum fix: why Apple rejects apps in 2026
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Read the rejection message and copy the exact guideline number. The sub-number tells you which problem to solve: 2.1 is completeness, 4.2 is minimum functionality.&lt;/li&gt;
&lt;li&gt;Fix 2.1 first. Run the release build on a real phone, not only in the preview. Tap every button, fill every form, and remove placeholder text. If the app has a login, create a demo account and put its details in the review notes.&lt;/li&gt;
&lt;li&gt;For a 4.2 rejection, give the app a job only a phone can do. Add native tab navigation for the things people do most. Add push notifications that open the right screen when tapped. Add one device feature that fits the app, such as camera upload or the share sheet. Add an offline screen, so losing signal does not show a blank page.&lt;/li&gt;
&lt;li&gt;Check the privacy forms. Make sure the App Privacy details in App Store Connect match what the app actually collects. If the app sends personal data to a third-party AI service, add a clear permission screen before the first request. Answer the age-rating questions honestly, including the social media question.&lt;/li&gt;
&lt;li&gt;Submit from your own Apple developer account. Under 4.2.6, an app built by a template or generation service is rejected unless the content provider submits it.&lt;/li&gt;
&lt;li&gt;Reply in App Store Connect and list exactly what changed, for example: "Added native tab navigation, push notifications, camera upload, and an offline screen." Then upload a new build. Apple reviews 90% of submissions in under 48 hours.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;What NOT to do: do not resubmit the same build with no changes. Do not change only the icon or the splash screen. Do not appeal first: you get one appeal per rejected submission, to the App Review Board.&lt;/p&gt;

&lt;h2&gt;
  
  
  When to get help instead of fixing it yourself
&lt;/h2&gt;

&lt;p&gt;If the app is a website in a wrapper and the fix needs a real native build, that is a rebuild, not a tweak. Get a developer to do it when the rejection mentions 4.2 and the app has no native features at all, or when two rounds of fixes have come back with the same answer.&lt;/p&gt;

&lt;p&gt;If this is your app, contact me through &lt;a href="https://israr-kundi.web.app" rel="noopener noreferrer"&gt;https://israr-kundi.web.app&lt;/a&gt;&lt;/p&gt;

</description>
      <category>flutter</category>
      <category>ios</category>
      <category>appstore</category>
      <category>publishing</category>
    </item>
    <item>
      <title>Which Backend Should You Choose for Your Mobile App?</title>
      <dc:creator>Israr Kundi</dc:creator>
      <pubDate>Fri, 13 Nov 2026 05:02:38 +0000</pubDate>
      <link>https://dev.to/israr-kundi/which-backend-should-you-choose-for-your-mobile-app-2kll</link>
      <guid>https://dev.to/israr-kundi/which-backend-should-you-choose-for-your-mobile-app-2kll</guid>
      <description>&lt;p&gt;Which backend should you choose for your mobile app? Firebase and Supabase are the two backends this article compares, and they store data in different ways.&lt;/p&gt;

&lt;h2&gt;
  
  
  The problem: "I just need a backend, why is this so hard?"
&lt;/h2&gt;

&lt;p&gt;You have an app idea. The guides you find name Firebase or Supabase, and they disagree with each other. One comparison says Firebase is cheaper, the next says Supabase is, and each one sounds sure.&lt;/p&gt;

&lt;p&gt;So you pick the one you heard first. Then your app grows, and the backend fights you: reports need data from three places at once, the app stops working offline, or the monthly bill jumps for no clear reason.&lt;/p&gt;

&lt;h2&gt;
  
  
  The cause: the two backends store data in different ways
&lt;/h2&gt;

&lt;p&gt;Firebase stores your data as documents. Think of each document as one card — one card per order, one card per user. That works when each screen reads one card.&lt;/p&gt;

&lt;p&gt;Supabase stores your data in tables, the way a spreadsheet does, on PostgreSQL. You write SQL queries that join tables together. One query can join orders to customers and products and add up the total.&lt;/p&gt;

&lt;p&gt;That difference is where the choice starts. If your app needs reports, an admin dashboard, or unplanned questions, SQL answers them with a new query. With documents, teams copy the fields each screen needs into each document, then update every copy when the source changes.&lt;/p&gt;

&lt;p&gt;There are two more differences that matter on a phone. First, offline use. Firestore keeps a copy of the data on the phone, so the app can read and write offline, and Google turns this on by default for Android and Apple apps. Supabase has no built-in offline cache — you add a sync layer such as PowerSync. If yours is a field service or delivery app that must work in a dead zone, that gap alone can decide for Firestore.&lt;/p&gt;

&lt;p&gt;Second, push notifications. Firebase includes Cloud Messaging, and it costs nothing on any Firebase plan. Supabase has no push service of its own. Its own guide sends push from Edge Functions through Firebase Cloud Messaging.&lt;/p&gt;

&lt;h2&gt;
  
  
  The minimum fix: which backend should you choose for your mobile app
&lt;/h2&gt;

&lt;h3&gt;
  
  
  1. Pick Supabase when your data is linked together
&lt;/h3&gt;

&lt;p&gt;Go with Supabase when your app has orders, customers, products and payments that relate to each other, when you want SQL and row level security, and when you want a way out to plain PostgreSQL later. Supabase is open source, and a standard Postgres dump restores anywhere.&lt;/p&gt;

&lt;p&gt;Watch one thing: a Supabase table without row level security switched on is readable and writable by any role with a grant on it. Since 30 October 2026, new tables in the public schema are not exposed to the data API at all until you add an explicit grant. Turn RLS on and write a row level security policy for every exposed table before real users arrive.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Firebase, when the phone must work offline
&lt;/h3&gt;

&lt;p&gt;Firebase is the pick when the app must keep working with no signal, when each screen reads one self-contained document, and when you want the database, push notifications and crash reports in one Google project. It also fits chat apps and anything that needs live updates.&lt;/p&gt;

&lt;p&gt;One catch: Firestore bills every document read, write and delete. Every query costs at least one read, even when it returns nothing. There is no hard cap — budgets and alerts do not stop usage. So read only the documents the screen shows, and never load a whole collection to show ten items.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Check the bill at your size, not at zero users
&lt;/h3&gt;

&lt;p&gt;Both start free. Supabase free covers 50,000 monthly users and a 500 MB database, but a free project pauses after one week idle. Its Pro plan is $25 a month and covers 100,000 monthly users and 8 GB of disk.&lt;/p&gt;

&lt;p&gt;Firebase Spark is free with no payment method: 1 GiB stored, 50,000 reads, 20,000 writes and 20,000 deletes a day. Past that you move to Blaze, which is pay-as-you-go per operation.&lt;/p&gt;

&lt;p&gt;In one cost model read on 2 November 2026, at 100,000 monthly users and 1,000 reads per user a month, the two came out close: about $100 a month on Supabase Pro and about $95 on Firebase with basic sign-in. Add multi-factor sign-in on Firebase and the same model put Firebase at about $370, because that needs the Identity Platform upgrade. Supabase includes basic multi-factor sign-in on every plan.&lt;/p&gt;

&lt;p&gt;What NOT to do: do not pick a backend because an AI tool defaults to it, and do not pick a custom backend for your first version. Start on Firebase or Supabase, and move only when you can name what the managed backend cannot do.&lt;/p&gt;

&lt;h2&gt;
  
  
  When to get help instead of choosing it yourself
&lt;/h2&gt;

&lt;p&gt;When your app takes payments or stores customer data, get a developer to plan the backend with you before you build. This is a choice that gets expensive to reverse once users sign up. My starting price for a small 4–5 screen app with Supabase is from $300.&lt;/p&gt;

&lt;p&gt;If this is your app, contact me through &lt;a href="https://israr-kundi.web.app" rel="noopener noreferrer"&gt;https://israr-kundi.web.app&lt;/a&gt;&lt;/p&gt;

</description>
      <category>flutter</category>
      <category>mobile</category>
      <category>backend</category>
      <category>supabase</category>
    </item>
    <item>
      <title>How to Convert Your Website into a Mobile App</title>
      <dc:creator>Israr Kundi</dc:creator>
      <pubDate>Thu, 12 Nov 2026 05:05:26 +0000</pubDate>
      <link>https://dev.to/israr-kundi/how-to-convert-your-website-into-a-mobile-app-5640</link>
      <guid>https://dev.to/israr-kundi/how-to-convert-your-website-into-a-mobile-app-5640</guid>
      <description>&lt;p&gt;How to convert your website into a mobile app? You have three routes: a progressive web app, a WebView wrapper, or a real rebuild — and the plain wrapper is the one most likely to be rejected.&lt;/p&gt;

&lt;h2&gt;
  
  
  The problem: "I already have a website, I just want it as an app"
&lt;/h2&gt;

&lt;p&gt;You run a shop or a small business. Your website already works, and customers keep asking for an app. Online tools promise to turn your site into an app.&lt;/p&gt;

&lt;p&gt;So you pay and submit the app. Then a rejection can arrive, naming Apple's Guideline 4.2.&lt;/p&gt;

&lt;h2&gt;
  
  
  The cause: the stores want an app, not a bookmark
&lt;/h2&gt;

&lt;p&gt;Apple's App Review Guidelines, updated in October 2026, open Guideline 4.2 with this sentence: "Your app should include features, content, and UI that elevate it beyond a repackaged website." An app that is not particularly useful, unique, or "app-like" does not belong on the App Store.&lt;/p&gt;

&lt;p&gt;Two smaller rules catch wrappers too. Rule 4.2.2 says apps should not be mainly marketing material, adverts, web clippings, content aggregators, or a collection of links — unless they are catalogues. Rule 4.2.6 says apps made with a commercial template or app generation service will be rejected unless the provider of the app's content submits them. So submit under your own Apple Developer account, not the converter's.&lt;/p&gt;

&lt;p&gt;Google Play's rules read differently. Its Spam policy does not allow apps whose primary purpose is to "drive affiliate traffic to a website or provide a webview of a website without permission from the website owner or administrator" — owning the site covers that part. Its Functionality policy is the harder one: apps that "do not have the basic degree of adequate utility as mobile apps" are not allowed.&lt;/p&gt;

&lt;p&gt;WebViews themselves are not banned: plenty of approved apps show some screens in one. The problem is an app that is only the same website a user could open in Safari.&lt;/p&gt;

&lt;p&gt;One more rule: since 31 August 2026, new apps and updates on Google Play must target Android 16 (API level 36) or higher.&lt;/p&gt;

&lt;h2&gt;
  
  
  The minimum fix: how to convert your website into a mobile app the stores accept
&lt;/h2&gt;

&lt;h3&gt;
  
  
  1. List what the app must do that the website cannot
&lt;/h3&gt;

&lt;p&gt;Push notifications, offline access, camera upload, barcode scanning, fingerprint login, saved items. If the list is empty, you do not need a store app yet — a bookmark or a progressive web app does the same job with no store fee and no review.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Pick one of the three routes
&lt;/h3&gt;

&lt;p&gt;Start light: a progressive web app installs from your website, works offline, and skips store review. It cannot be listed on the App Store, but Android lists it in Google Play through a Trusted Web Activity.&lt;/p&gt;

&lt;p&gt;The middle route is a WebView wrapper, loading your site inside a thin app shell. It is quick to build, and it stands a better chance with real app features added — push, offline support, native navigation, device features, native screens for the main tasks — though neither store publishes a checklist for passing. Budget for one or two review rounds.&lt;/p&gt;

&lt;p&gt;Choose a rebuild in Flutter for the third route: one codebase, real apps on iOS and Android, native screens from the start. A rebuild is built as an app from the start. Pick it when customers will open the app weekly or daily for a core task, like ordering or booking. My starting price for a small 4–5 screen app with Supabase is from $300; publishing to one store is $100.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. If you keep the wrapper, add app-only features before you submit
&lt;/h3&gt;

&lt;p&gt;Add a native tab bar and keep web content to single screens. Add push notifications and a usable offline screen. Keep login signed in, and make file upload work inside the app. In your App Review notes, name the features only the app has, and give reviewers a demo account.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. Submit under your own accounts, with the current targets
&lt;/h3&gt;

&lt;p&gt;Apple charges $99 a year for its Developer Program, Google a $25 one-time registration fee, for any app listed in the stores. Publish under your own accounts, and check the build targets Android 16 for Google Play.&lt;/p&gt;

&lt;p&gt;What NOT to do: do not submit a bare wrapper of your homepage — the rules above are written about exactly that app. Do not let a converter service submit the app under its own account — rule 4.2.6 rejects that. Do not wrap a website you do not own. And do not treat a rejection as final: Apple sends the reason and guideline number, so fix that point and resubmit.&lt;/p&gt;

&lt;h2&gt;
  
  
  When to get help instead of converting it yourself
&lt;/h2&gt;

&lt;p&gt;When the app takes payments or holds user accounts, get a developer to plan the app-only features with you before you pay anyone. If you already got a Guideline 4.2 rejection, get help before you resubmit.&lt;/p&gt;

&lt;p&gt;If this is your app, contact me through &lt;a href="https://israr-kundi.web.app" rel="noopener noreferrer"&gt;https://israr-kundi.web.app&lt;/a&gt;&lt;/p&gt;

</description>
      <category>flutter</category>
      <category>mobile</category>
      <category>business</category>
      <category>webdev</category>
    </item>
    <item>
      <title>How Much Does It Really Cost to Build a Mobile App in 2026?</title>
      <dc:creator>Israr Kundi</dc:creator>
      <pubDate>Wed, 11 Nov 2026 05:00:03 +0000</pubDate>
      <link>https://dev.to/israr-kundi/how-much-does-it-really-cost-to-build-a-mobile-app-in-2026-26c8</link>
      <guid>https://dev.to/israr-kundi/how-much-does-it-really-cost-to-build-a-mobile-app-in-2026-26c8</guid>
      <description>&lt;h1&gt;
  
  
  How Much Does It Really Cost to Build a Mobile App in 2026?
&lt;/h1&gt;

&lt;p&gt;How much does it really cost to build a mobile app in 2026? A simple app costs about $5,000 to $12,000 to build through a freelancer and $10,000 to $50,000 or more through an agency in the first year.&lt;/p&gt;

&lt;h2&gt;
  
  
  How much does it really cost to build a mobile app in 2026? Look at what each number buys
&lt;/h2&gt;

&lt;p&gt;The numbers you find online are far apart. Fiverr's page-one app gigs start at a median of $100. Clutch's verified client reviews put the average project cost at about $90,780. Studios that publish fixed prices charge $5,000 to $18,000 for a first version: Tovosolutions lists $4,999 for up to 8 screens, dedev $8,000, MVP Factory $10,000 to $16,000, and ZIRA $10,000 to $18,000.&lt;/p&gt;

&lt;p&gt;Each number buys a different thing. On Fiverr, the starting price is the smallest package, often one screen or one feature. A studio's fixed-price package covers a first version, an MVP. Clutch's average covers whole projects, and it is pulled up by large projects; the common case is the $10,000 to $49,999 range.&lt;/p&gt;

&lt;h2&gt;
  
  
  The cause: hours times rate, plus fixed costs
&lt;/h2&gt;

&lt;p&gt;Thinkmobiles breaks a basic MVP down to a minimum of about 300 hours across planning, design, backend, app development and screens. Upwork reports a median rate of $27 an hour for app developers, with most charging between $18 and $39. At those rates, the same 300 hours costs roughly $5,400 to $11,700, before the inevitable extra rounds of changes.&lt;/p&gt;

&lt;p&gt;Netguru publishes $100 to $150 an hour, with $15,000 to $50,000 for a simple single-platform app and $25,000 to $60,000 for an MVP with core features. Upwork's median covers developers worldwide, including lower-cost regions; expect to pay well above it for someone based in the US or Western Europe.&lt;/p&gt;

&lt;p&gt;Fixed costs sit on top for every route. Apple charges $99 a year for its Developer Program and Google charges a $25 one-time registration fee. Supabase is free while you build, though free projects pause after a week of inactivity, and the Pro plan starts at $25 a month.&lt;/p&gt;

&lt;h2&gt;
  
  
  The minimum fix: price the scope, not the idea
&lt;/h2&gt;

&lt;h3&gt;
  
  
  1. Write the screen list
&lt;/h3&gt;

&lt;p&gt;List every screen and what it does. A fixed price only holds against a written scope. Without that list, you cannot tell whether two quotes cover the same app.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Compare routes, not headline numbers
&lt;/h3&gt;

&lt;p&gt;An agency ($10,000 to $50,000+ for a simple app in the first year), a freelancer ($5,000 to $12,000 to build), and an AI builder ($300 to $1,000 a year) sell different things: a team, one developer, or a subscription you run yourself. Get each one to list what is inside the number before you compare the numbers.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Ask what sits outside the price
&lt;/h3&gt;

&lt;p&gt;Store accounts, hosting, analytics, email and payment fees are usually extra. Get them listed before you agree, not after the app is built.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. Put ownership in writing
&lt;/h3&gt;

&lt;p&gt;Source code goes in your own GitHub account, and the app is published under your own Apple and Google accounts. The risk with a freelancer is not the price. It is that one person holds all the knowledge of your codebase, and if they move on you inherit code you did not write and may not understand.&lt;/p&gt;

&lt;h3&gt;
  
  
  5. Budget for the year after launch
&lt;/h3&gt;

&lt;p&gt;Since April 28, 2026, Apple requires every upload to be built with Xcode 26 and the iOS 26 SDK. From August 31, 2026, Google Play requires new apps and updates to target Android 16. Every one of those requirements means updating dependencies, rebuilding and retesting. With an agency or freelancer that is paid work; doing it yourself, it is a few evenings a year on a maintained codebase.&lt;/p&gt;

&lt;p&gt;What NOT to do: do not buy a $100 starting gig and expect a finished app in the stores — that price buys the smallest package, often one screen or one feature. Do not compare quotes that cover different things; check what each one includes first. Do not skip the fixed fees: whichever route you pick, Apple and Google charge them.&lt;/p&gt;

&lt;h2&gt;
  
  
  What a small app costs with me
&lt;/h2&gt;

&lt;p&gt;My starting prices, from my cost page: building a small 4–5 screen app with Supabase from $300, fixing and finishing a half-built app from $50, publishing to one store $100. The exact quote depends on your screen list.&lt;/p&gt;

&lt;h2&gt;
  
  
  When to get help instead of pricing it yourself
&lt;/h2&gt;

&lt;p&gt;When the app takes payments, holds user accounts, or has to earn money from day one, get a developer to write the scope with you before you pay anyone. If two quotes differ wildly and you cannot see why, ask each one for the screen list behind the number.&lt;/p&gt;

&lt;p&gt;If this is your app, contact me through &lt;a href="https://israr-kundi.web.app" rel="noopener noreferrer"&gt;https://israr-kundi.web.app&lt;/a&gt;&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>flutter</category>
      <category>mobile</category>
      <category>business</category>
    </item>
    <item>
      <title>Make Your AI-Generated App Look Professional</title>
      <dc:creator>Israr Kundi</dc:creator>
      <pubDate>Tue, 10 Nov 2026 05:01:37 +0000</pubDate>
      <link>https://dev.to/israr-kundi/make-your-ai-generated-app-look-professional-3ppb</link>
      <guid>https://dev.to/israr-kundi/make-your-ai-generated-app-look-professional-3ppb</guid>
      <description>&lt;p&gt;You can make your AI-generated app look professional without rebuilding it. The app works — it just looks like every other app the same tool built.&lt;/p&gt;

&lt;h2&gt;
  
  
  The problem: "It works, but it looks like a template"
&lt;/h2&gt;

&lt;p&gt;You open your app next to three others from the same tool and cannot tell them apart. Same purple gradient on the hero, same font on every screen, three equal cards with a small icon on top of each, a little badge above the headline, a centred headline with two buttons under it.&lt;/p&gt;

&lt;p&gt;In April 2026, Adrian Krebs checked 1,590 project pages on Hacker News for about fifteen of these patterns: 22% showed at least four, 32% showed two or three, and only 46% showed one at most. A September 2026 check of 832 websites found 40% of apps built with Lovable carried at least three of five default design markers, against 8% of funded Y Combinator startups.&lt;/p&gt;

&lt;p&gt;An analysis of 3.2 million Reddit posts, published in 2026, found "they all look the same" and "screams AI" each in about 13% of discussions on the topic.&lt;/p&gt;

&lt;h2&gt;
  
  
  The cause: the tool returns the average
&lt;/h2&gt;

&lt;p&gt;An AI coding tool predicts the most likely output from what it has seen. Ask for "a clean, modern dashboard" with no other direction and the model returns to the middle of what it has seen most often — Anthropic calls this distributional convergence.&lt;/p&gt;

&lt;p&gt;Anthropic's design instructions for Claude were rewritten three times between November 2025 and September 2026. The September 2026 version lists five families: big serif headlines with a terracotta accent, near-black with one acid-bright accent, newspaper-style layouts, identical rounded cards, and "template chrome" — small all-caps labels above every heading, middle dots, monospace labels, and an arrow on every link. OpenAI's March 2026 design guide for GPT-5.4 bans the same kind of defaults: no Inter, Roboto, or Arial, no purple on white, no cards used for no reason.&lt;/p&gt;

&lt;p&gt;The look is not a bug in your prompt. It is the tool working with no decisions to follow.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to make your AI-generated app look professional: the minimum fix
&lt;/h2&gt;

&lt;p&gt;You do not need a redesign. Make a handful of decisions once, write them down, and feed them to the tool.&lt;/p&gt;

&lt;h3&gt;
  
  
  1. Kill the gradient, pick one accent
&lt;/h3&gt;

&lt;p&gt;Replace the hero gradient with a flat ground — white, near-black, or a low-chroma tint — and let one accent colour do all the emphasis. Pick the accent and two neutrals with real hex values, and forbid other decorative colours.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Break the type monoculture
&lt;/h3&gt;

&lt;p&gt;Keep one typeface for body text and give headlines a second one with actual character. If you keep a single family, at least open up the headline size and tighten its tracking so it stops looking like large body copy.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Replace decoration with proof
&lt;/h3&gt;

&lt;p&gt;Swap gradient blobs, glass panels, and stock illustrations for real screenshots of your product, with real data, cropped tight on the part that matters. A rough screenshot of a working product beats a polished abstract graphic, because only one shows the actual product.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. Rewrite the headline as a claim
&lt;/h3&gt;

&lt;p&gt;"AI-powered workflow automation" is a category, not a headline. A claim names the customer and the result: what happens, for whom, and how fast. Generated copy defaults to categories.&lt;/p&gt;

&lt;h3&gt;
  
  
  5. Break the grid once
&lt;/h3&gt;

&lt;p&gt;Make one section asymmetric — a wide screenshot against narrow text, or a section that breaks the three-column rhythm — to show that choices were made.&lt;/p&gt;

&lt;h3&gt;
  
  
  6. Write the decisions down and reuse them
&lt;/h3&gt;

&lt;p&gt;Put your colours, type scale, spacing steps, and corner radius on one page — a token sheet — and paste it into every session. Add a ban list: no purple or indigo gradients, no pill badge above a headline, no three equal icon cards, no emoji in the interface.&lt;/p&gt;

&lt;p&gt;Without a written system, the tool freestyles.&lt;/p&gt;

&lt;p&gt;What NOT to do: do not ask the tool to "make it more unique" or "more modern" — vague words produced the generic look in the first place. Do not restyle screen by screen before you fix the tokens; you will redo the work when the next prompt drifts back to the defaults. And do not rebuild the app if it already works. Only the decision layer is missing.&lt;/p&gt;

&lt;h2&gt;
  
  
  When to get help instead of fixing it yourself
&lt;/h2&gt;

&lt;p&gt;When the app is about to face investors, enterprise buyers, or paying customers, get a designer or developer to author the token system once. The same goes if every new prompt keeps drifting your screens back to the defaults: the system is not written down tightly enough, and someone who has done it before can pin it down.&lt;/p&gt;

&lt;p&gt;If this is your app, contact me through &lt;a href="https://israr-kundi.web.app" rel="noopener noreferrer"&gt;https://israr-kundi.web.app&lt;/a&gt;&lt;/p&gt;

</description>
      <category>flutter</category>
      <category>ai</category>
      <category>design</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Stripe Payment Successful but App Still Shows Unpaid</title>
      <dc:creator>Israr Kundi</dc:creator>
      <pubDate>Mon, 09 Nov 2026 04:58:51 +0000</pubDate>
      <link>https://dev.to/israr-kundi/stripe-payment-successful-but-app-still-shows-unpaid-dnp</link>
      <guid>https://dev.to/israr-kundi/stripe-payment-successful-but-app-still-shows-unpaid-dnp</guid>
      <description>&lt;p&gt;Stripe payment successful but app still shows unpaid — your customer paid, and Stripe shows the money. The message that was meant to tell your app about it never arrived, or arrived and got turned away.&lt;/p&gt;

&lt;h2&gt;
  
  
  Stripe payment successful but app still shows unpaid: the problem
&lt;/h2&gt;

&lt;p&gt;A customer writes in: "I paid, but I still can't use the app." You open Stripe and the payment is right there, marked succeeded. You open your app and the same customer is still on the free plan — no error, nothing in the logs. The payment is not the problem — the gap between Stripe and your app is.&lt;/p&gt;

&lt;h2&gt;
  
  
  The cause: your app only learns about payments from a webhook
&lt;/h2&gt;

&lt;p&gt;With hosted Checkout, the payment page is Stripe's, not your app's. When a payment succeeds, Stripe sends your server a webhook — a message posted to a web address you registered — to say "this customer paid." Your app switches the customer to the paid plan only when that message arrives and your code acts on it.&lt;/p&gt;

&lt;p&gt;So there are only two ways this breaks: the message never reaches your code, or it reaches your code and gets rejected. Your logs may show the sign of it: "No signatures found matching the expected signature for payload."&lt;/p&gt;

&lt;h2&gt;
  
  
  The minimum fix
&lt;/h2&gt;

&lt;h3&gt;
  
  
  1. Read the delivery log first
&lt;/h3&gt;

&lt;p&gt;In the Stripe Dashboard, open Workbench, then Webhooks, pick your endpoint, and open Event deliveries. It shows every event Stripe tried to send and the status your server answered with.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;No event listed at all: start with step 2 — check the endpoint address and which events it is subscribed to.&lt;/li&gt;
&lt;li&gt;Event listed with an error status: the break is your endpoint. A 400 usually means a signature problem, 401 or 403 means something is blocking Stripe, 404 a wrong address, 500 an error in your code.&lt;/li&gt;
&lt;li&gt;Event delivered with a 2xx status but the plan never changed: your code answered OK but the plan still did not save. Go to step 6.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  2. Check the endpoint address is your live one
&lt;/h3&gt;

&lt;p&gt;Use your real production address, not a preview deployment or old domain. Stripe does not follow redirects — if your address redirects, Stripe counts that as a failed delivery. Put the final address in the endpoint settings.&lt;/p&gt;

&lt;p&gt;Also check the endpoint is switched on and subscribed to the events your code waits for. An endpoint only gets the event types you pick — if your code waits for &lt;code&gt;checkout.session.completed&lt;/code&gt; but the endpoint only gets &lt;code&gt;payment_intent.succeeded&lt;/code&gt;, your code never runs.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Use the right signing secret
&lt;/h3&gt;

&lt;p&gt;Every webhook endpoint has its own signing secret, starting with &lt;code&gt;whsec_&lt;/code&gt;. Test and live secrets differ, and the Stripe CLI's secret differs again from the Dashboard's. Use the wrong one in live mode and every event fails its signature check.&lt;/p&gt;

&lt;p&gt;Copy the live endpoint's secret from the Dashboard into your production settings, and redeploy.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. Check the signature against the raw body
&lt;/h3&gt;

&lt;p&gt;Stripe signs the exact bytes it sends. If your code reads the body as JSON first and then checks the signature, the check fails every time. Verify the signature against the raw body, before your code parses it, with Stripe's own library.&lt;/p&gt;

&lt;h3&gt;
  
  
  5. Grant access only from the webhook, never from the success page
&lt;/h3&gt;

&lt;p&gt;Do not switch on the paid plan from the page the customer lands on after paying. If they close the tab before that page loads, nothing is recorded — and if your code switches on the plan when that page loads, anyone who types that address into a browser gets the paid plan for free.&lt;/p&gt;

&lt;p&gt;Do the real work in the webhook handler, when &lt;code&gt;checkout.session.completed&lt;/code&gt; arrives and &lt;code&gt;payment_status&lt;/code&gt; is &lt;code&gt;paid&lt;/code&gt;. The success page should only read the status from your database.&lt;/p&gt;

&lt;h3&gt;
  
  
  6. Make sure the handler knows who paid — and can save it
&lt;/h3&gt;

&lt;p&gt;This step has two separate problems. First, your handler cannot tell which user paid, because the checkout session was created without a user ID. Save the user ID in &lt;code&gt;client_reference_id&lt;/code&gt; or the session metadata when you create the checkout.&lt;/p&gt;

&lt;p&gt;Second, the handler runs but cannot write to your database. It runs on your server with no logged-in user, so it needs a server-only key. With Supabase, a write with the anon key gets blocked by row-level security — use the service role key, kept out of your frontend code.&lt;/p&gt;

&lt;p&gt;If the handler is a Supabase Edge Function, turn JWT verification off: Stripe sends no Supabase token, so every call would come back 401.&lt;/p&gt;

&lt;p&gt;For subscriptions, one more event matters: &lt;code&gt;checkout.session.completed&lt;/code&gt; fires once, at signup. Handle &lt;code&gt;customer.subscription.updated&lt;/code&gt; and &lt;code&gt;invoice.paid&lt;/code&gt; too, or the plan never updates again.&lt;/p&gt;

&lt;h3&gt;
  
  
  7. Replay what was missed
&lt;/h3&gt;

&lt;p&gt;Once the endpoint is fixed, resend the failed events from the Dashboard. In live mode, Stripe retries a failed delivery for up to three days, and you can resend one by hand for up to 15 days. Fix the cause first.&lt;/p&gt;

&lt;h2&gt;
  
  
  When to get help instead of fixing it yourself
&lt;/h2&gt;

&lt;p&gt;If the delivery log shows your own code answering with a 500, or the app takes subscriptions, get a developer to look at the handler. A bug that hands out paid access for free, or leaves paying customers locked out, costs more than the fix.&lt;/p&gt;

&lt;p&gt;If this is your app, contact me through &lt;a href="https://israr-kundi.web.app" rel="noopener noreferrer"&gt;https://israr-kundi.web.app&lt;/a&gt;&lt;/p&gt;

</description>
      <category>stripe</category>
      <category>webhooks</category>
      <category>payments</category>
      <category>flutter</category>
    </item>
    <item>
      <title>Vibe-Coded App Security Holes to Close Before Real Users</title>
      <dc:creator>Israr Kundi</dc:creator>
      <pubDate>Sun, 08 Nov 2026 05:01:43 +0000</pubDate>
      <link>https://dev.to/israr-kundi/vibe-coded-app-security-holes-to-close-before-real-users-3blf</link>
      <guid>https://dev.to/israr-kundi/vibe-coded-app-security-holes-to-close-before-real-users-3blf</guid>
      <description>&lt;p&gt;Vibe-coded app security holes are the gaps your AI builder left open while making the app work. Before real users sign up, close four of them: open database tables, secrets in front-end code, auth checks that point the wrong way, and production settings never switched on.&lt;/p&gt;

&lt;h2&gt;
  
  
  The problem: it works, and it is wide open
&lt;/h2&gt;

&lt;p&gt;Your app works. You typed what you wanted, the AI tool built it, and it looks right. People can sign up, add details, and pay. So the question is simple: can anyone else read all of it?&lt;/p&gt;

&lt;p&gt;In June 2026, Symbiotic Security scanned 1,072 vibe-coded apps using Supabase. 98% had at least one flaw, 16% a critical one, and only 26 were clean. On 172, anyone could delete records without signing in; on 39, anyone could read every table. UpGuard reported the same pattern on 25 September 2026: 16,326 Supabase databases had tables readable from the public internet with no sign-in, out of roughly 300,000 domains scanned, and over half showed signs of personal data inside.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why it happens
&lt;/h2&gt;

&lt;p&gt;An AI builder aims for a working demo, not a locked door. It writes the feature, watches it run, and moves on. Security checks are not part of that loop unless you ask for them.&lt;/p&gt;

&lt;p&gt;Tables are the clearest example. One made in the Supabase dashboard gets Row Level Security switched on by default; one made with raw SQL does not, and raw SQL is how AI tools make tables. UpGuard traced the open databases back to exactly that gap.&lt;/p&gt;

&lt;p&gt;Keys follow the same pattern. The tool needs a key to talk to the database, so it pastes the key into the code where it can reach it — code that ships to the browser, where anyone can copy it out. In the Symbiotic scan, 308 apps had their Supabase key in their JavaScript, and 24 had another API key in their source code.&lt;/p&gt;

&lt;p&gt;Auth guards get written the wrong way round too. In February 2026, The Register reported on one Lovable-built education app with 16 vulnerabilities, six critical, that exposed 18,697 user records including 14,928 unique email addresses. Missing RLS and inverted auth guards were the cause: the checks existed, but they let the wrong people through.&lt;/p&gt;

&lt;h2&gt;
  
  
  Vibe-coded app security holes: the minimum fix
&lt;/h2&gt;

&lt;p&gt;Work through these in order. Each step takes minutes, and each closes a hole the scans above keep finding.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;List every table with Row Level Security switched off. In the Supabase dashboard, check each table in the public schema, or run this query: select tablename from pg_tables where schemaname = 'public' and rowsecurity = false; Every table that shows up is readable by anyone with your public key if your project uses the old automatic grants (all projects created before 30 May 2026 do). Switch RLS on for each one, then write policies that only let a signed-in user touch their own rows — one each for read, add, change, delete. Do not write a policy that says using (true): it switches RLS on and lets everyone through — the same as having no RLS at all. It is also the fix an AI assistant writes most often when a query fails, so check for it even if RLS looks on.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Search your code for every key, then sort them into two piles. The publishable key, sometimes called the anon key, is designed to be public, so it can stay in front-end code. Your data is protected by RLS policies, not by hiding that key. The service_role key, and any key labelled secret or private, must never sit in front-end code: it bypasses RLS. Move anything needing one behind your own server or a server function, and rotate every key that was ever in client code — the old key is already out there, in every copy that shipped. Do not just move a secret key into a different file in the same front-end folder: the browser still downloads that file, so the key is still public.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Test every action while signed out. Open a private browser window and try to read, change, and delete a record without signing in. If any of it works, the guard is missing or backwards. Check the admin pages and API endpoints too, not just the screens users see. In a March 2026 VibeWrench scan of 100 vibe-coded apps, 21% had no authentication on their endpoints. Check storage too: a public bucket serves every file to anyone with the link.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Switch on the production protections, then re-check after every change. Turn on CSRF protection: 70% of the VibeWrench apps were missing it. Run the Supabase Security Advisor and fix every RLS warning it lists. Then repeat this check after each round of AI changes: each fix can quietly reopen a hole. The holes come back when nobody is watching.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  When to get help instead
&lt;/h2&gt;

&lt;p&gt;Get help if a service_role key was ever live in shipped code, or if your checks show records already readable. Get help too if you cannot tell which tables are open, or if your policies still let a signed-out test read them. Guessing at access rules is how the holes stay open.&lt;/p&gt;

&lt;p&gt;If this is your app, contact me through &lt;a href="https://israr-kundi.web.app" rel="noopener noreferrer"&gt;https://israr-kundi.web.app&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Update (15 Nov 2026): A reader pointed out a gap in this article. Row Level Security is row-level, not column-level. Under a typical policy, a signed-in user can update columns like is_admin from the browser console. The fix is to control access at the column level with revoke and grant, or keep privileged columns out of tables the client can write to. Thanks to Sunnatulla for the correction.&lt;/p&gt;

</description>
      <category>security</category>
      <category>supabase</category>
      <category>flutter</category>
      <category>instagramreel</category>
    </item>
    <item>
      <title>Do I Need My Own App Instead of Paying a Platform?</title>
      <dc:creator>Israr Kundi</dc:creator>
      <pubDate>Sat, 07 Nov 2026 04:56:22 +0000</pubDate>
      <link>https://dev.to/israr-kundi/do-i-need-my-own-app-instead-of-paying-a-platform-5f7j</link>
      <guid>https://dev.to/israr-kundi/do-i-need-my-own-app-instead-of-paying-a-platform-5f7j</guid>
      <description>&lt;h1&gt;
  
  
  Do I Need My Own App Instead of Paying a Platform?
&lt;/h1&gt;

&lt;p&gt;Do I need my own app for my shop instead of paying a platform on every sale? When your platform takes a cut of every order plus a monthly fee, that question stops being about technology and starts being about your margins.&lt;/p&gt;

&lt;h2&gt;
  
  
  The problem: the monthly fee tripled, and the cut stayed
&lt;/h2&gt;

&lt;p&gt;Boutique owners talked about this exact squeeze in a Square Community thread from February 2026. One owner put it plainly: CommentSold "ended the 49.99 a month plan giving them 5% of the sales and went to 149.99 and 5% of your sales as the base plan". Same post: "5% of your sales, 3% for credit card fees and 149.99 a month it's a definite no for us now."&lt;/p&gt;

&lt;p&gt;Her answer was to leave. She added a Hot deals tab to her own website, started training customers with emails and texts to go there for the same deals, and finished a new app that was already in review before she cancelled CommentSold. Another boutique owner in the same thread wrote that she is cancelling CommentSold and finishing her own mobile app, because "I will have all the control of the app then." A third said a lot of her boutique friends are cancelling too.&lt;/p&gt;

&lt;p&gt;So the pain is not one angry shop owner. Three voices in the same thread describe the same squeeze.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why it happens
&lt;/h2&gt;

&lt;p&gt;Platforms charge you twice: a monthly fee, and a percentage of every sale, with card fees on top. The monthly fee tripled, from $49.99 to $149.99, while the 5% cut of sales stayed exactly where it was. You pay more before you sell a single item, and still hand over 5% of each order plus around 3% in card fees.&lt;/p&gt;

&lt;p&gt;Lock-in makes it worse. When CommentSold hosted the app, cancelling meant losing the app as well. One owner spelled it out: before, CommentSold hosted the app with built-in live shows, and "when we cancel we will lose the app. So I am building our own". Leaving means rebuilding, so she built her own first.&lt;/p&gt;

&lt;p&gt;One owner also noted that "live shows are starting to die out", in the same reply where she said she is cancelling CommentSold.&lt;/p&gt;

&lt;h2&gt;
  
  
  Do I need my own app for my shop instead of paying a platform on every sale? The minimum fix
&lt;/h2&gt;

&lt;p&gt;Work through these steps in order, and do the sums before you cancel anything.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;Add up what you pay now. Take last month's bill and split it into three lines: the monthly fee, the percentage of your sales, and the card fees. With the CommentSold numbers from the thread, $2,000 of sales in a month means $149.99, plus $100 from the 5%, plus about $60 in card fees — around $310 for the month.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;List what the platform actually does for you. Write down each thing: live shows, the hosted app, checkout, emails, texts. Cross off anything you no longer use. If live shows have died out for your shop, say so honestly. What is left is the real value you are paying for.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Try the halfway step first. One boutique owner did not jump straight to an app. She put a Hot deals tab on her own website and trained her customers with emails and texts to go there for the same deals she used to give on CommentSold. It shows you whether your customers will follow you off the platform.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;If you build your own app, keep it small. Products, checkout, a deals section, and a way to tell customers about a deal. Do not rebuild live shows or every platform feature. Build only the parts that bring in sales.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Build and test the replacement before you cancel. The owner in the thread finished her new app and had it in the review process, with one more live still scheduled, before cancelling. Cancel only when the new app, or the website plus email setup, is already working.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Check who owns what before you sign anything new. Ask whether you can export your customer list, your order history, and your product list. Ask who owns the app if you stop paying. Get the answer in writing, not as a sales promise.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Do not cancel first and build later. Cancelling means losing the app CommentSold hosted, so have the replacement ready first. Do not jump to another platform with the same percentage cut on every sale without reading its fee page first.&lt;/p&gt;

&lt;h2&gt;
  
  
  When to get help instead
&lt;/h2&gt;

&lt;p&gt;Get help if checkout or payments are outside your comfort zone, or if you need your product list and customer list moved without losing orders. Get help too if you have been quoted a build and cannot tell what is actually included. A second pair of eyes on the fees and the handover is worth having before you cancel.&lt;/p&gt;

&lt;p&gt;If this is your shop, contact me through &lt;a href="https://israr-kundi.web.app" rel="noopener noreferrer"&gt;https://israr-kundi.web.app&lt;/a&gt;&lt;/p&gt;

</description>
      <category>smallbusiness</category>
      <category>ecommerce</category>
      <category>mobile</category>
      <category>flutter</category>
    </item>
    <item>
      <title>Stuck in Play Store Closed Testing? How to Fix It</title>
      <dc:creator>Israr Kundi</dc:creator>
      <pubDate>Fri, 06 Nov 2026 04:59:22 +0000</pubDate>
      <link>https://dev.to/israr-kundi/stuck-in-play-store-closed-testing-how-to-fix-it-3oa8</link>
      <guid>https://dev.to/israr-kundi/stuck-in-play-store-closed-testing-how-to-fix-it-3oa8</guid>
      <description>&lt;p&gt;Stuck in Play Store closed testing, with the console saying you have 12 testers while nobody is really testing your app? You need 12 testers opted in continuously for at least 14 days before Google lets you apply for production access.&lt;/p&gt;

&lt;h2&gt;
  
  
  The problem: the console says 12 testers, but nobody is testing
&lt;/h2&gt;

&lt;p&gt;Your app is finished. You ran a closed test, applied for production access, and Google said no. Then a new closed test starts on its own, and the console still shows 12 testers opted in.&lt;/p&gt;

&lt;p&gt;That is exactly what happened to one developer in June 2026. After his production access application was rejected, a third closed testing cycle started on its own on 24 June 2026. Play Console still counted 12 testers. The real number of testers, apart from himself, was zero. The app was installed on only 5 devices. He had deleted the Google Group holding his testers, hoping the count would reset. It did not. His support ticket was closed without a comment. He opened a forum thread on 27 June 2026.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why it happens
&lt;/h2&gt;

&lt;p&gt;Google's rule is the cause. For personal Play Console accounts created after 13 November 2023, you must run a closed test with at least 12 testers who have been opted in continuously for at least 14 days. Until you meet that, the Production and Pre-registration pages stay disabled. Review usually takes seven days or less.&lt;/p&gt;

&lt;p&gt;Three things catch people out. First, being on the tester list is not enough on its own. Each tester has to open the opt-in link and accept, and then actually install the app and use it, or Google can still refuse you for low engagement. Second, the 14 days have to be continuous. A tester who opts out and back in starts a fresh 14 days. Third, meeting the numbers only lets you apply. It does not guarantee approval. Google can still refuse you if your testers were not engaged with the app during the test, and it can ask you to test for longer.&lt;/p&gt;

&lt;p&gt;Business accounts do not have this requirement, but you cannot switch a personal account to a company account. You would need a whole new account. And in September 2026, one developer got the refusal email with the reason spelled out: testers were not engaged with the app during the closed test.&lt;/p&gt;

&lt;h2&gt;
  
  
  Stuck in Play Store closed testing: the minimum fix
&lt;/h2&gt;

&lt;p&gt;Do these steps in order. The count only moves when real people opt in and stay.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;Check whether the rule even applies to you. The 12-tester, 14-day rule applies to personal accounts created after 13 November 2023. Organisation accounts and older personal accounts are exempt.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Recruit 15 to 18 real testers as a buffer, even though Google's minimum is 12. With only 12, one dropout puts you back under the line, so the extra testers cover you if someone leaves. Ask friends, family, colleagues, or people like your real users. Each one must be a real person on a real device who will actually open the app.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Make opting in easy and check it worked. Send each tester the opt-in link, and ask them to open it, accept, and install the app. Then check both numbers: the opted-in count, which lets you apply for production access, and installed devices, which show whether testers installed the app. Installs alone do not prove they used it. In the June 2026 case, the console showed 12 opted in and only 5 installs. If installs are low, your test is not really running.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Give testers a short job to do. Tell them which features to try and how to report a bug. Google's own guidance says to ask testers to use as many features as possible. A tester who installs the app and never opens it does not help.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Collect the feedback and answer it. Read the Testing feedback page in Play Console, reply to testers, and fix the real bugs. Keep a short note of what feedback came in and what you changed. Google's page says you must summarize your testing feedback when you apply.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Apply only when the closed testing release is published and at least 12 testers have been opted in continuously for 14 days. Then apply and answer the three sections honestly: about your closed test, about your app, and about your production readiness, using your real test numbers and notes.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Do not delete your tester group and expect the count to reset. In the June 2026 case it did not work that way: the console kept counting 12 testers after the group was gone. Testing guides warn that emulators, bots, or duplicate accounts do not count as testers, so they will not move you toward the 12. And do not apply while your testers have not really used the app. That risks another refusal for low engagement.&lt;/p&gt;

&lt;h2&gt;
  
  
  When to get help instead
&lt;/h2&gt;

&lt;p&gt;Get help if you have been refused again, if the tester count will not move, or if you need the production access answers written from your real test numbers. Get help too if your app still has crashes or broken screens. A clean test with real users and honest answers gives you the best chance of getting through.&lt;/p&gt;

&lt;p&gt;If this is your app, contact me through &lt;a href="https://israr-kundi.web.app" rel="noopener noreferrer"&gt;https://israr-kundi.web.app&lt;/a&gt;&lt;/p&gt;

</description>
      <category>mobile</category>
      <category>android</category>
      <category>googleplay</category>
      <category>flutter</category>
    </item>
    <item>
      <title>My API Key Is Visible in the Code — How to Fix It</title>
      <dc:creator>Israr Kundi</dc:creator>
      <pubDate>Thu, 05 Nov 2026 10:38:09 +0000</pubDate>
      <link>https://dev.to/israr-kundi/my-api-key-is-visible-in-the-code-how-to-fix-it-1i81</link>
      <guid>https://dev.to/israr-kundi/my-api-key-is-visible-in-the-code-how-to-fix-it-1i81</guid>
      <description>&lt;p&gt;My API key is visible in the code — and if that is what you found, anyone with a copy of your app can see it too. Rotate that key first, then move it off the client, because deleting it from the code alone does not fix the leak.&lt;/p&gt;

&lt;h2&gt;
  
  
  The problem: your key is sitting in the open
&lt;/h2&gt;

&lt;p&gt;You built the app fast with an AI tool. It works. Then you open the code, or someone else does, and there it is: your API key, sitting in a file anyone can read. It might be in a .env file, in the JavaScript bundle, or right in the source. You did not mean to publish it. The tool put it there so the app could call the API straight from the phone or browser.&lt;/p&gt;

&lt;p&gt;In March 2026, VibeWrench scanned 100 apps built with Lovable, Bolt.new, Cursor, and v0.dev. It found 318 vulnerabilities, and 41% of the apps exposed secrets or API keys. One Lovable app had a Supabase service role key sitting in a .env file. With that key, anyone can bypass Row Level Security and read every row in every table. A June 2026 scan by Symbiotic Security looked at 1,072 Supabase-backed vibe-coded apps and found 98% had at least one flaw.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why it happens
&lt;/h2&gt;

&lt;p&gt;AI builders need the key to call the API, so they drop it into the client code. That is exactly why it leaks. Anything in the client ships with the app. In Flutter, a key passed with --dart-define is baked into the release binary. A .env file added with flutter_dotenv is bundled into the app as an asset. Anyone who pulls the app apart can find both. Some builders even add dangerouslyAllowBrowser: true to the OpenAI SDK to make an error go away. That setting exposes your secret key in client-side code. It is the leak, not the fix.&lt;/p&gt;

&lt;p&gt;One thing to get straight: not every key in your code is a leak. A Supabase anon key is public by design. The protection there comes from Row Level Security, not from keeping the key secret. The real danger is secret keys — a service role key, an OpenAI key, a Stripe secret key — sitting where anyone can read them. And when RLS is missing, even the public anon key opens the whole database. A September 2026 UpGuard scan found 16,326 Supabase databases readable by anyone using only the public anon key, because RLS was never turned on.&lt;/p&gt;

&lt;h2&gt;
  
  
  My API key is visible in the code: the minimum fix
&lt;/h2&gt;

&lt;p&gt;Do these steps in order. The order matters, because the first step is the only one that stops the key from working.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;Rotate the key at the provider, first. Make the old key stop working. Once a key has been visible in code or on GitHub, assume someone copied it.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Check usage and billing for calls you did not make. Look at the provider's usage page for calls from countries or times you don't recognise. If someone used your key, you will see it there.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Remove the key from all client code. Search the built bundle and the repo, not just the source file. A key in git history stays readable even after you add .gitignore.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Move the call server-side. Put the key on your own backend, a backend proxy, or an Edge Function, and let the app call that instead. For Supabase, store the secret with the Edge Function secrets and read it inside the function. The browser only calls your function, never the real API.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;If the key was ever in git, purge the history — after rotating. Rewrite history with git-filter-repo, force-push, and tell anyone with a clone. Deleting the commit alone does not remove copies others already have.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Stop it happening again. Turn on GitHub push protection, so secrets get blocked before they reach the repo. Keep every .env file in .gitignore. Set a spend cap at the provider, so a future leak cannot run up an open-ended bill.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Hiding the key better is not a fix. Obfuscation makes a key harder to read, not hidden — it is still in the binary and can be pulled out. Do not just delete the key from the code without rotating it. Copies already exist in git history, cached bundles, and anywhere the code was seen.&lt;/p&gt;

&lt;h2&gt;
  
  
  When to get help instead
&lt;/h2&gt;

&lt;p&gt;Get help if the key could reach real user data, if you are not sure what the key can access, or if the app is already live with users. That means keys like a Stripe secret key or a Supabase service role key, not a publishable key. Check in the provider dashboard what the key can read and write before you decide what to rotate. The same goes if the leak is spread across git history and old builds — that cleanup is easy to get wrong, so get help with it.&lt;/p&gt;

&lt;p&gt;If this is your app, contact me through &lt;a href="https://israr-kundi.web.app" rel="noopener noreferrer"&gt;https://israr-kundi.web.app&lt;/a&gt;&lt;/p&gt;

</description>
      <category>api</category>
      <category>security</category>
      <category>flutter</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Is my Supabase database open for anyone to read?</title>
      <dc:creator>Israr Kundi</dc:creator>
      <pubDate>Wed, 04 Nov 2026 04:49:30 +0000</pubDate>
      <link>https://dev.to/israr-kundi/is-my-supabase-database-open-for-anyone-to-read-57ap</link>
      <guid>https://dev.to/israr-kundi/is-my-supabase-database-open-for-anyone-to-read-57ap</guid>
      <description>&lt;h1&gt;
  
  
  Is my Supabase database open for anyone to read?
&lt;/h1&gt;

&lt;p&gt;Is my Supabase database open for anyone to read? It can be, if an AI coding tool built your app and Row Level Security (RLS) was never turned on for your tables. You can check in a few minutes, and the fix is usually small.&lt;/p&gt;

&lt;h2&gt;
  
  
  What you’re seeing
&lt;/h2&gt;

&lt;p&gt;Most owners see nothing wrong. The app works. Users sign in, data shows up, and you ship it.&lt;/p&gt;

&lt;p&gt;That’s the trap. An open database looks just like a working one. No error, no warning banner, nothing breaks.&lt;/p&gt;

&lt;p&gt;UpGuard scanned about 300,000 Supabase domains and found 16,326 databases with tables readable from the public internet with no authentication. Over half showed signs of personal data.&lt;/p&gt;

&lt;p&gt;A smaller case shows what this looks like in one app. In February 2026, The Register reported on an education app built with Lovable. It had 16 vulnerabilities, 6 of them critical, and exposed 18,697 user records, including 14,928 unique email addresses. The causes were missing RLS and inverted auth guards, which means the login checks were working the wrong way round.&lt;/p&gt;

&lt;p&gt;If your app stores emails, names, orders or messages, you’re in the group that should check.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why it happens
&lt;/h2&gt;

&lt;p&gt;Your app can look finished while the database is still wide open. That gap usually comes from how the tables were made.&lt;/p&gt;

&lt;p&gt;Tables made in the Supabase dashboard get Row Level Security turned on by default. Tables made through the API or raw SQL — the route most AI coding tools take — don’t.&lt;/p&gt;

&lt;p&gt;So your app can pass every screen test and still leave its tables readable by anyone who knows how to ask.&lt;/p&gt;

&lt;p&gt;A quick way to check this is to look in Supabase at whether RLS is on for each table, then test that table from a logged-out browser session.&lt;/p&gt;

&lt;h2&gt;
  
  
  Is my Supabase database open for anyone to read? The minimum fix
&lt;/h2&gt;

&lt;p&gt;You don’t need to rebuild the app. Start with this list, in order.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Open Supabase and list every table in your app.&lt;/li&gt;
&lt;li&gt;Turn on RLS for each table — no exceptions.&lt;/li&gt;
&lt;li&gt;Add one policy per table that says who can read it and who can write to it.&lt;/li&gt;
&lt;li&gt;Log out, then try to read each table without signing in. Nothing should come back.&lt;/li&gt;
&lt;li&gt;Fix any table that still returns data before you move on.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Don’t just add a policy and assume it’s safe. A policy with the wrong condition can leave a table open while looking protected.&lt;/p&gt;

&lt;p&gt;Don’t hide behind a secret key in your app code, either. Anyone who can read that code can use the key — and then your RLS rules don’t matter.&lt;/p&gt;

&lt;p&gt;Don’t rely on the app hiding a screen or a button. If the table is readable, the screen is only hiding it, not protecting it.&lt;/p&gt;

&lt;h2&gt;
  
  
  When to get help instead
&lt;/h2&gt;

&lt;p&gt;If you don’t know which tables hold personal data, or which policies your app actually needs, stop there.&lt;/p&gt;

&lt;p&gt;Guessing at policies can lock out real users or leave a gap open. Get someone who has fixed this before to check the tables and policies with you.&lt;/p&gt;

&lt;p&gt;If this is your app, contact me through &lt;a href="https://israr-kundi.web.app" rel="noopener noreferrer"&gt;https://israr-kundi.web.app&lt;/a&gt;&lt;/p&gt;

</description>
      <category>cybersecurity</category>
      <category>database</category>
      <category>security</category>
    </item>
  </channel>
</rss>
