- Really cool tool http://www.classyshark.com for opening up any android executable and analyzing its content.
- Great for debugging and setting up proguard stuff
- Good for handling multidex-related questions
- Good for analyzing dependencies
- Has an easy to use GUI with a good search feature
- Good for general inspection of a project
- Use rebound (http://facebook.github.io/rebound/)
- Basically a bunch of other tips on how to do good UX... very little in the way of actual android tips
- Use branch (https://branch.io)
- Totally free
- Built-in cross-platform support
- Supports FireOS
- Customizable user experience
- Built in metrics dashboard
- Kotlin is growing and finally starting to be adapted by some real teams
- Kotlin looks pretty awesome
- Kotlin is so simple that it could effectively be used in place of Gradle for functionality and simplicity
- Good because you can do your entire codebase in it (soon you can do xml layouts and drawables too)
- Basically a sales pitch by couch db
- Facebook does some crazy stuff in the linux kernel to measure performance on the go because all existing android solutions are terrible.
- Really cool stuff, but way too in-depth and would takes months and months to replicate.
- https://facebook.github.io/react-native/docs/android-ui-performance.html
- Lyft has their own caliper-like tool integrated into their build system with CI
- More of a general development process talk; was quite similar to ours
- Periscope has a really cool hearts animation
- Does anyone even use periscope though?
- Static analysis is super important
- Use Dagger 2
- Use annotations and actually process them so you can be confident they work before runtime
- Use Infer http://fbinfer.com and check out RAVE (can't find link)
- Use rebound and custom animations
- FireOS is one of the best forks
- Expect many more forks in the future as AFAAS (Android-Forks-As-A-Service) becomes a thing
- Android has finally made a dynamic audio-buffer (making it much easier to send data over the audio jack) as part of M
- Avoid built-in MediaService
- Basically common sense (good docs and tests)
- Way over-the-top