App Development
I build Android and iOS apps using Unity. I turn screen designs into working apps, connect them to your existing services and add agreed device features. We can start with the main task users need to complete, then add more features. The work, cost and delivery plan are agreed before development begins.
Prototype, test, then decide
For a Unity-based app, we can start with one useful task from start to finish and agreed usage tracking. Test whether people can complete it and where they get stuck before adding more screens and features.
App timing is estimated after reviewing the designs, available APIs and device features. We agree what is working, what uses sample data and what is needed for a real-user test. Recruitment and the observation window are planned separately from development.
I use a structured testing process, adapted to the prototype, audience and budget. We agree the recruitment channels, advertising setup, metrics and responsibilities with you before testing.
We agree any paid asset licenses before purchase. Asset compatibility and permitted use need checking. Custom art, advertising, test-user recruitment and ongoing services are separate costs unless explicitly included.
Review the evidence together: develop further, change the idea or stop. The next stage needs a new agreement. An early test informs that decision; it does not guarantee demand, retention or revenue.
Discuss a first prototypeWhen this fits
01
Turn agreed designs into an interactive app build. Test layouts, navigation and a key journey with sample data. Handover identifies what is mocked; production backend work and store preparation are separate unless included.
02
Build the app’s main task with working features and connections to the available services we agree to use. You receive a version to try, source code, setup notes and a list of remaining work. App-store release is separate unless included in our agreement.
03
Complete an agreed set of features for defined platforms and devices. Receive a release candidate, device-check results and build documentation. Store submission support, account access and backend dependencies are agreed upfront.
What you receive
Responsive screens, reusable UI components and interaction states, implemented from your designs or designs prepared with an agreed specialist.
Structured services, lifecycle-aware asynchronous navigation, loading and error states, and clear boundaries between UI and data.
Integration with available backend APIs, third-party SDKs and agreed native device features. Backend ownership and API dependencies are established before implementation.
Builds and checks on agreed Android/iOS devices, source, setup instructions and a clear record of completed scope and remaining work.
This offer covers Unity-based app client engineering, not every app stack. Backend development, hosting, third-party fees and specialist work are separately scoped. I remain your technical owner; trusted specialists can join by agreement. Store approval is outside my control.
How we work together
Discuss the users, core task, designs, platform requirements and available APIs. Check whether Unity is appropriate before proposing development.
Define screens, working versus mocked behavior, dependencies, acceptance criteria, fee and delivery plan.
Review testable builds together. Validate the core workflow before adding more screens and integrations.
Test the agreed devices and features, document setup and required services, and agree any further development separately.
Relevant development experience
My non-game experience includes a production Android/iOS application. I can describe my engineering responsibilities without exposing the client’s product or private implementation.
Production Android / iOS
Sole Unity client engineer and mobile architect. I implemented responsive Figma-driven UI, reusable components, dependency-injected services, lifecycle-aware asynchronous navigation, backend-dependent flows and native integrations, with device validation.
Product identity withheld · NDA-safe
Confidential by default
Product identity, screenshots, code and business details remain private. We can discuss the architectural approach at a non-confidential level; deeper access to your project can follow an NDA and agreed permissions.
How I handle confidentialityBefore we start
No. I assess the interaction, UI, integrations and platform constraints first. This service is for Unity-based clients; I do not present it as a native or web full-stack service.
Yes. We can first clarify the core journey and required screens. I can work with your designer or involve a trusted specialist by agreement; design responsibilities and fees are explicit.
Not by default. I can integrate the app client with available APIs. A new backend needs its own agreed scope and owner, along with hosting and ongoing service costs.
Choose one useful first scope instead of funding every feature at once. We agree deliverables, review points, dependencies, fee and delivery plan before work begins. Additional features, content or platforms are estimated before they are added.
Yes. Your idea and project details are not portfolio material without permission. Start with a non-sensitive outline; we can arrange an NDA before sharing confidential designs, data or repository access.
Discuss app development
Tell me who will use it, the main task and what already exists. We can choose a useful first version around your priorities and available budget.
Have a limited budget? Tell me your priority and the range you’re comfortable with. I’ll be clear about a realistic first step.
Confidential from the first conversation
I count contact interactions in aggregate, without visitor IDs or message contents.
Build a game
Improve an existing product
Keep a product moving
Revive & retest a product
Connect AI to a real workflow
Bring the right skills together
Check quality before the next step