<?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: Abdullah Naseer</title>
    <description>The latest articles on DEV Community by Abdullah Naseer (@userxnom).</description>
    <link>https://dev.to/userxnom</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%2F4209313%2F9451ef0a-e609-4949-890b-d86e1cc5512d.jpg</url>
      <title>DEV Community: Abdullah Naseer</title>
      <link>https://dev.to/userxnom</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/userxnom"/>
    <language>en</language>
    <item>
      <title>How to Tell If a Gig Shift Actually Made You Money</title>
      <dc:creator>Abdullah Naseer</dc:creator>
      <pubDate>Tue, 27 Oct 2026 13:29:01 +0000</pubDate>
      <link>https://dev.to/userxnom/how-to-tell-if-a-gig-shift-actually-made-you-money-29mj</link>
      <guid>https://dev.to/userxnom/how-to-tell-if-a-gig-shift-actually-made-you-money-29mj</guid>
      <description>&lt;p&gt;A shift can look busy, pay out a decent amount, and still leave you worse off than you think. The number most apps show you first is gross pay — what came in before costs. That is useful, but it is not the whole story. If you want to know whether a shift was actually worth taking, you need the number that is left after the real costs of doing the work.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why gross pay misleads
&lt;/h2&gt;

&lt;p&gt;Gross pay leaves out everything you spent to earn it. Fuel, food on the road, parking or tolls, and the wear on your vehicle all come out of that same money. A long, high-paying shift with a lot of driving can leave less in your pocket than a shorter, quieter shift close to home. Judging shifts by gross pay alone can make the expensive shifts look like the best ones, when they are not.&lt;/p&gt;

&lt;h2&gt;
  
  
  Subtract the costs you actually paid
&lt;/h2&gt;

&lt;p&gt;After each shift, write down these three things:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Fuel and travel costs.&lt;/strong&gt; What you spent to get to jobs, between jobs, and home again — not just the fuel for the paid trips.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Vehicle wear and maintenance.&lt;/strong&gt; Tires, oil, brakes, and repairs do not happen every shift, but every mile adds to them. If you ignore this cost, you are borrowing from a future repair bill.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Other shift costs.&lt;/strong&gt; Parking, tolls, food you bought because you were out, and anything else you would not have spent if you had stayed home.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Then use this simple check:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Net profit = gross pay − fuel and travel costs − vehicle wear and maintenance − other shift costs&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;That net number is the one worth comparing, shift to shift.&lt;/p&gt;

&lt;h2&gt;
  
  
  Do not forget dead and waiting time
&lt;/h2&gt;

&lt;p&gt;Money is only half the picture. Time is the other half.&lt;/p&gt;

&lt;p&gt;Count the whole shift, not just the paid time: driving to the first job, waiting between jobs, and getting home. A shift with a lot of unpaid waiting can pay less per hour than it first appears, even if the total looks fine. Try this second check:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Net profit per hour = net profit ÷ total time spent on the shift, including waiting and travel&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;When you compare shifts this way, patterns show up quickly. Some times of day, areas, or types of work consistently leave you with more per hour — and some consistently do not.&lt;/p&gt;

&lt;h2&gt;
  
  
  A simple routine after every shift
&lt;/h2&gt;

&lt;p&gt;You do not need a complicated system. After each shift, note:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;What you earned&lt;/li&gt;
&lt;li&gt;What you spent, in the categories above&lt;/li&gt;
&lt;li&gt;When you started and when you finished, including waiting time&lt;/li&gt;
&lt;li&gt;Your net profit, and your net profit per hour&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Then, before you accept a similar shift again, look back at what that kind of shift actually left you with last time. That one habit — comparing net profit, not gross pay — changes which shifts are worth taking.&lt;/p&gt;

&lt;h2&gt;
  
  
  A note on estimates
&lt;/h2&gt;

&lt;p&gt;You will not get every cost exactly right at first, especially vehicle wear. That is fine. A rough, honest estimate that you record every time is far more useful than a perfect calculation you never do. Over a few weeks, your own records will show you which estimates to adjust.&lt;/p&gt;

&lt;h2&gt;
  
  
  The tool I built for exactly this
&lt;/h2&gt;

&lt;p&gt;I built ShiftLog, a free Android app, for exactly this kind of tracking: log a shift, add income and expenses, and see your real net profit per shift. It works offline and needs no account. You can find it here: &lt;a href="https://play.google.com/store/apps/details?id=com.shiftlog.app" rel="noopener noreferrer"&gt;https://play.google.com/store/apps/details?id=com.shiftlog.app&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;What matters most is not the tool, though — it is the habit. Start with net profit, include waiting time, and let your own shifts tell you which work is actually paying.&lt;/p&gt;

</description>
      <category>android</category>
      <category>productivity</category>
      <category>career</category>
    </item>
    <item>
      <title>I built my first Android app without knowing how to code — meet ShiftLog</title>
      <dc:creator>Abdullah Naseer</dc:creator>
      <pubDate>Mon, 26 Oct 2026 19:11:31 +0000</pubDate>
      <link>https://dev.to/userxnom/i-built-my-first-android-app-without-knowing-how-to-code-meet-shiftlog-2fhb</link>
      <guid>https://dev.to/userxnom/i-built-my-first-android-app-without-knowing-how-to-code-meet-shiftlog-2fhb</guid>
      <description>&lt;p&gt;I'm Abdullah, a builder from Pakistan, and ShiftLog is my first app. It's a free, offline shift and profit tracker for gig workers and drivers. Log a shift, add income and expenses (fuel, food, anything else), and see your real net profit — not just your earnings.&lt;/p&gt;

&lt;p&gt;Why I built it: gig workers usually know what they earned, but not what they kept after expenses. ShiftLog answers that one question, simply.&lt;/p&gt;

&lt;p&gt;How it was built: Kotlin + Jetpack Compose + Room, everything on-device, no backend, no account needed. I built it by guiding AI agents step by step, learning as I went — I'm not a coder by background.&lt;/p&gt;

&lt;p&gt;It's live on Google Play now: &lt;a href="https://play.google.com/store/apps/details?id=com.shiftlog.app" rel="noopener noreferrer"&gt;https://play.google.com/store/apps/details?id=com.shiftlog.app&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;My goal this week: my first 100 downloads, and honest feedback from real gig workers. If you drive, deliver, or work shifts, try it and tell me what to fix first. I'm building in public — the next update comes from your feedback.&lt;/p&gt;

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