What we test for
Typical work
- New apps from one code base, on iOS and Android
- Native capabilities reached through channels or modules
- Bringing an existing native app and a cross-platform one into one product
- Release pipelines and store review on both platforms
The coding test
Build a screen with a list from an API, offline caching, loading and error states and tests, then reach one native capability the framework does not expose. Scored on state management, on the native side, and on what they say about the trade-off they just made.
Inside Cross-platform
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.
Flutter or React Native for a new app?
A strong answer covers: What the team already knows comes first. Flutter when the UI is custom and consistency across platforms matters, React Native when there is a web React team and sharing code is the point. Neither answer is right without knowing who maintains it.
When do you tell a client cross-platform is the wrong choice?
A strong answer covers: Heavy graphics, deep platform integration, or a product whose whole value is feeling native on one platform. Also when they already have two native teams. Say it in week one, not after six months.
How much of the code should actually be shared?
A strong answer covers: Business logic, networking, models and state: all of it. The last tenth of the UI often should not be, because forcing one layout onto both platforms is where cross-platform starts to feel cheap. Share what is invisible, branch what is felt.
How do you keep a cross-platform app from falling behind the platforms?
A strong answer covers: Budget for the upgrades. A new OS version, a new store requirement and a framework major arrive every year whether anyone planned for them or not, and a team that skips two framework majors ends up with a rewrite it did not choose.
One code base is not one behaviour. Where does that bite?
A strong answer covers: Navigation and the back gesture, permissions, keyboards, notifications, and store review rules. Plan for both platforms from the start and test on both, or you ship a good Android app and an iOS app that feels wrong.
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 Cross-platform developers?
6+ years of professional Cross-platform 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.