Back-ends that outlive their launch, with the app to match.
Cloud platforms and mobile apps, built together as one system: PHP/Laravel and Node.js on DigitalOcean, with iOS and Android shipped to both stores from one React Native codebase. Builds are quoted after a scoping call; if you want a fixed number first, a code-quality audit is priced per scope and delivered in writing.
NDA signed before I see any code, and the senior engineer on the build does not change halfway through. If you already have a launch date, put it in the first message. I would rather argue about it early than miss it.
Built together from the first commit
Two vendors, one app and one API, and the integration belongs to whoever has time left. That is the version I get called in to fix. EC:{Dev} Labs builds the cloud back-end and the mobile client as one system. Same architecture, same code review, one accountable lead.
This has been the core of my work since 2013: schema design and query patterns that hold up at scale, and architecture decided before the first line of code. The logistics platform in the case studies shows it in production.
What gets built
One scope covers it from API schema to store submission.
- REST and GraphQL APIs in Laravel or Node.js, with MySQL, Postgres, or Firebase behind them, and query patterns that run at scale
- React Native + TypeScript apps for iOS and Android: one codebase, both stores, with navigation, state, and CI set up from day one
- Java 17 native modules where the cross-platform layer can’t reach: hardware access, performance-critical rendering, platform-specific APIs
- Push notifications, deep links, analytics, and crash reporting wired to your back-end from the start
- Linux, nginx, Docker on DigitalOcean (or your provider), with the deploy steps documented as part of the work
- App Store and Play Store submission, including the tedious parts
Two ways to bring me in
Same engineering, two engagement models.
What the first month looks like
What you’re shipping, what already exists, and where the risk sits. After the call you get a written scope summary; if we agree on it, that becomes the basis for the contract.
Ongoing work bills weekly: you buy a week of focused output, get a written report of what shipped, and adjust the next week’s scope. No hourly tracking spreadsheets.
Repository, infrastructure configuration, and written docs, handed over as a checklist we work through together.
What clients ask about a build
Can you sign an NDA and work white-label?
Yes, both. NDA-ready means I review and sign standard agreements without requiring two weeks of legal negotiation. White-label means your client sees your studio’s name on everything.
What does handover include?
The repository, the infrastructure configuration, and written documentation: enough that the next engineer can read what’s running without calling me.
Who owns the code and the infrastructure accounts?
You do, from the first week. Work happens in your repositories and your cloud, domain, and store accounts wherever possible: App Store, Google Play, and API credentials registered to you. You own the code and the keys throughout, so nothing needs buying back if you pause or end the engagement.
Have a platform or an app to ship?
Send over what you already have, whether that is a spec, a running app, or just the idea, and we scope it together on the call.