Under development

Independent software developer

Based in Lahore, Pakistan. Local time in Lahore

Sharjeel Asif

I take products from idea to production: the plan, the design, the web and Android apps, the database, and the Linux servers they run on. Product engineering, Web & Android apps, Linux & DevOps.

Open to new projects

About

I’m Sharjeel, an independent software developer who owns the whole product. I plan it, design it, direct AI coding agents to build it, prove every change with real tests, and run it on servers I manage myself. One person, from the first sketch to production.

Based in
Lahore, Pakistan
UTC+5 · working worldwide
Education
CS Grad’26
GC University Lahore
How I build
AI-assisted, human-verified
Agents write code; I plan, decide, test and ship.
Status
Open to new projects
Freelance or product work
Services

What I can build for you

Three disciplines, one point of contact. Pick one, or hand me the whole thing.

  1. Web

    Web apps, end to end

    From a written plan and a UI you sign off on, to a fast, accessible Next.js front end and the API and database behind it. A sharp landing page or the dashboard your team works in every day.

    • Product planning & UI design
    • Web apps, dashboards & landing pages
    • APIs with FastAPI or Express
    • PostgreSQL schemas & migrations
    • Next.js
    • React
    • TypeScript
    • FastAPI
    • PostgreSQL
    • Tailwind CSS
  2. Android

    Android apps that work offline

    Flutter apps that keep working without a connection and sync when they can, with reminders, biometric lock and the polish of a native Android app.

    • Flutter apps for Android
    • Offline-first storage & two-way sync
    • Notifications & fingerprint lock
    • Material You theming & haptics
    • Flutter
    • Dart
    • SQLite
    • Material You
  3. DevOps

    Servers, deploys & domains

    I set up and run the infrastructure myself: a Linux VPS, Docker, nginx, SSL, automated deploys that roll back on failure, and backups you can actually restore. Then the domain, DNS and SEO, so people can find it.

    • Linux VPS setup & management
    • Docker, nginx, SSL & rate limits
    • CI/CD with GitHub Actions
    • Backups, domains, DNS & SEO
    • Linux
    • Docker
    • nginx
    • GitHub Actions
    • pm2
Work

One product, every layer

One product taken all the way down, instead of a dozen screenshots. Built with AI coding agents; planned, decided, verified and shipped by me.

Live · used daily

Habits

Web + Android · Own product · AI Engineering

A habit tracker I use every day: a FastAPI server on PostgreSQL, a Next.js web app and a Flutter Android app that works fully offline. AI coding agents wrote the code. I wrote the plan, made every product call, made each step prove itself with real tests and attack scripts, and merged and deployed every change myself.

  • Offline-first Android app with two-way sync
  • Rate limits proven by before/after attack tests
  • Encrypted off-site backups, restorable to any minute of the last 30 days
  • Every push tested; every deploy checked and rolled back on failure
  • FastAPI
  • PostgreSQL
  • Next.js
  • Flutter
  • Docker
  • nginx
  • GitHub Actions
  • Claude Code

Measured before / after

  • Before: 2.2 s, after: 0.03 s

    Another user’s sign-in check while heavy statistics run, after moving SQLite to PostgreSQL

  • Before: 11 s, after: 0.16 s

    A normal user’s slowest request during a nonstop-statistics attack

  • Before: 50, after: 20

    Password checks when 50 addresses guess one account. The owner can still sign in

  • Before: 12, after: 0

    Server errors from 18 malformed inputs (broken Unicode, NaN, Infinity)

How it’s built

  1. Process

    Review, plan, prove

    An independent software developer review ranked the risks. I turned it into a 10-step plan: one branch per step, each with must-haves, a verification list and a written report. Agents never commit or deploy; I review and ship every change.

    • Claude Code
    • AGENTS.md
    • Written reports
  2. Product

    Rules before screens

    Three habit types, weekday schedules that never rewrite history, and an importance-weighted daily score. Server, phone and web compute it identically, and a test compares them figure by figure.

    • Product decisions
    • UI design
  3. Database

    PostgreSQL, moved with zero loss

    The live data moved from SQLite during a deploy: rows and sync counters compared, with automatic fallback on any mismatch. Nobody was signed out. Constraints repeat the API’s rules as a last line of defence.

    • PostgreSQL 18
    • SQLAlchemy
    • Alembic
  4. Backend

    An API that says no politely

    Sign-in throttling that never locks the owner out, quotas with plain-language messages, and a two-account isolation test over every route. Every route is fuzzed, and none may answer with a server error.

    • Python
    • FastAPI
    • pytest
    • Schemathesis
  5. Web

    Instant on the web

    Ticks show before the server answers and roll back if saving fails. Stats, streaks, a score-tinted calendar, keyboard shortcuts and export, checked by a 63-step test of every screen in a real browser.

    • Next.js
    • TanStack Query
    • shadcn/ui
    • Playwright
  6. Android

    Works on a plane

    Every change is saved on the phone first and synced in resumable batches; the latest edit wins. Local reminders, fingerprint lock, and it catches up on its own after a server restore.

    • Flutter
    • Dart
    • SQLite
  7. Infrastructure

    Self-hosted, self-checking

    Docker on my own VPS behind nginx with per-address limits. Each deploy checks everything before it changes anything, and rolls back if the new version doesn’t answer. The whole deploy is rehearsed in Docker-in-Docker first.

    • Linux
    • Docker
    • nginx
    • GitHub Actions
  8. Backups

    Restorable to the minute

    Every change is encrypted and shipped off-site within a minute, and kept 30 days in a bucket the server can’t delete from. Restores are rehearsed automatically and checked row by row against the live data.

    • WAL-G
    • Backblaze B2
    • Object lock
Process

How a project ships

The same simple pipeline every time, so you always know what happens next.

  1. Discover

    A short call about your goals, users and deadline. You get a written scope and an estimate.

  2. Design

    Wireframes and UI you see and sign off on before any code is written.

  3. Build

    AI agents write code against the plan. Every step proves itself with real tests before it reaches you, and you can click through progress every week.

  4. Ship

    Automated deploys to a server I set up, with SSL, backups, your domain and SEO in place.

  5. Support

    I stay on after launch for fixes, updates and the next feature.

Stack

Tools I trust

Boring, proven tools wherever possible, paired with frontier AI agents. That’s what keeps projects on time and servers quiet.

frontend
  • TypeScript
  • React
  • Next.js
  • Tailwind CSS
  • shadcn/ui
  • TanStack Query
  • GSAP
backend
  • Python
  • FastAPI
  • Node.js
  • Express.js
  • REST APIs
data
  • PostgreSQL
  • SQLite
  • SQLAlchemy
  • Alembic
mobile
  • Flutter
  • Dart
  • Android
devops
  • Linux
  • VPS
  • Docker
  • nginx
  • pm2
  • GitHub Actions
  • SSL & DNS
  • Backblaze B2
ai
  • Claude
  • Claude Code
  • Gemini
  • Antigravity
  • AGENTS.md workflows
  • Test-first verification
design
  • Figma
  • Canva
Contact

Have a project in mind?

Let’s ship it.

Tell me what you’re building. I’ll reply with questions, a plan and an estimate.

Local time
Local time in Lahore
Based in
Lahore, Pakistan · UTC+5
Availability
Taking new projects