3 ms·

I’m in two minds I got so frustrated with a cross platform technology i just wrote a native app to get away from it which the company later adopted. It impleme

I’m in two minds I got so frustrated with a cross platform technology i just wrote a native app to get away from it which the company later adopted. It implemented all latest native features, was tiny in size, and code base was easy to understand. As it grows and our teams grow it does get harder, but also, if you’re using bleeding edge features, cross platform solutions can only cater to the lowest common denominator

mhuffman 4y ago
I have had similar experiences on several decent sized mobile projects. The idea of a single code-base to rule them all is very seductive. The reality, when you get to UI and hardware issues, is when you begin to get frustrated. If your app doesn't need perfect hardware coverage, great hardware sub-system coverage (cameras in particular), and you have some cohesive UI design that won't irk people on seperate platforms ... then go ahead, React Native, or ionic, or flutter, or plenty of frameworks will work for you. Otherwise, I think it is better to just bite the bullet and run two separate code-bases with pretty tight project managment to keep them synced.