Share the settings with the whole team — a year later
After one year of keeping the project's settings into VCS, I share my new findings. What worked? What didn't work, and how did we fix it? Read to the end for a bonus tip!
tips
22 posts
Quickly change tokens case (Android Studio protip #7)
Changing the casing of some text has never been so easy as in your IDE!
Share the settings with the whole team (Android Studio protip #6)
How can you make sure everyone on the team is using the same IDE settings? Put the .idea folder in version control!
Use tasks to bring the stories to you (Android Studio protip #5)
Surface tickets from your issue tracker in the IDE, and automate some of the work away!
Use custom viewers for your data (Android Studio protip #4)
Not all data types display in something useful when showing in the debugger. But you can fix that...
Analyse data flows without the debugger (Android Studio protips #3)
Trying to figure out where a value comes from? Put away the manual debugging kit and take a look at Analyze Data Flow
Analyse a stack trace (Android Studio protips #2)
A little known feature of your IDE: you can copy-paste in stacktraces from anywhere and get them linkified.
Clear the app data quickly (Android Studio protips #1)
Clearing your app's data on device when testing is a huge pain. But there is a nifty plugin that will save you quite some time...
Annotations to support your contracts
Learn what the support annotations are, and why you should use them