What we test for
Typical work
- A new app to both stores, or the native side a cross-platform app could not avoid
- Offline-first features that sync without losing what the user typed
- Release pipelines, store reviews and the phased rollout that catches a bad build
- Crash and performance work on the devices your users actually own
The coding test
Build a screen that lists data from an API, works offline and saves edits made without a connection. Then we cut the network mid-save and reopen the app. Scored on what survives, how the conflict is resolved and how the UI tells the user, not on animations.
Inside Mobile
The ones people search for by name get a page of their own, with their own coding test and interview questions.
Cross-platform
One code base to both stores, with the native side handled when it has to be.
See the page →Flutter
One Dart code base shipped to both stores, with tests and releases.
See the page →React Native
Shared TypeScript code for iOS and Android, with the native side handled.
See the page →Native mobile
Swift and Kotlin in the platform idiom, for products where native is the point.
See the page →Android and Kotlin
Kotlin and Jetpack Compose, with Play Store releases handled.
See the page →Kotlin
Coroutines with a scope that ends, and null safety used as a design tool rather than a compiler setting.
See the page →iOS and Swift
Swift, SwiftUI and UIKit, from the code to App Store review.
See the page →Five interview questions you can reuse
We use questions like these in our soft-skills and technical rounds. Steal them for your own interviews.
Cross-platform or native for a new app?
A strong answer covers: Cross-platform when the app is mostly screens, forms and API calls, and one team has to ship to both stores. Native when the product lives in the camera, the sensors, heavy graphics or the latest OS features. The senior answer starts from the product and the team, not from a favourite framework.
How do you handle data the user changed while offline?
A strong answer covers: Save it locally first, queue the change, and sync when the connection returns, with a rule for when the server changed it too. Last write wins is a choice, not a default, and the user should see which version they are looking at. Listen for what happens to a half-sent change.
A crash only happens on some devices. How do you find it?
A strong answer covers: Crash reports with symbols uploaded, grouped by OS version, device and app version, to find what the failing ones share. Then reproduce on that device or an emulator with the same settings. The usual causes are memory on low-end phones and an OS version nobody tested.
How do you release without breaking everyone at once?
A strong answer covers: A phased rollout in both stores, crash-free rate watched before widening, and a feature flag to turn off new code without a new build. A forced-update path for the day an old version must stop. Store review time belongs in the plan, not in the surprise.
How do you keep an app fast on a cheap Android phone?
A strong answer covers: Test on one. Keep work off the main thread, page long lists, size images to the screen and measure startup time. Most slowness that users notice is a long list rendering everything, or startup doing work that could wait.
One invoice a month.
The shortlist is free. Pick the contract that suits you: monthly, six months or twelve.
What every seat includes
- Contracts, payroll and compliance handled
- Vetting: coding test, soft skills, English and a level check
- Free replacements: unlimited on 12+ months, 2 on 6 months, 1 on monthly
- A direct line to our CEO
Terms in plain words
- Monthly, six months or twelve, your choice
- Your rate is locked for the whole contract on 6 and 12+ months
- Monthly ends with 30 days’ notice
- Want to hire the developer full-time? The buyout is set in the contract from day one
Questions tech leads ask us
How senior are your mobile developers?
6+ years of professional mobile work, with apps they shipped to the stores. We test the platform you hire for, cross-platform or native.
Can I see the coding test results?
Yes. Every profile card includes the score and the reviewer's notes.
Skip the sales rep. Talk to the CEO.
Tell us what you're building, your stack and when you need people. Three vetted profiles per role within 48 hours of the call, and a straight answer on whether we're the right fit.