Skip to content

From shipping apps to GDE: the work that actually compounds

I am not a Google Developer Expert yet. This is the deliberate 12-month plan I am running — and the parts of public work that actually count.

Hasan Abbas Sorathiya4 min read

I am not a Google Developer Expert yet. I am building toward it deliberately, and I think the path is more concrete than most people admit.

A GDE is recognized by Google for expertise in a technology plus a track record of contributing to the developer community — talks, articles, open source, mentoring, and helping developers solve real problems. It is not a certification you buy, and it is not awarded for having a popular app. It is awarded for being useful in public, consistently.

Here is the flywheel I am running, and the parts that actually compound.

1. Ship first, then write

The strongest technical content comes from a problem you actually solved. Not "10 Flutter tips," but "why our checkout rebuilt 40 times a second and how we found it."

My rule: every article starts as a note from production. If I cannot point to the code, the error, or the decision, I do not write it. Readers can tell the difference immediately, and so can reviewers.

A practical format:

  • Problem: what broke, with the symptom a user saw.
  • Investigation: how I measured or narrowed it.
  • Fix: the change, with the tradeoff I accepted.
  • Generalization: the rule I now apply.

That structure produces content no tutorial can copy, because it is yours.

2. Publish on a cadence you can sustain

One excellent post every two weeks beats four rushed posts in a week followed by six months of silence. Consistency is the signal. It also compounds: search traffic, inbound messages, and talk invitations all arrive late and then accelerate.

My cadence:

  • Two long-form posts per month, alternating Flutter engineering and AI-in-production topics.
  • Short build notes in between — a screenshot, a benchmark, a bug that took a day.
  • A monthly summary on LinkedIn that links to the canonical posts.

Everything lives on this site first. Cross-posting is distribution; the canonical link stays here.

3. Speak before you feel ready

The first talk does not need to be at a major conference. It needs to be useful to the people in the room.

The ladder I follow:

  1. Internal engineering talk at work — low stakes, real audience.
  2. Local Flutter or mobile meetup — 15 minutes, one lesson.
  3. Community online sessions — broader reach, recorded.
  4. Conference CFPs — submit six to get one, and expect silence.

A talk is not a blog post read aloud. The best ones show a problem live, fail once on purpose, and leave the audience with a checklist they can apply on Monday.

4. Maintain one thing in public

A pinned repository that is actively maintained signals more than ten abandoned experiments. My candidates are the ones where I have genuine domain depth:

  • stoolap-flutter — embedded SQL for Flutter with vector search and reactive streams.
  • BULBVPN — a Flutter VPN built for restricted networks.
  • wp-mcp-server — an MCP server for the WordPress REST API.

The rule: issues answered, releases tagged, README that explains the why, and a path for a stranger to run it in five minutes. A small repo with a real user is worth more than a large repo with none.

5. Answer questions in public

The fastest way to find out what you do not understand is to answer a stranger's question precisely. I spend thirty minutes a week on Flutter and Riverpod discussions, Stack Overflow, and GitHub issues.

Two rules:

  • Answer the question asked, then add the context that prevents the next question.
  • If I do not know, I say so and come back with what I found. Public honesty is a credential.

6. Build in public, not just ship in public

For Duas and Aamal and Lumio TV, I share the decisions — not the revenue, not vanity metrics, but the engineering choices: how localization works, why offline-first matters, what a 4.6-star review taught me. App users become readers; readers become users. The two audiences feed each other.

What does not count

  • Buying visibility. Followers do not make expertise.
  • One viral post. A spike without a body of work is noise.
  • Surface-level tutorials. "How to center a div in Flutter" is already answered ten thousand times.
  • Speaking only to sell. The community can smell a pitch.

A 12-month plan I can be held to

QuarterFocusOutput
Q4 2026Foundation6 posts, 1 meetup talk, refresh 2 repos
Q1 2027Range6 posts, 2 CFPs submitted, 1 open-source release
Q2 2027DepthConference talk, 1 deep technical series, mentoring
Q3 2027CommunityWorkshop, collaboration with other Flutter devs

If the work is consistent, the recognition follows. If it is not, no amount of networking fixes it.

The honest scoreboard

I track what is measurable: posts published, talks given, issues answered, repos maintained, and inbound conversations that start with "I read your article." Not followers.

The goal is not the badge. The goal is to be the engineer other engineers can learn from. The badge is a side effect of doing that in public for long enough.

If you are on the same path, or you are hiring someone who is, let's compare notes. I am always up for a good conversation about Flutter, AI, and the unglamorous work of getting better.

CareerGDECommunity

The next one

Get new essays by email

One email when a new essay or app ships. No newsletter treadmill, no noise.

No spam · Unsubscribe anytime

Hasan Abbas Sorathiya

Hasan Abbas Sorathiya

Senior mobile & AI engineer in Dubai. I build iOS, Android and Flutter products, and write about the parts that were hard.

Work with me