In this episode, I talk with Maks about his experience with multiple mobile app technologies (Ionic, Flutter, React Native, and native) and how that intersects with his experience as a recruiter. He has some interesting thoughts on how your recruiting should impact your technology choice for your project.

=============Quotes============

"... the biggest difference is that Flutter doesn't allow you to update your application without going through the whole AppStore approval process and Ionic and React Native both have that capability. And this can be a big benefit of using those."

"Pick the right technology for what they are building, and the right technology usually should also have the right talent availability. If you pick something that's really niche and I've seen that happening a lot of times, then in the end you can end up with a very small and narrow talent pool. Then if you don't look outside of your geography, you might not be able to find anyone."

"Ionic, obviously React Native. These are things where you don't really need to be an expert in mobile development. You can hire a good web developer who will get up to speed with those really fast. And, this is a huge benefit because it means that even if you have a more senior team, you want to add someone because you don't have the right velocity, you can hire a web developer, you can hire a regular or a mid-level developer, train them to work with React Native or Ionic React or Ionic angular. And basically, they will be up to speed within like days really, to be honest."

"If you don't get demos of what someone is building, if they're sitting behind the curtain and then waiting for this big opening of what they've built, that's going to end up really badly."

"... on this journey, you might need to pivot several times. So if you come to this mindset that you're going to hire a freelancer or even an agency that will develop this MVP for you, if you haven't thought about having a budget for the next iteration and the third iteration, then you might end up with a product that you paid for and nobody is going to use. So whether are you need a co-founder or not? Or a CTO? Or you can use a freelancer agency?
I think it's not the it isn't necessarily the right question. You just make sure that with the choice that you go, you have the budget to go for a longer period of time because building a product is going to take pivoting is going to take learning. And during the first phase, like building your early product MVP or even a proof of concept, you need to maximize the learning. So you need to at least as fast as possible to be able to iterate fast."

"And you can with a reasonable budget, you can create a small team that's a mix between part-time people and a full-time person that will be really productive and that will expand your budget compared to, for instance, working with agencies that will charge you premium rates for setting up the whole team. And what they'll do and what they will do under the hood is putting the tech lead for 5 to 10 hours, putting the PO to QA, and [...] then adding this junior developer where they can really optimize their profit margin and the junior or the mid-level person is going to do the bulk of the work because otherwise it just wouldn't make the business sense for them."

=============Bio===============
Maksymilian is a software engineer, technical lead, and entrepreneur. During his 16+ year career, he was building digital products ranging from early-stage startups to multinational corporations within telecom, pharma, and financial environments. For the past 6 years, he has been primarily engaged in hybrid mobile development. He also co-founded ITCraftship – tech-focused recruitment and staff augmentation agency, that uses agile in its recruitment processes.