Skip to content
JobreachGet started

How to cold email for a mobile developer job

A mobile developer post names a platform, and the person hiring wants to know whether you have shipped an app real people use. Lead with one app they can install: the store link, who uses it, and the hardest problem you solved in it.

Updated

What mobile developer posts ask for

Posts are for one platform or for a cross-platform framework, and they ask for:

  • Android: Kotlin (Java in older apps), Jetpack Compose or XML layouts, and Android’s architecture pieces (ViewModel, Room, coroutines).
  • iOS: Swift, SwiftUI or UIKit, and Xcode.
  • Cross-platform: Flutter with Dart, or React Native with JavaScript or TypeScript.
  • Working with APIs (REST, sometimes GraphQL), storing data on the phone, and keeping the app usable on a slow or missing network.
  • State management: Provider, Riverpod or Bloc in Flutter; Redux or a similar library in React Native.
  • Releasing: the Play Store and App Store process, crash reports (Firebase Crashlytics) and push notifications.
  • Store links or a GitHub. Mobile posts often ask for apps you have published.

Your proof as a fresher

As a fresher, nothing beats an app someone can download:

  • An app on the Play Store or the App Store with real installs and reviews, even a few. Link it.
  • An internship where your feature shipped in a release. Say what it did, and how many people use the app.
  • An open-source app with your merged changes, or a well-documented app on GitHub with a short demo video if it isn’t published.
  • A hackathon app, if it worked end to end on a real phone, not only in an emulator.

A tutorial clone (a calculator, a weather app, a to-do list) shows you followed a course. A small app that solves a real problem for real people shows much more.

Your proof if you are switching in

Coming from web development, testing or another mobile platform? Lead with what carries over:

  • From web development with React: the React Native or Flutter app you have built since, and the API work you already do every day.
  • From backend development: the APIs your mobile team calls, and the app you have built on top of them.
  • From mobile testing: the devices, versions and crashes you know well, and the app or features you have now built yourself.
  • From one platform to another (Android to Flutter, say): the same app rebuilt, or one feature built in both.

If your work app is private, describe what you built without the company’s details, and add one public app or repository.

Your proof in two sentences

Sentence one: the app, the platform and who uses it. Sentence two: the hardest problem you solved and a result someone can see (installs, ratings, speed, crashes fixed).

Fresher, Flutter

I built BusBuddy, a Flutter app that shows when the next college bus will reach your stop, published on the Play Store and used by students at my college. It keeps working with no signal by storing the timetable on the phone and syncing when the network comes back.

Switching from web

As a React developer at an agency, I built and published a React Native app for a gym client, with class booking and payments, now on both stores. I cut its start-up time by loading the schedule screen first and the rest in the background.

Both are made-up examples. The numbers in yours must be your own, and ones you can explain in an interview.

An example email

Sanjay, the CTO of a grocery delivery startup, posts for a Flutter developer, 0 to 2 years, with an address for resumes and a request for store links. Ritika graduated this year and has one app on the Play Store. This is the whole email.

To
sanjay@basketly.example
Subject
Flutter Developer: Ritika Sharma, B.Tech 2026, app on the Play Store

Hi Sanjay,

I saw your post for the Flutter Developer role at Basketly. I finished my B.Tech in Computer Science this year, and I have built in Flutter for the past year and a half.

My app MessMenu, on the Play Store, lets students in my hostel see the day’s menu and skip a meal before noon, so the kitchen cooks less; about 200 students use it every day. The hard part was the noon cut-off on a weak hostel network, so the app saves each choice on the phone and sends it the moment the network is back.

Ordering on a weak network is a problem Basketly’s customers have too, which is why your post stood out. My resume is attached, and the Play Store link and the code are on my GitHub below.

Ritika Sharma
+91 98xxx xxxxx
github.com/ritikasharma-example

A made-up example: Ritika, Sanjay and Basketly are fictional. Every claim in the email comes from Ritika’s own resume.

What makes it work:

  • The store link answers the post’s own request, and Sanjay can install the app in a minute.
  • One problem solved (a weak network) that a delivery app shares, so the match is plain.
  • Daily users, even in one hostel, show the app works outside an emulator.
  • Flutter is named once; the proof does the rest.

The subject line

The role title as the post writes it, your name, your stage and, if your app is published, that it is: the reader learns the one thing they most want to know before opening.

  • Flutter Developer: Ritika Sharma, B.Tech 2026, app on the Play Store
  • Android Developer (Kotlin): Harsh Patel, 2 years, Jetpack Compose
  • React Native Developer: Neel Gupta, 3 years in React, app on both stores

Avoid subjects like “Job application” or “Resume”. The person who posted may have several openings, and the role first tells them which one.

Mistakes to avoid

  • Screenshots instead of a store link or a demo video. Reviewers want to tap through the app.
  • Android, iOS, Flutter and React Native listed as if you were an expert in all four. Lead with the one the post asks for.
  • An app that crashes on first open. Install it fresh on an old phone before you send the link.
  • A store listing with no screenshots and no description. It is part of your application now.
  • Tutorial projects as your lead. Build one small app for a real problem and publish it.
  • An APK file attached to the email. Many people won’t install an unknown file; a store link or a video is safer.

And the ones that hurt in every role: a guessed address, a generic resume, and an email longer than a phone screen. More in how to email a recruiter about a LinkedIn hiring post.

Where mobile developer posts appear

  • LinkedIn posts by founders and CTOs of consumer startups: delivery, fintech, ed-tech, health and social apps.
  • Other titles for the same work: Android developer, iOS developer, Flutter developer, React Native developer, mobile app developer.
  • Company job boards on Greenhouse, Lever and Ashby, under mobile or engineering.
  • Agencies that build apps for clients, which hire mobile developers often and look at published apps first.

A LinkedIn post search to start from (search Posts, Date posted Past 24 hours):

Mobile developer posts for freshers

("android developer" OR "flutter developer" OR "react native") ("send your" OR "share your") fresher NOT Lahore

4 of 5 ORs, ANDs and NOTs

Swap a title for "iOS developer" if that is your platform. If posts from Islamabad crowd the results too, add NOT Islamabad (five operators). Interns can search ("android developer intern" OR "flutter developer intern") instead of the titles, without fresher. LinkedIn finds nothing at all once a search has more than five ORs, ANDs and NOTs: see how to find hiring posts on LinkedIn. If there is no reply in about a week, follow up once.

Guides for other roles

All of them, with what to lead with for each: cold email by role.