Skip to main content

Team

Founders with product and delivery depth

R-DEV is led by Tomas and Iveta Radvansky. Tomas brings 15+ years across mobile, web, AI, Flutter, Firebase, and release engineering, including delivery work for startups, SMEs, and remote product teams.

15+Years across mobile and product engineering
NZBased in New Zealand, working worldwide

Leadership

Meet R-DEV's founders

Meet the people connecting product priorities with technical decisions and hands-on software delivery.

Iveta Radvanska

CEO

Iveta Radvanska

Co-founder of R-DEV and creator of Backyard Hunt, focused on turning family learning into playful digital experiences.

Read more
Tomas Radvansky

CTO

Tomas Radvansky

Medical doctor turned technical architect with 15+ years across Flutter, Firebase, Node.js, AI features, and startup product delivery.

Read more

How We Work

Founder-led delivery for focused product teams

R-DEV is intentionally small. Clients work directly with senior people who can connect product goals, architecture, implementation, and release planning without adding agency layers.

Technical depth

Tomas leads architecture and delivery across Flutter, Firebase, Node.js, React Native, Swift, Kotlin, AI-assisted features, and CI/CD automation. The focus is practical engineering that keeps MVPs, migrations, and shipped products maintainable.

Product judgment

Iveta brings founder and operator context to the company, including product thinking from R-DEV's own in-house work. That gives consultations a grounded view of launch constraints, customer experience, and long-term maintainability.

Experience you can explore

Choosing a development partner means understanding the work behind the advice. Explore our Carv case study for Flutter and Firebase architecture, the ElevenLabs project for cross-platform audio integration, and PositionTech for long-running mobile and web delivery.

Our own products also inform how we approach a client engagement. Building and maintaining software ourselves brings practical questions into the conversation: what to release first, what to automate, how to support users, and which technical choices will remain manageable as the product changes. On a first call, we connect that experience to your scope and constraints.