A mobile workflow that fits
Design navigation, forms, loading states, and recovery around a smaller screen and interrupted use. Define what must work when the network is slow or unavailable.
Mobile application development
Put the useful part of your product in someone’s hand.
iOS and Android apps, including companions to existing web applications.
Based in Columbus, Ohio. Available for remote projects.
01
Where I can help
An app earns its place on a phone when it makes a repeated task easier. That might involve recording a voice note, checking a job on site, capturing a photo, or returning to something personal without starting over in a browser.
I build with React Native and Expo, connecting mobile interfaces to the accounts, data, and business rules behind the product. If you already have a web application, we can work out what the mobile experience should share and where it needs its own design.
02
What we can build together
The application and its connections
Build the agreed iOS and Android features and connect the backend. Scope device capabilities such as audio, camera access, notifications, or offline storage where they serve the product.
Device testing and release preparation
Test the core journey on agreed devices, handle permissions and error states, and prepare release builds and handoff documentation. Include store submission support when it is part of the engagement.
03
All work →Relevant work
ChildScribe
ChildScribe is my beta memory-keeping product. Its Expo mobile work sits alongside a Laravel web application, with a voice-led experience and shared product data.
View project ↗expo-agent-bridge
I built developer tooling that exposes screenshots, navigation, state, network logs, and console output from an Expo app to coding agents in the iOS Simulator.
View project ↗04
How we'd work together
- 01
Choose the reason for an app
Identify the repeated task and device features that matter. Compare a mobile app with improvements to your existing mobile website before committing to the build.
- 02
Prove the core journey
Build a working slice with real backend integration and test it on the agreed devices. Resolve authentication, permissions, and connectivity behavior early.
- 03
Prepare for release and updates
Work through release builds, store materials, and testing feedback. Agree on ongoing operating-system, dependency, and product updates as a separate support scope.
The first conversation defines the fit. Scope, price, and timing are agreed before work begins.
Questions
Can one codebase serve iOS and Android?
React Native and Expo let us share substantial application code. Platform behavior and device integrations still need individual attention and testing; the supported devices are part of the scope.
Can the app use our existing backend?
Yes, when the backend can provide the necessary APIs and authentication. I can assess those interfaces and include any changes needed for the mobile workflow.
Do you handle app store submission?
Submission support can be included. You provide the business-owned developer accounts and required business information. Store approval and review timing remain with the platform.
Start a conversation
Tell me what you need to make work.
These details give me enough context to suggest a useful first step.
- The task people should use the app for
- Target platforms and any camera, audio, notification, or offline needs
- Your existing product or backend, deadline, and budget range
jeff@hooton.codes