6 ms·
If I were to seriously attempt to commercialize the toy apps I build for my kids/family I'd go iOS first easily. People with Apple devices are far likelier to p
by sidlls 9y ago
If I were to seriously attempt to commercialize the toy apps I build for my kids/family I'd go iOS first easily. People with Apple devices are far likelier to pay, and Android development is, in my view, an inferior experience (although Kotlin makes it marginally less so these days).
- Illniyar 9y agoBut would you really setup a CI process to automatically build that app? (and one that'll probably cost you at least a 100$ a month)
- scosman 9y agoI would. Every time. I've been happy with bitrise if people are looking for mobile CI alternatives: https://www.bitrise.io/ https://www.bitrise.io/
- MarkyC4 9y agoBitrise has been great for us at work as well, but we're beginning to investigate Microsoft's CI platform since we build web/desktop apps as well, which aren't a first class citizen in Bitrise. Fwiw: We also wish there was a way to publish test/linting results (you can make it an artifact, but it won't load assets, so you're stuck zipping and downloading or publishing to your own managed Web server)
- sytse 9y agoBitrise looks very nice for mobile apps. And it is open source https://www.bitrise.io/cli https://www.bitrise.io/cli Are people interested in if we ingrate https://github.com/bitrise-io/bitrise https://github.com/bitrise-io/bitrise in GitLab Runner so it works with GitLab CI?
- Pharaoh2 9y agoThis may have been historically true, but our internal data shows us that starting early 2017, people in tier 1 countries were equally likely to pay and have comparable LTV on both platforms. And if you also going to launch in EU/Australia/Canada, you will have a nearly 50-50 split of ios and android users on a platform neutral app. So the classical logic of implementing on iOS first doesn't really apply anymore. Now its more, implement first on the platform you are comfortable with but don't forget about the other platform because there is a equal amount of money to be made there... PS: Data excludes low end iOS and android devices. (< SE, old iPads/iPods, old and cheap android devices). These devices have extremely low conversion on both platforms anyway.
- sebleon 9y agoThe logic still applies. 1. Start with platform you're most comfortable with. 2. Iterate on product until you have a winning formula 3. Replicate on 2nd platform to double revenues Building is a lot easier than identifying what to build, better to speedily experiment on one platform.
- jjeaff 9y agoIn my opinion the new logic is build in React Native (unless your app fits in the 10% of use cases that won't work well with RN), then deploy to both at once. We have had excellent results.
- ewjordan 9y agoReact Native is great for apps, and if it's a game, just use Unity. They're building up their internal CI infrastructure and it works better every month. Tbh, I'm not sure how many use cases don't fit either React Native or Unity, I'd practically never choose to do an app another way these days.
- rimliu 9y agoI'd say RN won't work well in 99% cases.