Under the hood, iOS builds use xcodebuild, simctl install, and simctl launch. Android builds use the project’s Gradle wrapper, adb install, and an explicit launch intent. The device operations are also exposed through an HTTP API.
327 karma · joined May 3, 2010
Under the hood, iOS builds use xcodebuild, simctl install, and simctl launch. Android builds use the project’s Gradle wrapper, adb install, and an explicit launch intent. The device operations are also exposed through an HTTP API.
Technologies: BEng, Full stack developer, Kubernetes, Docker, Python, Django and some Node JS. Experience with both GCP and AWS, Extensive experience with Swift for iOS, React Native and some Android/Java to support RN apps
Résumé/CV: https://robsandhu.com Email: sandhu.rob@gmail.com
iOS Developer based in Vancouver, Canada
Portfolio: http://robsandhu.com
Blog: http://robsandhu.tumblr.com
Open source iOS project: https://github.com/hsandhu/HSInstagram
Contact: rob.sandhu.me@gmail.com
Reserved instances: http://aws.amazon.com/ec2/reserved-instances
I found the CPU time for micro instances to be sparse and unreliable to host an API for example.
This topic is very popular amongst hackers lately. I find the web developers in particular resist the native app trend, to avoid Objective-C (iOS) and Java (Android). Typical web developer lives in Javascript and a chosen high level language (Ruby, Python) on the server side.
Mobile apps are interesting because of the access to GPS, camera, accelerometer etc. Until all hardware is accessible through HTML5 providing an excellent UX, the app trend will continue in my view.