4 ms·
so writing it twice on Swift and Java is better than once on something like Dart/Flutter? what’s the best cross-platform strategy?
by M5x7wI3CmbEem10 6y ago
so writing it twice on Swift and Java is better than once on something like Dart/Flutter?
what’s the best cross-platform strategy?
- hadtodoit 6y agoIf all you're doing is creating an MVP do whatever is easiest. But yes ideally you would have two separate codebases and obviously it's dependent on your project how much tools can be shared between the projects.
- ajconway 6y agoHistorically, developing an app with tools that are native to the platform provided asymptotically better user experience. So, if your goal is to perfect the UX, native is your choice. In reality, rarely do you need to work on the UX first. It is usually more wise to sketch the idea using cross platform tools, validate the idea, then rewrite parts of it / develop new features with native technologies.
- M5x7wI3CmbEem10 6y agomy concern with not releasing it correctly the first time is that someone else picks up the idea and does it better before you can.
- hadtodoit 6y agoThis goes back to the argument of first to market or best. I have yet to see a definitive answer.