What we test for
Typical work
- Features in existing iOS and Android apps, in their own language
- Platform capabilities a cross-platform framework cannot reach
- Migrations to SwiftUI and to Jetpack Compose without a rewrite
- Store releases, review, and staged rollouts
The coding test
Build a screen in SwiftUI or Compose with data from an API, offline state, error handling and tests, then fix a memory or lifecycle bug we planted. Scored on platform idiom, on lifecycle awareness, and on the tests.
Inside Native
The ones people search for by name get a page of their own, with their own coding test and interview questions.
Five interview questions you can reuse
We use questions like these in our soft-skills and technical rounds. Steal them for your own interviews.
When is native worth paying for over cross-platform?
A strong answer covers: Deep platform integration, heavy graphics or hardware, strict performance or battery budgets, or a product whose value is feeling right on one platform. Two code bases is a real cost, so it should be a decision rather than a default.
SwiftUI or UIKit, Compose or Views, in a code base that has both?
A strong answer covers: New screens in the new framework, existing ones left alone until there is a reason, interoperating at the boundary. A rewrite for its own sake spends months and ships the same app.
How do you find a memory leak on mobile?
A strong answer covers: Instruments or the Android profiler on a real device, looking for retain cycles and listeners nobody removed, and watching memory across a navigation loop rather than at a single moment. A leak shows up as a slow app long before it shows up as a crash.
What do you do about a permission the user denied?
A strong answer covers: Degrade gracefully and keep the feature usable without it, ask in context rather than at launch, explain why before the system dialog, and route to settings afterwards. A blocked screen that just says no is a one-star review.
What gets an app rejected from review, and how do you avoid it?
A strong answer covers: Permissions with no clear purpose string, forced sign-in, payments routed outside the store, private APIs, and incomplete metadata. Read the guidelines for what you are building before you build it, and keep a shippable build while you argue.
One monthly price per developer. Everything in it.
No deposit, no minimum term, no placement fee. You pay one invoice a month for each developer on your team.
Per developer, all-in. Your quote arrives by email with your exact number after you send the brief.
- Developer pay, local payroll and taxes
- Vetting: coding test, soft skills, English
- Free replacement within 90 days
- A direct line to our CEO
What changes the price
- Seniority and role. Senior engineer, tech lead or architect.
- Stack. Some stacks and niche tools cost more to staff.
- Team size. Larger teams get a better monthly rate per seat.
- White-label. Agencies reselling under their brand get partner pricing.
Terms in plain words
- First 2 weeks risk-free: if it isn't working, you don't pay for them
- Month to month, 30 days' notice to end
- No deposit and no minimum number of seats
- Want to hire the developer full-time? Buyout of 3 months' fee in year one, 2 months' after
Questions tech leads ask us
How senior are your Native developers?
6+ years of professional Native work, with recent production experience.
Can I see the coding test results?
Yes. Every profile card includes the score and the reviewer's notes.
What does it cost?
$6,900 per developer per month, all-in, and flat: the same rate whatever the stack. Your exact quote arrives by email after you send the brief.
Skip the sales rep. Talk to the CEO.
Tell us what you're building, your stack and when you need people. Three matched profiles within 48 hours, and a straight answer on whether we're the right fit.