11–20 of 78 posts
"I used to think the iOS simulator was painful, now I realise it's pretty awesome. Skip the Android simulator all together and deploy to a real device, or be prepared to spend a lot of time waiting." With its "native" emulator, yes, but there are better alternatives like Genymotion. Giving up on them is not good development advice.
"I used to think the iOS simulator was painful, now I realise it's pretty awesome. Skip the Android simulator all together and deploy to a real device, or be prepared to spend a lot of time waiting." With its "native" emulator, yes, but there are better alternatives like Genymotion. Giving up on them is not good development advice.
"I used to think the iOS simulator was painful, now I realise it's pretty awesome. Skip the Android simulator all together and deploy to a real device, or be prepared to spend a lot of time waiting." With its "native" emulator, yes, but there are better alternatives like Genymotion. Giving up on them is not good development advice.
Check out Genymotion.
It's not a coindidence that it is recommended by very talented developers such as C. Mottier: http://cyrilmottier.com/2013/06/27/a-productive-android-deve...
You can get a pretty responsive emulator if you use an x86 ABI and HAXM[0]. [0] http://software.intel.com/en-us/android/articles/intel-hardw...
You will get a faster emulator, but since x86 is used on like sub 1 percent Android devices, won't that be more like using a simulator, which would make it just as useless/useful as a simulator? Does the x86 image contain support for ARM, too?
"When the user rotates the device your activity is completely reset" You just need to set " android:configChanges="orientation|keyboardHidden" in the manifest. This is very well documented.
"When the user rotates the device your activity is completely reset" You just need to set " android:configChanges="orientation|keyboardHidden" in the manifest. This is very well documented.
"A trick often used by iOS devs is to use the tag of a view to hold lookup information, such as offset in arrays. With Android you can shove the entire object into the tag; pretty useful." Yes, but if it's something like a ListView, don't put offset in array there, because the views are recycled (when user scrols), so you're likely to end up with corrupted data. I got bitten by this in the beginning. You can go to gr…
@property (nonatomic, strong) id context;
or
@property (nonatomic, weak) id context;
if you are sure the context will always exist.
"I used to think the iOS simulator was painful, now I realise it's pretty awesome. Skip the Android simulator all together and deploy to a real device, or be prepared to spend a lot of time waiting." With its "native" emulator, yes, but there are better alternatives like Genymotion. Giving up on them is not good development advice.
That is the reason why there are Nexus phones.
Some things I would note: * Do not use getBaseContext() like he does when he created the new Activity. Use getApplicationContext for most things (unless an Activity is required) as this is guaranteed to be the same throughout the lifetime of your application. * For log alternatives, checkout Timber by Jake Wharton ( https://github.com/JakeWharton/timber ) * I would suggest using the Build.VERSION_CODES when making th…
alias lc="adb logcat | sed -e $'s/^I.*/\e[0;94m&\e[0m/g; s/^D.*/\e[0;92m&\e[0m/g; s/^W.*/\e[0;93m&\e[0m/g; s/^E.*/\e[0;91m&\e[0m/g'"> There is also the excellent Genymotion emulator.
Genymotion deserves to be mentioned in a top level comment. It's the by far the fastest Android emulator and it works brilliantly simple.