I build mobile apps used by millions.

.NET MAUI, Android, React Native. Over a decade in production mobile, shipped to both stores.

Currently the longest-serving engineer on the Cinemark mobile app, 4.9 stars with 820K+ ratings on the App Store. Previously Android Technical Lead at Baylor Scott & White Health.

About

I don't follow trends. I move with the platform.

Career arc

VB6C# / .NETDesktop to WebMonoDroid / MonoTouchXamarinXamarin FormsNative Android / KotlinReact Native / TS.NET MAUIAI-Assisted Dev

I started writing software in VB6. Moved to C# when .NET was still new. When the industry shifted to the web, I shifted too. When mobile arrived, really arrived, before the tools were mature, I got in early. I was building Android apps in MonoDroid and iOS apps in MonoTouch before the project was even called Xamarin.

Since then I've been through every major shift in the .NET mobile ecosystem. Xamarin to Xamarin Forms to .NET MAUI. Along the way I added native Android with Kotlin and cross-platform work with React Native and TypeScript. The stack changes with the problem.


Platform depth & AI-assisted development

Because I've spent most of my mobile career in cross-platform frameworks built on top of iOS and Android, I've had to understand both native platforms deeply, the APIs and the ecosystems they run on. On the iOS side that means certificates, provisioning profiles, entitlements, APNS, and the full code-signing chain. I can explain exactly how those pieces relate to each other and why things break when they don't line up. That knowledge comes from shipping production iOS apps for over a decade and debugging everything that can go wrong between Xcode and the App Store, not from writing Swift.

Today I use AI-assisted development as a core part of how I work. GitHub Copilot is in my daily workflow across mobile development, CI/CD pipelines, debugging, and documentation. I'm currently studying for my GitHub Copilot certification. I've been doing this long enough to recognize a shift when it's happening. I'd rather learn it early than catch up later.

How I think about engineering

Strong fundamentals are what separate a good engineer from a great one. I can troubleshoot faster because I understand what is happening underneath.

Break big problems into small ones. Fix the small ones first. Don't be afraid to make mistakes, learn from them and move on.

Know when to ask for help. Timeboxing a problem before asking isn't giving up, it's good engineering discipline.

The best launch is one you celebrate with everyone who helped build it. Shipping is a team sport.

Capabilities

Mobile development is the through-line. Here's what it takes to ship.

I write mobile apps, architect them, ship them, maintain the delivery pipelines, manage store presence, and debug the platform edge cases that most developers hand off to someone else.

.NET MAUI & Cross-Platform

13+ years

I've been on this stack since 2013. MonoDroid, MonoTouch, Xamarin, Xamarin Forms, and now MAUI. Cinemark has run on every version of it.

.NET MAUIXamarin FormsC#

Native Android

Led team of 8

Kotlin, Jetpack, Firebase Crashlytics, CI/CD pipelines. Led the Android team at Baylor Scott & White, reducing the Android crash rate from 300+ per day to under 1% and lifting the Play Store rating from 3.5 to 4.5 stars.

KotlinJetpackFirebase

React Native

TypeScript, offline support, and production hybrid work. At BSW I led the Android team through a rebuild that hosted React Native for the main dashboard inside a native Kotlin app, wiring the two layers together through the JS Bridge. I also shipped a sports training app with offline scoring that synced when the connection came back.

React NativeTypeScriptExpoJS Bridge

iOS Platform & Ecosystem

The iOS delivery chain: certificates, provisioning profiles, entitlements, APNS, code signing. I know how these pieces relate and why they break. No Swift required to know the platform.

APNSCode SigningApp Store ConnectTestFlight

App Store & Google Play

Submission strategy, release operations, and keeping builds out of rejection across both stores. I know the guidelines, the edge cases, and which design decisions cause review delays before they happen.

App Store ConnectGoogle Play ConsoleReview Guidelines

Mobile CI/CD

Designed and built multi-environment mobile delivery pipelines for Cinemark and Baylor Scott & White using Azure DevOps. Pipelines covered Dev, QA, Staging, and Release with automated distribution to TestFlight, Google Play, and BrowserStack, plus iOS Simulator builds for QA investigation.

Azure DevOpsTestFlightBrowserStackVS App Center

Backend & API

.NET Web API, Azure services, Entity Framework. I build and integrate the APIs that the apps I ship run on.

.NET Web APIAzureEntity Framework

AI-Assisted Mobile Development

Active in daily work

GitHub Copilot is part of my daily mobile workflow, across development, CI/CD pipeline work, debugging, and documentation. It's built into how I work, not bolted on.

GitHub CopilotClaude CodeGH-300 in progress

Built for millions. Measured in results.

4.9

App Store rating, 820K+ ratings

4.6

Google Play rating, 108K+ reviews

<1%

Crash rate, monitored continuously

13+

Years of production mobile experience

Not actively looking

Let's have a conversation.

I'm not actively in the market right now, but I'm always open to conversations worth having. If something here caught your attention, I'd still like to hear from you.