Dear Hiring Manager,
I have spent the last few years freelancing on mobile apps for different clients and I am now looking for a permanent mobile engineer role. Short builds kept my platform knowledge sharp and my ramp quick, but I want to stay with an app through its release cycles and own the long tail of crashes and edge cases, so I am after one team rather than the next gig. Recently I rebuilt an account recovery flow, cut crash reports on older devices, and improved completion on small screens.
Hopping between clients meant learning a new codebase and a new release process fast, shipping to the stores, then doing it again somewhere else, and that speed comes with me into a permanent role. Your team needs sound mobile UI judgement, care for performance, respect for platform constraints, release discipline, and clean API integration, which is the work I have been doing under freelance deadlines. The difference I want is staying long enough to watch crash rates settle and to fix the device-specific bugs that only show up over time.
That recovery flow used Swift, Kotlin, and React Native, with attention to offline state and crash reporting, but the part I would want to talk through is the older-device problem. I traced the crashes to a memory issue on low-end hardware, reworked the flow to suit smaller screens, and tracked the crash reports down after release rather than assuming the fix held. Permanent work lets me keep chasing that kind of long-tail quality instead of leaving it for the next contractor.
I would value a conversation about the parts of your app that misbehave across devices and where you would point me first. Mobile teams look for evidence that product quality holds up across real devices and release cycles, so I will keep this concrete and let the recovery work make the case.
Yours sincerely, Alex Morgan