Lead Mobile Engineer · San Francisco, CA
Daniel Nugent
I’m an Android specialist who ships the whole product: native Android and iOS apps, the backend behind them, and the architecture decisions that keep them fast to change. I do my best work owning a product from first sketch through release and iteration.
-
20 years in software
Deep engineering experience across product development, delivery, and long-term maintenance.
-
Android depth, full-stack range
Kotlin, Compose, coroutines, and Flow at the core, plus native iOS in SwiftUI and TypeScript APIs on Cloudflare.
-
43k+ Stack Overflow reputation
Long-time contributor helping developers solve real Android and software engineering problems.
Projects
Coming Soon · iOS & Android
ThingMap
A home inventory app for knowing exactly where everything is: every room, shelf, and storage bin, searchable from your phone.
I designed and built ThingMap end to end: a TypeScript API on Cloudflare, a Next.js admin console, and fully native apps for Android (Kotlin and Jetpack Compose) and iOS (SwiftUI).
How it’s built
Backend
A TypeScript API on Cloudflare Workers, with HTTP routes, domain models, persistence helpers, middleware, and services kept separate. D1 holds the relational inventory data, R2 stores images, and JWT access/refresh auth enforces ownership on every authenticated resource. Schema changes are managed through migrations. A separate Next.js admin console lets me inspect users, usage, verification state, and sessions, and take moderation actions. It talks only to protected admin endpoints and never touches backend internals.
- TypeScript
- Cloudflare Workers
- D1
- R2
- JWT
- Next.js
Android
Kotlin and Jetpack Compose, with a layered, Clean Architecture–style design split into Gradle modules: an app shell, shared core modules, and one module per feature. The presentation layer uses MVI. Screens send intents to Hilt-injected ViewModels, which expose a single immutable view state and one-off effects. A pure-Kotlin domain layer defines the models, repository interfaces, and use cases. The data layer implements them with Retrofit over the API and a Room cache, which keeps the app responsive while it syncs in the background.
- Kotlin
- Jetpack Compose
- MVI
- Hilt
- Retrofit
- Room
iOS
SwiftUI, with nearly all of the code in a local Swift Package: feature modules
(Auth, Home, Item, Search, Profile) built on shared Core and DesignSystem
modules. The presentation layer uses MVVM with @Observable view
models, and an app-level router handles navigation. Core defines the models,
the API client, and the service protocols. Each feature provides its own live
service, with async/await throughout. Because the view models depend on
protocols, tests can swap in fakes. Login tokens are stored in the Keychain,
and the app uses no third-party libraries.
- Swift
- SwiftUI
- @Observable
- async/await
- Swift Package
- Keychain
About
I’m strongest on small teams where one experienced engineer can create a lot of leverage early. I work across the full path from discovery and planning through implementation, release, and iteration, and I care about making sound technical decisions up front so teams move faster with less rework.
I focus on code that is understandable, testable, and practical to maintain, with close attention to user experience, performance, and release quality. Android is my deepest expertise, but I’m just as comfortable building the SwiftUI app or the API it talks to, as ThingMap shows.
I use AI-assisted tools to speed up planning, prototyping, and implementation, while keeping human judgment on architecture, product tradeoffs, and code quality.
What I bring
- End-to-end product ownership, from idea to shipped app
- Deep Kotlin and modern Android expertise
- Native iOS in SwiftUI, plus the backend APIs behind it
- Pragmatic architecture that supports fast iteration
- Close collaboration with product and design
- Clear communication and dependable execution
Mobile apps, built thoughtfully
If you’re building a mobile product and want someone who can own it across Android, iOS, and the backend, I’d like to hear about it. Reach out at danielnugent@gmail.com.