Good Practices About Android

Best practices doesn't exist, but we can recommend you some good practices that can make your Android code easier to read and write.

Transcript

1. Good Practices About Android Jorge Juan Barroso Carmona Android Expert @flipper83 jorge@gokarumi.com
2. Silver bullets do not exist.
4. Any fool can write code that a computer can understand. Good programmers write code that humans can understand. Martin Fowler
5. Single responsibility principle Open/closed principle Liskov substitution principle Interface segregation principle Dependency inversion principle
6. Expose your Dependencies
7. Segregate Layer Responsabilities
8. Hide implementations. Use interfaces
9. Activities are not controllers
10. Async Tasks break Single responsibility principle
11. Async Tasks give headache: problems with context changes, problems with versions, problems cancel it.
12. Main thread is sacred
13. Organize your styles and themes
14. Custom views clean your layout.xml and help to readability and refactoring.
15. Memory leak is not OutOfMemoryException. WeakReference is your friend.
16. Fragmentation is not about screen resolutions.
17. There's no need to reinvent the wheel. android-arsenal.com Square libs StackOverflow
18. The Truth Is In The Code! Android is open source
19. Q&A? @flipper83 jorge@gokarumi.com