<?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: Saqib Riaz</title>
    <description>The latest articles on DEV Community by Saqib Riaz (@saqib2619).</description>
    <link>https://dev.to/saqib2619</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%2F4244377%2F80db8e6e-ae09-4607-b5f7-ace258155873.jpg</url>
      <title>DEV Community: Saqib Riaz</title>
      <link>https://dev.to/saqib2619</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/saqib2619"/>
    <language>en</language>
    <item>
      <title>Offline-First, Zero Backend: Building a Tailoring Business App That Works Without Internet</title>
      <dc:creator>Saqib Riaz</dc:creator>
      <pubDate>Sun, 15 Nov 2026 16:05:30 +0000</pubDate>
      <link>https://dev.to/saqib2619/offline-first-zero-backend-building-a-tailoring-business-app-that-works-without-internet-1lf1</link>
      <guid>https://dev.to/saqib2619/offline-first-zero-backend-building-a-tailoring-business-app-that-works-without-internet-1lf1</guid>
      <description>&lt;p&gt;Every tailor I know keeps his whole business in paper registers. One notebook for measurements. Another one for orders. Payments live in a third place, which is mostly his memory. It works, right up until the busy season, when the pages fill with arrows and crossings-out and one regular customer's sizes end up in the margin of a book from two years ago.&lt;/p&gt;

&lt;p&gt;TailorVexa is the app I built to replace those registers. It runs a tailoring shop from the phone in the tailor's pocket: customer profiles, measurements, orders and payments, all in one place. And the decision I made before writing a single screen still shapes everything about it:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;No internet required. No account. No server. Everything stays on the phone.&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Why offline-first was the whole point
&lt;/h2&gt;

&lt;p&gt;In the markets where this app gets used, the connection comes and goes, and mobile data costs real money. An app that asks for a login before it will show a customer's chest size is an app that gets deleted by the end of the week. But connectivity was only one of three reasons.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Trust.&lt;/strong&gt; A tailor's measurement book is his business. Plenty of shop owners do not want their customer list sitting on a stranger's server, and honestly, I understand them. The list is the shop.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Cost.&lt;/strong&gt; A backend charges you every month, forever. I build with a zero budget, so every recurring cost is a countdown to the day the thing shuts down. An app with no server has no such countdown.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Speed.&lt;/strong&gt; Reading from local storage is instant. A tailor standing at the counter, tape around his neck, a customer waiting — he will not stand there watching a spinner.&lt;/p&gt;

&lt;h2&gt;
  
  
  The stack
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Flutter&lt;/strong&gt; for the interface, one codebase aimed at Android&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Drift on top of SQLite&lt;/strong&gt; for storage — customers, measurements, orders and payments as proper relational data, all on the device&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;English and full Urdu&lt;/strong&gt;, with a real right-to-left layout, because Urdu is the language the shop actually works in&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;PIN and biometric lock&lt;/strong&gt;, because the phone gets passed around during a working day&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;JSON backup and restore&lt;/strong&gt;, so the whole shop can move to a new phone from one exported file&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That backup piece matters more than people expect. The first question anyone asks about an offline app is what happens when the phone is lost. A file the owner exports himself, keeps where he likes, and imports on the next phone answers it — no cloud, no signup, no subscription standing in between.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the app actually does all day
&lt;/h2&gt;

&lt;p&gt;Each customer gets a profile, and the profile holds everything: his measurements, his orders, what he has paid and what he still owes. A regular walks in after eight months and his full record is on screen in seconds. Anyone who has watched a tailor dig through last season's diary while the counter fills up knows what those seconds are worth.&lt;/p&gt;

&lt;p&gt;Measurements got the most care, because they are the heart of the record. The standard sizes sit in their own fields — chest, waist, length, sleeves, the usual list. And because every experienced tailor keeps notes that never fit a printed form, the app lets him add his own measurement entries too: his own names, his own words, saved with the customer's profile and carried through backup and restore like everything else. One tailor's shorthand is another tailor's confusion, so the app does not force anyone into ready-made boxes.&lt;/p&gt;

&lt;p&gt;Orders carry the booked date and the promised date, and where each one stands — pending, ready or delivered. Payments are written into the order itself: advance taken, part payment later, balance on delivery. When a customer asks what is left on his suit, the answer is a look at the screen, not a debate between two honest memories.&lt;/p&gt;

&lt;h2&gt;
  
  
  The honest trade-offs
&lt;/h2&gt;

&lt;p&gt;No server means no sync between two phones, and no automatic cloud backup sitting somewhere. I do not dress that up. For a single-shop business, one phone is the office, and for that reality local-first is not the cheap option. It is the correct one.&lt;/p&gt;

&lt;p&gt;The full app page, with screenshots and the download, is here: &lt;a href="https://aitechappspk.blogspot.com/2026/11/tailorvexa.html" rel="noopener noreferrer"&gt;TailorVexa on AI Tech Apps&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;If you build for people outside the always-online world, I would argue offline-first is not the fallback plan. It is the product.&lt;/p&gt;




&lt;p&gt;&lt;strong&gt;More from AI Tech Apps:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://aitechappspk.blogspot.com/2026/11/stickora.html" rel="noopener noreferrer"&gt;Stickora — the WhatsApp sticker app with 4,448 original stickers&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://aitechappspk.blogspot.com/2026/11/qyberna.html" rel="noopener noreferrer"&gt;QYBERNA — my self-hosted VPN system with an Android app&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>flutter</category>
      <category>android</category>
      <category>showdev</category>
      <category>indiehackers</category>
    </item>
    <item>
      <title>I Shipped a WhatsApp Sticker App with 4,448 Original Stickers — Here's What I Learned</title>
      <dc:creator>Saqib Riaz</dc:creator>
      <pubDate>Sat, 14 Nov 2026 11:23:33 +0000</pubDate>
      <link>https://dev.to/saqib2619/i-shipped-a-whatsapp-sticker-app-with-4448-original-stickers-heres-what-i-learned-1enf</link>
      <guid>https://dev.to/saqib2619/i-shipped-a-whatsapp-sticker-app-with-4448-original-stickers-heres-what-i-learned-1enf</guid>
      <description>&lt;p&gt;Most sticker apps on the Play Store are thin wrappers around the same recycled meme packs. When I decided to build my own sticker app, I set one rule on day one: &lt;strong&gt;every sticker in the app would be original artwork.&lt;/strong&gt; No scraped memes, no copied packs, nothing with someone else's copyright sitting inside it.&lt;/p&gt;

&lt;p&gt;That one rule shaped the entire project — and nearly doubled the work.&lt;/p&gt;

&lt;h2&gt;
  
  
  The numbers
&lt;/h2&gt;

&lt;p&gt;The final build ships with:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;4,448 stickers&lt;/strong&gt; in &lt;strong&gt;278 packs&lt;/strong&gt; of 16&lt;/li&gt;
&lt;li&gt;3,336 static stickers and 1,112 animated ones&lt;/li&gt;
&lt;li&gt;Every pack has 12 static + 4 animated designs, all unique&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;"All unique" is easy to claim and hard to prove, so I proved it to myself before shipping: I hashed every sticker file (SHA-256) and compared the hashes across the whole library. Zero duplicates. That check runs in CI now, so a duplicate can't sneak back in with a later pack.&lt;/p&gt;

&lt;h2&gt;
  
  
  Lesson 1: Dedupe is a pipeline step, not a hope
&lt;/h2&gt;

&lt;p&gt;With a library this size, duplicates don't sneak in through carelessness — they sneak in through volume. Similar prompts, similar palettes, near-identical poses. So the pipeline has three gates: an automated similarity pass, a hash check, and a final human review of every pack before it ships. A sticker that fails any gate doesn't ship.&lt;/p&gt;

&lt;h2&gt;
  
  
  Lesson 2: Animated stickers are a different sport
&lt;/h2&gt;

&lt;p&gt;Static stickers are forgiving. Animated ones have strict size and format expectations, and a pack that looks fine in a folder can still fail on a phone. I built the animated pipeline around small WebP files, tested every pack on real devices, and kept the animation loops short — a sticker that loops forever is a sticker people delete.&lt;/p&gt;

&lt;h2&gt;
  
  
  Lesson 3: Captions are a feature
&lt;/h2&gt;

&lt;p&gt;The stickers use the caption style people actually send each other in Pakistan — family-group humour, cricket jokes, everyday desi moments. The art carries the joke, but the caption is what makes someone tap it in the middle of a conversation. Writing captions took almost as long as drawing the art, and it was worth every hour.&lt;/p&gt;

&lt;p&gt;A few stickers from the library:&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%2Fdrive.google.com%2Fuc%3Fexport%3Dview%26id%3D1fttApLNC9OkMQNHGgYr_e0cZr_S4WAb6" 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%2Fdrive.google.com%2Fuc%3Fexport%3Dview%26id%3D1fttApLNC9OkMQNHGgYr_e0cZr_S4WAb6" alt="Stickora sample sticker" width="512" height="512"&gt;&lt;/a&gt;&lt;br&gt;
&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdrive.google.com%2Fuc%3Fexport%3Dview%26id%3D1jiFIxehHzO2JD2PYfaheaF_XBPnbnb4T" 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%2Fdrive.google.com%2Fuc%3Fexport%3Dview%26id%3D1jiFIxehHzO2JD2PYfaheaF_XBPnbnb4T" alt="Stickora sample sticker" width="512" height="512"&gt;&lt;/a&gt;&lt;br&gt;
&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdrive.google.com%2Fuc%3Fexport%3Dview%26id%3D1LCa8_Qm06yqsXbCev3T8XZRFJfdGcCrB" 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%2Fdrive.google.com%2Fuc%3Fexport%3Dview%26id%3D1LCa8_Qm06yqsXbCev3T8XZRFJfdGcCrB" alt="Stickora sample sticker" width="512" height="512"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Lesson 4: Monetize without ruining the joke
&lt;/h2&gt;

&lt;p&gt;The app is free, so it carries ads — but stickers are an emotional, in-the-moment product. Interrupting someone mid-conversation to show them an ad is the fastest way to get uninstalled. So ads only appear on screens where the user is browsing or managing packs, never in the middle of sending a sticker. Revenue is lower than it could be. Retention is higher than it would be otherwise. That's the trade I chose.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I'd do differently
&lt;/h2&gt;

&lt;p&gt;Start the dedupe audit at sticker #100, not at the end. And build the animated pipeline first — retrofitting it after the static library was done cost me weeks.&lt;/p&gt;

&lt;p&gt;The full app page, with the download and the complete pack breakdown, is here: &lt;a href="https://aitechappspk.blogspot.com/2026/11/stickora.html" rel="noopener noreferrer"&gt;Stickora on AI Tech Apps&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;If you've built a content-heavy app, I'd genuinely like to hear how you handled originality and scale — drop a comment below.&lt;/p&gt;

&lt;p&gt;Shipping 4,448 original stickers taught me that originality isn't a marketing line, it's a pipeline. And monetization isn't about squeezing every screen, it's about protecting the moment someone wants to share a laugh. Those two problems turned out to be the whole game.&lt;/p&gt;




&lt;p&gt;&lt;strong&gt;More from AI Tech Apps:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://aitechappspk.blogspot.com/2026/11/tailorvexa.html" rel="noopener noreferrer"&gt;TailorVexa — the offline-first tailoring business app&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://aitechappspk.blogspot.com/2026/11/qyberna.html" rel="noopener noreferrer"&gt;QYBERNA — my self-hosted VPN system with an Android app&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>buildinpublic</category>
      <category>showdev</category>
    </item>
  </channel>
</rss>
