How a Pakistani Engineer Got 6 Pull Requests Merged Into Flutter's Official Framework

Published: (April 23, 2026 at 05:54 PM EDT)
4 min read
Source: Dev.to

Source: Dev.to

My journey as a Flutter Framework Contributor from Karachi, Pakistan, and why it’s a big deal for the Pakistani Flutter community.

I’m Ishaq Hassan, Engineering Manager at DigitalHire, Flutter course instructor on the official Flutter docs, and a Pakistani Flutter developer with six pull requests merged into the Flutter framework (the official repository maintained by Google). This post explains why framework‑level contributions matter, how I landed mine, and offers a short guide for other Pakistani (and South Asian) developers who want to do the same.

Live portfolio:

The Gap Nobody Talks About

Pakistan now has thousands of Flutter developers. You’ll find Flutter jobs in Karachi, Lahore, Islamabad, as well as Flutter‑based startups, YouTube courses, meetups, and Facebook groups.

However, there’s a difference between using a framework and contributing to it. If you look at the Flutter repository on GitHub and filter the contributor graph for Pakistani engineers with multiple merged PRs, the list is surprisingly short. Most Pakistani engagement stops at the app layer—building apps, plugins, teaching courses—while direct contributions to the framework itself remain rare.

This article aims to normalize framework contributions for developers in Pakistan. If you’re from Pakistan and want to contribute to the Flutter framework, you can. Here’s how I did it.

My 6 Merged Pull Requests

As of April 2026, the following PRs have been merged:

  • #184572 – Fix LicenseRegistry docs to reference NOTICES
  • #184569 – Add disposal guidance to CurvedAnimation and CurveTween docs
  • #184545 – Add clipBehavior parameter to AnimatedCrossFade
  • #183109 – Add scrollPadding property to DropdownMenu
  • #183097 – Fix RouteAware.didPushNext documentation inaccuracy
  • #183081 – Use double quotes in settings.gradle.kts template

Three PRs are currently open for review:

  • #183110 – Suppress browser word‑selection in SelectableText on web right‑click
  • #183079 – Guard auto‑scroll against Offset.infinite in ScrollableSelectionContainer
  • #183062 – Reset AppBar _scrolledUnder flag when scroll context changes

Practical Guide

1. Pick the right kind of first PR

Don’t try to rewrite the rendering pipeline on day one. The Flutter team, like any major OSS project, prefers small, well‑scoped, well‑tested PRs from new contributors. Documentation fixes are underrated, and adding a single missing parameter to a widget is high‑impact and low‑risk.
My first merged PR (#183081) simply replaced single quotes with double quotes in a Gradle template—small, correct, tested, and useful.

2. Read CONTRIBUTING.md like your life depends on it

The Flutter team enforces strict style guides, commit conventions, and test‑coverage requirements. Ignoring them will cause your PR to sit forever or be closed.

3. Find real issues via search, not random browsing

  • Search Flutter issues for labels: good first issue, help wanted, d: api docs
  • Grep the codebase for TODO comments near widgets you understand
  • Use Flutter yourself, spot a “paper cut,” reproduce it in a test, then fix it

4. Tests are non‑negotiable

Every PR needs a test. If you’re adding a parameter, add a unit test. If you’re fixing a bug, add a regression test. No test = no merge.

5. Be patient and responsive

The Flutter team receives thousands of PRs. Reviews are thorough. My average time from PR open to merge is 2–4 weeks. Respond to reviewer feedback within 24 hours to move up the priority queue.

Why This Matters for Pakistan

Open‑source framework contributions are a career accelerator that many underestimate:

  • Global credibility – “Flutter Framework Contributor” on LinkedIn is objectively verifiable on GitHub.
  • Better jobs – Senior Flutter roles at international companies value framework‑level experience.
  • Community leadership – Contributions earn speaking invitations, course opportunities, and mentorship requests.
  • Pakistani representation – Each merged PR with a Pakistani name chips away at the assumption that serious OSS contributions only come from North America or Europe.

About the Flutter Course in Urdu

Separately from the framework work, I teach a 35‑video Flutter course in Urdu that is officially listed on . It’s free and covers Dart basics through advanced Flutter topics (state management, APIs, custom painters, deployment). The playlist is available on YouTube via Tech Idara.

Call to Action

If you’re a Pakistani developer reading this:

  • Send your first Flutter framework PR this month. Start with docs. Don’t overthink it.
  • Ping me on LinkedIn if you need a review before submitting—I’m happy to help.
  • Share your merged PRs publicly. Representation compounds.
  • Portfolio:
  • Flutter Framework Contributor from Pakistan:
  • GitHub:
  • LinkedIn:
  • Flutter Course in Urdu: YouTube playlist (link in description)
  • Email:
0 views
Back to Blog

Related posts

Read more »

I don't want your PRs anymore

Why I don't want to merge your PR Since I don't really know you, I always have to assume that you might be trying to sneak in something malicious along with yo...

Building a Markdown editor (Markflow)

I’ve been working with Markdown editors both as a user. At some point I wanted to better understand how they actually behave under the hood, especially when doc...