6 ms·
None of what you said makes sense. Firstly on iOS you can send as many IPAs as I want to friends, testers, colleagues etc provided I've gone through the 30s pr
by threeseed 13y ago
None of what you said makes sense.
Firstly on iOS you can send as many IPAs as I want to friends, testers, colleagues etc provided I've gone through the 30s process of adding them to Apple's list. This isn't some giant inconvenience that warrants completely switching a platform.
Secondly if your app is intended to be cross platform. Then why would you start creating OS specific functionality you know will never work on the other platform. It's completely illogical.
iOS is likely to remain the primary platform for prototyping. Why ? Because it is just so much nicer. The iOS Simulator "just works" and exactly mirrors your target devices. Not the pathetic joke that comes with the Android SDK which has no relation to how your app will run on a Samsung versus HTC devices.
- general_failure 13y agoWe are not comparing Dev tools. We are comparing Dev life cycle and methodologies
- threeseed 13y agoWe are talking about choosing iOS versus Android for prototyping. My point is that the iOS development experience is far superior to Android in particular because of the strength of the simulator. How you "get your code running" is the most important part of the dev life cycle.
- tadfisher 13y agoPerhaps for software development, but not for product development. Often as or more important to a product is finding out how it works for real users, and rapidly prototyping and disseminating builds is a good way to do that. While software engineering is hard as a discipline, I don't feel it is the hardest part of building a startup.
- bad_user 13y agoOn the other hand, for Android it's far easier to get your app running on the device itself. The only thing you have to do is to connect the device to your computer and click Run in the IDE. Beginners can get something up and running within minutes, which includes the time to download the IDE and create a Hello World. The whole workflow runs well, as you get the logs in your IDE or whatever and you can do debugging and so on and it's really not that bad, given that no simulator can match an actual device - there's something to be said about keeping the phone in your hand, rotating it at will and touching it to see how the app feels. Apple's provisioning process on the other hand is the most painful thing I ever experienced.
- engrenage 13y ago> Apple's provisioning process on the other hand is the most painful thing I ever experienced. Your information is years out of date. In XCode, you click 'use this device for development' and all the provisioning is done fully automatically. So no. It is not far easier to get your app running on the device itself. That is just false.
- dvanduzer 13y agoI get the impression that everyone in this thread with strong negative opinions, regardless of platform, hasn't spent more than half an hour on the other one.
- chetanahuja 13y agoHow you "get your code running" is the most important part of the dev life cycle. How you *get your code running on a device" is even better. And it's trivial with Android. It's a royal pain in the butt with iOS.
- threeseed 13y agoI take it you've NEVER actually developed on iOS before. The simulator in almost every situation matches the device. And I don't understand how connecting your phone to your Mac constitutes "a royal pain in the butt".
- chetanahuja 13y agoOh yes I have. Both on iOS and Android. While suppressing disbelief that this is even something being argued, I present the instructions to run your newly built app package on your Android device: 1) Make sure your the appropriate security options to allow app installs are checked in the phone settings. 2) adb -d install <path to apk> 3) Enjoy the your own app on your hardware you own without asking permission from anybody else For iOS, start by paying $99 to Apple to register in the dev program. Then go through this tutorial explained with the help of >20 screenshots: http://mobiforge.com/developing/story/deploying-iphone-apps-real-devices http://mobiforge.com/developing/story/deploying-iphone-apps-...
- slewis 13y agoMy company has prototyped on both platforms, and I strongly prefer Android for this purpose. Test flight is significantly more inconvenient for all parties than sending around Android apks. So is Apple's provisioning process for development (you'll certainly have to figure out how to re-provision your development devices a few times). Android's OS integration also makes for better demos of our app. Since it's a remote control for another device it makes a lot of sense to have lock-screen and pull-down controls. We can't show that off on iOS. Finally, the Android developers that I know simply don't use the simulator, they always use hardware. I found it strange coming from iOS, but I've gotten used to it. I weight this negative much lower than the deployment advantages that Android has for prototyping. Of course in the end you'll have apps on both platforms, but here's a vote for doing early development on Android.
- nucleardog 13y agoI love Android. I really only develop for Android. But to say the Android emulators are better than the iOS simulator (or even comparable) is hilarious to me. The reason everyone tests on hardware is because the emulator is %@$#ing slow. i7 @ 4.2GHz, 12 GB of RAM... the emulator still takes MINUTES to start and runs unusably slow. The iOS Simulator on the MBP work gave me (mid-2010) runs at basically native speed. I do some development with Cordova. During development I either test on my Android phone or an iOS simulator. Those are the only realistic options.
- charleslmunger 13y agoHave you tried using the x86 images with KVM? They're quite speedy.
- yla 13y agoHay. Have you tried Genymotion (http://www.genymotion.com/ http://www.genymotion.com/). It's really really fast. Currently, they only support for Android 4.+ emulators but they will support the lower api soon.
- antback 13y agotry using genymotion. it takes 20 seconds on my mbp to starting up.
- mattquiros 13y ago> This isn't some giant inconvenience that warrants completely switching a platform. WRONG. Contacting all 30 of your friends and WAITING for them to give you their device UUIDs and giving them long instructions on how to find it from iTunes if they don't know how? How is that easier than sending an APK to your friends which they can simply download and install? And you seem to just have glossed over how it's a waste of money to sign up for an iOS developer license to build an app that, you find out, nobody wants to use. > why would you start creating OS specific functionality you know will never work on the other platform. It's completely illogical. Uhhhhhh, what? What do you mean OS-specific functionality? GPS? File reading and writing? Motion sensors? Buttons and text fields? Are you kidding me? Both Android and iOS have those. Do you even own a smartphone? If you mean iCloud, why is that a problem? Even if you're developing for iOS, you can use Google Drive. If my startup had something to do with cloud syncing, catering to platform-exclusive cloud services isn't illogical. > iOS is likely to remain the primary platform for prototyping. Why ? Because it is just so much nicer. I'm pretty sure a "prototype" doesn't have to be "nice." > The iOS Simulator "just works" and exactly mirrors your target devices. Again, WRONG. You're not supposed to rely on the simulator precisely because it DOESN'T exactly mirror your target devices. It doesn't have motion sensors, uses your computer's internet connection as its own, uses your computer's processing power as its own, doesn't give you the same retina iPhone experience, etc. Gee, have you even tried developing mobile apps?
- dvanduzer 13y agoYou know, there are dozens of free apps out there that accept an email address as input, and provide a MIME encoded UDID as output. I know it's a pain in the ass to buy an entire Apple computer just to develop for iOS, but crikey, why are you so angry about it?
- BitMastro 13y agothreeseed is well known to "favour" the Apple ecosystem and disdain the Google one. In other words, it's trollish
- threeseed 13y ago
- NicoJuicy 13y agoIf you would developped for Android, you should have known that you don't simulate a brand. You simulate application sizes :) Ever developped for Android, because i doubt so. Easier collecting feedback and faster "getting it out" iterations to improve your application.