<?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 Ilyas </title>
    <description>The latest articles on DEV Community by Muhammad Ilyas  (@miksi0078).</description>
    <link>https://dev.to/miksi0078</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3724648%2Fadc48032-d380-4b37-bde9-9d135ac3d1ba.jpeg</url>
      <title>DEV Community: Muhammad Ilyas </title>
      <link>https://dev.to/miksi0078</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/miksi0078"/>
    <language>en</language>
    <item>
      <title>Architecting an Offline-First Parking Ecosystem for Pakistan (RFC)</title>
      <dc:creator>Muhammad Ilyas </dc:creator>
      <pubDate>Wed, 21 Jan 2026 20:16:48 +0000</pubDate>
      <link>https://dev.to/miksi0078/architecting-an-offline-first-parking-ecosystem-for-pakistan-rfc-256g</link>
      <guid>https://dev.to/miksi0078/architecting-an-offline-first-parking-ecosystem-for-pakistan-rfc-256g</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.amazonaws.com%2Fuploads%2Farticles%2Fygj13c7facwzm01x5g59.jpeg" 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.amazonaws.com%2Fuploads%2Farticles%2Fygj13c7facwzm01x5g59.jpeg" alt=" " width="800" height="446"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h1&gt;
  
  
  Introduction
&lt;/h1&gt;

&lt;p&gt;I am a BS Artificial Intelligence student at UCP Lahore. My team and I are designing &lt;strong&gt;ParkEase&lt;/strong&gt;, a system to solve urban congestion caused by parking searches.&lt;/p&gt;

&lt;p&gt;We are currently in the &lt;strong&gt;architecture phase&lt;/strong&gt; and looking for feedback on our logic and tech stack choices.&lt;/p&gt;

&lt;h1&gt;
  
  
  The Engineering Challenge
&lt;/h1&gt;

&lt;p&gt;The core problem isn't just "finding a spot." It is handling data in a constrained environment:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt; &lt;strong&gt;Connectivity:&lt;/strong&gt; Parking basements in Lahore often have zero signal.&lt;/li&gt;
&lt;li&gt; &lt;strong&gt;Data Sync:&lt;/strong&gt; How to sync payment data when the user comes back online.&lt;/li&gt;
&lt;li&gt; &lt;strong&gt;Concurrency:&lt;/strong&gt; Handling real-time "Reserve" requests so two drivers don't book the same slot.&lt;/li&gt;
&lt;/ol&gt;

&lt;h1&gt;
  
  
  Proposed Architecture
&lt;/h1&gt;

&lt;h2&gt;
  
  
  1. The "Offline Wallet" Logic
&lt;/h2&gt;

&lt;p&gt;To solve the connectivity issue, we are proposing a "Float-based" wallet:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;User pre-loads funds (e.g., 1000 PKR).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Entry:&lt;/strong&gt; Guard scans QR -&amp;gt; Timer starts (Local timestamp).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Exit:&lt;/strong&gt; Guard scans QR -&amp;gt; Timer stops -&amp;gt; Fee calculated locally on the Guard's device.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Sync:&lt;/strong&gt; Transaction uploads to Firebase once the Guard's device reconnects.&lt;/li&gt;
&lt;li&gt;&lt;em&gt;Question for the community: Is this the safest approach to prevent fraud?&lt;/em&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  2. The "Hourly Block" Algorithm
&lt;/h2&gt;

&lt;p&gt;We designed a billing algorithm to maximize revenue for owners. Instead of per-minute billing, we use "Hourly Blocks."&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;em&gt;Scenario:&lt;/em&gt; Enter 5:59 PM, Exit 6:01 PM.&lt;/li&gt;
&lt;li&gt;
&lt;em&gt;Logic:&lt;/em&gt; System detects occupancy in Block A (5-6) and Block B (6-7).&lt;/li&gt;
&lt;li&gt;
&lt;em&gt;Result:&lt;/em&gt; Billable time = 2 Hours.&lt;/li&gt;
&lt;/ul&gt;

&lt;h1&gt;
  
  
  The Tech Stack Choices
&lt;/h1&gt;

&lt;p&gt;We are planning to build this using:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Frontend:&lt;/strong&gt; Flutter (for cross-platform consistency).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Backend:&lt;/strong&gt; Node.js (for scalable, non-blocking I/O).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Database:&lt;/strong&gt; Firebase Realtime Database (for the live map availability).&lt;/li&gt;
&lt;/ul&gt;

&lt;h1&gt;
  
  
  Request for Feedback
&lt;/h1&gt;

&lt;p&gt;Since we are currently building the MVP, I would love to hear from senior engineers:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt; Is Firebase the right choice for cost-scaling, or should we move to PostgreSQL + WebSockets?&lt;/li&gt;
&lt;li&gt; Are there security risks with the Offline Wallet approach we missed?&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;You can view our full project documentation here:&lt;br&gt;
[&lt;a href="https://github.com/miksi0078" rel="noopener noreferrer"&gt;https://github.com/miksi0078&lt;/a&gt;]&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Building in public from Lahore, Pakistan.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>beginners</category>
      <category>architecture</category>
      <category>flutter</category>
      <category>discuss</category>
    </item>
  </channel>
</rss>
