3 ms·
IF a developer team his mostly iphones they will do that one first I bet. Thats how I have seen it done usually. The problem is that if most non standard use
by matt321 4y ago
IF a developer team his mostly iphones they will do that one first I bet. Thats how I have seen it done usually. The problem is that if most non standard use cases (like bluetooth) support are garbage in cross platform tools. So I have to make two mobile apps: one for iphone and one for android. I have an iPhone so I making that one first. If its not that popular, maybe I just dont make an android app.
- taurusnoises 4y agoGet it. Is there a general vibe in the dev world of like, "ugh, now we have to make the Android version..."
- smoldesu 4y agoNot neccesarily? If you start with an Android app, the sentiment tends to go both ways. There's simply no good cross-platform mobile toolkits.
- skydhash 4y agoReact Native and Flutter is fine if you want to do information app (backed by a backend for most of the work), but as soon as you want to tap into the native capabilities of the device, the difference can become too much. Those toolkits rely on being able to find a common ground between the two ecosystems, and sometimes that can be a hindrance.